After running the update script

wget -qO wo wordops.se/tup && sudo bash wo # install WordOps

...and it completing without any visible errors, I now get a 502 Bad Gateway for every page of the website. The entire site is now offline.

Correction...

Half the website is now offline.

I can't seem to figure out what is going on.

ee stack status

...shows

PHP5.6-FPM is not installed
PHP7.0-FPM is not installed
HHVM is not installed
mysql : Running
postfix : Running

wo stack status

...shows a weird message, different from ee stack status

'Namespace' object has no attribute 'php7'

It seems to me that if they are the same command they should be giving the same response; but they aren't. I brought this up in the [https://community.wordops.org/d/2-namespace-object-has-no-attribute-php7] as it seemed to be more inline with the conversation there.

The last time I had this issue (with ee) was back in February 2015 [https://community.easyengine.io/t/502-bad-gateway-nginx/3965] due to an incorrect

listen =

...argument. However, I've tried a similar adjustment and it doesn't seem to help/hurt the status of the website.

Also, it may be of note that:

wo stack purge --php
ee stack purge --php

...does NOT remove php7.2 from the system stack. Neither does:

wo stack purge --php7
ee stack purge --php7

I checked the nginx error log:
cat /var/log/nginx/error.log

...and found these errors:

2019/02/06 13:37:32 [emerg] 6792#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:38:53 [emerg] 6904#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:39:24 [emerg] 1189#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:42:07 [emerg] 1995#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:42:34 [emerg] 2040#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:51:56 [emerg] 4283#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 13:53:15 [emerg] 6189#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:05:38 [emerg] 6906#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:05:42 [emerg] 7063#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:05:42 [emerg] 7067#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:05:51 [emerg] 7620#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:24:36 [emerg] 7989#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43
2019/02/06 14:26:29 [emerg] 8070#0: open() "/etc/nginx/fastcgi_params" failed (24: Too many open files) in /etc/nginx/fastcgi_params:43

Continuing with my struggles, I checked:

ls /var

...and it showed a new crash directory. Within the:

ls /var/crash

...there was a nginx-custom.0.crash file, I assume, left over from when I ran:

wget -qO wo wordops.se/tup && sudo bash wo # install WordOps

...because it wasn't there before.

In fairness, I've been trying both ee and wo commands and have found that not all of the commands are interchangeable; at least not on a previously existing ee configuration.

When I ran:

ee stack purge --nginx
ee stack install --nginx

...I wasn't getting the correct version of nginx, but when I ran:

ee stack purge --nginx
wo stack install --nginx

...I got the correct version of nginx and the 502 Bad Gateway error went away entirely.

Hosted by VirtuBox