Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sites do not work after machine reboot #1251

Open
devbhosale opened this Issue Oct 18, 2018 · 15 comments

Comments

8 participants
@devbhosale
Copy link

commented Oct 18, 2018

After host reboot, I am seeing this error using docker logs container ID for nginx-proxy (see separate issue #1250 for issue about getting proxy error logs.

[error] 91#91: *14 no live upstreams while connecting to upstream, client

Not sure what else you will need to troubleshoot but please let me know.

lsb_release -a

System Information

  • lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 18.04.1 LTS
    Release: 18.04
    Codename: bionic

  • ee cli version
    EE 4.0.0-beta.6

  • ee cli info
    ee cli info
    +-------------------+----------------------------------------------------------------------------+
    | OS | Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 |
    | Shell | /bin/bash |
    | PHP binary | /usr/bin/php7.2 |
    | PHP version | 7.2.11-1+ubuntu18.04.1+deb.sury.org+1 |
    | php.ini used | /etc/php/7.2/cli/php.ini |
    | EE root dir | phar://ee.phar |
    | EE vendor dir | phar://ee.phar/vendor |
    | EE phar path | /opt/easyengine/nginx/conf.d |
    | EE packages dir | |
    | EE global config | /opt/easyengine/config.yml |
    | EE project config | |
    | EE version | 4.0.0-beta.6

  • wp --allow-root --info
    wp --allow-root --info
    wp: command not found

@devbhosale

This comment has been minimized.

Copy link
Author

commented Oct 18, 2018

dockergen.1 | 2018/10/18 02:44:53 Running 'nginx -s reload'
dockergen.1 | 2018/10/18 02:44:53 Received event die for container 36a1ace0beef
dockergen.1 | 2018/10/18 02:44:53 Generated '/etc/nginx/conf.d/default.conf' from 5 containers
dockergen.1 | 2018/10/18 02:44:53 Running 'nginx -s reload'
nginx.1 | 2018/10/18 02:45:03 [error] 142#142: *14 no live upstreams while connecting to upstream, client: 69.255.22.171, server: ee1.mydomain.com, request: "GET / HTTP/1.1", upstream: "http://ee1.mydomain.com-42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/", host: "mydomain.com"
ngi

@devbhosale devbhosale changed the title [error] 91#91: *14 no live upstreams while connecting to upstream, client Reboot Error- 91#91: *14 no live upstreams while connecting to upstream, client Oct 18, 2018

@frankwrk

This comment has been minimized.

Copy link

commented Oct 25, 2018

I had the same issues rebooting the host VM and found that the nginx docker container doesn't start properly. You will need to find the ID of that docker container, stop it manually and restart it. Other methods that worked include using the ee site down command, which stops the website and bring it back up with ee site up

@devbhosale

This comment has been minimized.

Copy link
Author

commented Nov 18, 2018

@kirtangajjar @mbtamuli Is this on the radar to be fixed before v4 is released?

@kirtangajjar

This comment has been minimized.

Copy link
Member

commented Nov 23, 2018

@devbhosale Can you try to reproduce this issue from v4 stable and let us know if its still there?

@mrrobot47 mrrobot47 added this to To Do in v4 Maintenance Releases via automation Nov 29, 2018

@mrrobot47 mrrobot47 moved this from To Do to Backlog in v4 Maintenance Releases Nov 29, 2018

@handpressed

This comment has been minimized.

Copy link

commented Dec 8, 2018

Definitely still an issue - has happened to me on several reboots using 4.0.0 - 4.0.4.

https://community.easyengine.io/t/easyengine-services-not-running-on-server-reboot/11651

@michacassola

This comment has been minimized.

Copy link

commented Dec 20, 2018

Can confirm this still an issue as well running Ubuntu 18 LTS and EE 4.0.10

@jeyeveey26

This comment has been minimized.

Copy link

commented Dec 30, 2018

Easiest way to deal with it instead of SSH every time is I set a simple script in /etc/init.d/ until this is fixed that runs the command:

ee service restart nginx-proxy

@michacassola

This comment has been minimized.

Copy link

commented Jan 30, 2019

That command didn't work either this time. Now on 4.0.10 and Ubuntu 18 LTS not working.

@michacassola

This comment has been minimized.

Copy link

commented Jan 30, 2019

Running
sudo ee site disable site.com
sudo ee site enable site.com
doesn't work.

Running
ee service restart nginx-proxy
doesn't work.

Restarting the server multiple times doesn't work.

Please somebody find a fix!

@kirtangajjar

This comment has been minimized.

Copy link
Member

commented Jan 31, 2019

@michacassola Can you try ee service enable db --force and check the output of docker ps -a and check if any of the site or service containers are restarting or exited?

@kirtangajjar kirtangajjar changed the title Reboot Error- 91#91: *14 no live upstreams while connecting to upstream, client Sites do not work after machine reboot Jan 31, 2019

@michacassola

This comment has been minimized.

Copy link

commented Jan 31, 2019

Sorry, already deinstalled and reinstalled. Now the main site runs fine, the others were anyways just test sites. If I run into the same problem again when new updates come in or after a rebot now I will do the steps you mentioned and post the output here.

@tenil

This comment has been minimized.

Copy link

commented Feb 14, 2019

@michacassola Can you try ee service enable db --force and check the output of docker ps -a and check if any of the site or service containers are restarting or exited?

After disable and enable the sites, I got “Error establishing a database connection” message. This command solved the problem. Thanks.

@tenil

This comment has been minimized.

Copy link

commented Feb 25, 2019

502 Bad Gateway - is back.

Running
'sudo ee site disable site.com'
'sudo ee site enable site.com'
doesn't work.

Running
'ee service restart nginx-proxy'
doesn't work.

Same as @michacassola.

Dont know what to do now. Any help?

@petebytes

This comment has been minimized.

Copy link

commented Feb 25, 2019

For me the following worked.
ee site disable on each of the sites
cd into /opt/easyengine/services and run
docker-compose down
docker-compose up -d
reboot
Then ee site enable for each of the sites

@tenil

This comment has been minimized.

Copy link

commented Feb 25, 2019

For me the following worked.
ee site disable on each of the sites
cd into /opt/easyengine/services and run
docker-compose down
docker-compose up -d
reboot
Then ee site enable for each of the sites

Thank you! It worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.