All site down, after upgrade

I have update ee with “ee cli update”
apparently the version 4.1.4 was installed smoothly even if “ee cli version” still say EE 4.1.3.

Anyway, when I try to enable one of the sites, I get the following log:

[01-09-2020 15:11:52] ee.INFO: ::::::::::::::::::::::::ee invoked::::::::::::::::::::::::
[01-09-2020 15:11:52] ee.DEBUG: -----------------------
[01-09-2020 15:11:52] ee.DEBUG: COMMAND: cd /opt/easyengine/services && docker ps -q --no-trunc | grep $(docker-compose ps -q global-nginx-proxy)
[01-09-2020 15:11:53] ee.DEBUG: STDOUT: 9eba1d3a713fed145a16e3143e754ff49f9e4ebde504a5912e3916285d2830d1
[01-09-2020 15:11:53] ee.DEBUG: RETURN CODE: 0
[01-09-2020 15:11:53] ee.DEBUG: -----------------------
[01-09-2020 15:11:53] ee.DEBUG: -----------------------
[01-09-2020 15:11:53] ee.DEBUG: COMMAND: docker ps > /dev/null
[01-09-2020 15:11:54] ee.DEBUG: RETURN CODE: 0
[01-09-2020 15:11:54] ee.DEBUG: -----------------------
[01-09-2020 15:11:54] ee.DEBUG: -----------------------
[01-09-2020 15:11:54] ee.DEBUG: COMMAND: command -v docker-compose > /dev/null
[01-09-2020 15:11:54] ee.DEBUG: RETURN CODE: 0
[01-09-2020 15:11:54] ee.DEBUG: -----------------------
[01-09-2020 15:11:54] ee.DEBUG: Using default global config: /opt/easyengine/config/config.yml
[01-09-2020 15:11:54] ee.DEBUG: No project config found
[01-09-2020 15:11:54] ee.DEBUG: argv: /usr/local/bin/ee site enable XXX DOT COM
[01-09-2020 15:11:54] ee.DEBUG: Running command: site
[01-09-2020 15:11:54] ee.DEBUG: Running command: site enable
[01-09-2020 15:11:54] ee.INFO: ======================== site enable start ========================
[01-09-2020 15:11:54] ee.INFO: Enabling site XXX DOT com.
[01-09-2020 15:11:54] ee.DEBUG: -----------------------
Starting XXXXXXcom_php_1 … error ERROR: for homestagingluganocom_php_1 Cannot start service php: OCI runtime create failed: container_linux.go:349: starting container process caused “process_linux.go:449: container init caused “write sysctl key net.ipv4.tcp_keepalive_time: open /proc/sys/net/ipv4/tcp_keepalive_time: no such file or directory””: unknown ERROR: for php Cannot start service php: OCI runtime create failed: container_linux.go:349: starting container process caused “process_linux.go:449: container init caused “write sysctl key net.ipv4.tcp_keepalive_time: open /proc/sys/net/ipv4/tcp_keepalive_time: no such file or directory””: unknown Encountered errors while bringing up the project.
[01-09-2020 15:11:58] ee.DEBUG: RETURN CODE: 1
[01-09-2020 15:11:58] ee.DEBUG: -----------------------
[01-09-2020 15:11:58] ee.ERROR: There was error in enabling XXXX DOT COM. Please check logs.

I’m on Lightsail AWS - Ubuntu 16.04.7 LTS

Can anybody please help?

Thanks,
Richard.

You seem as if you have a white screen. This can potentially be caused where your server is out of resources to make the update. Some hosts have time out limits. It could also be a plugin issue.

First, if you can access http:/ahrents.com/wp-admin and login, then disable your plugins and start over, that may be helpful. If you can’t login to your WordPress Dashboard, then follow the next steps.

Disable the .maintenancemode file that is added to your home directory when you trigger an update. You’ll need FTP or SFTP access to your home directory, provided by your hosting company. You can simply remove the “.” to disable to see if that brings it back.

Or, you can try to disable your plugins by accessing your /wp-content/plugins directory and either renaming the directory from “plugins” to something like “plugins++” or doing the same inside the directory to each individual plugin, so that you can figure out which plugin was the offender in terms of updating correctly.

Usually, this is a plugin conflict or a server time out issue, so you’ll also want to ask your host for assistance, as well.

Since we don’t know what version of PHP you are running, that could be an issue, as well. If your web host has you on an outdated version of PHP, then you can ask them to upgrade you to the latest version, 7.2, and see if that helps.