Ran an update to plesk this afternoon on a cloud server I have, it seemed to complete successfully however it gave and error that another instance of the installer was running and said the server may be non-responsive.
All sites are fine, however the Plesk panel is inaccessible now. 502 Bad Gateway when accessing xxx.xxx.xxx.xxx:8443
Running /etc/init.d/sw-engine restart is OK - starting and stopping sw-engine is fine but has no effect on the login screen still 502, the last line of /var/log/sw-cp-server/error_log shows:-
I think possibly the update failed, my Linux and Plesk Knowledge is limited so any help is appreciated! I also notice that /run is 100% used. I'm not sure if this is an issue or not!
All sites are fine, however the Plesk panel is inaccessible now. 502 Bad Gateway when accessing xxx.xxx.xxx.xxx:8443
Running /etc/init.d/sw-engine restart is OK - starting and stopping sw-engine is fine but has no effect on the login screen still 502, the last line of /var/log/sw-cp-server/error_log shows:-
Code:
2018/08/20 16:28:55 [error] 33289#0: *9001 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxx.xxx.xxx.xxx:8443", referrer: "https://panel-url.xxx"
I think possibly the update failed, my Linux and Plesk Knowledge is limited so any help is appreciated! I also notice that /run is 100% used. I'm not sure if this is an issue or not!
Code:
ps aux | grep sw-
psaadm 7031 0.0 0.0 325716 540 ? S Jan04 0:08 sw-engine-kv
root 22906 0.0 3.3 511496 33400 ? Ss 16:18 0:00 sw-engine-fpm: master process (/etc/sw-engine/sw-engine-fpm.conf)
root 23891 0.0 0.0 112704 972 pts/0 R+ 16:33 0:00 grep --color=auto sw-
root 33287 0.0 0.0 52432 4 ? Ss Jul24 0:00 sw-cp-server: master process /usr/sbin/sw-cp-serverd -c /etc/sw-cp-server/config
sw-cp-s+ 33289 0.0 0.3 54484 3456 ? S Jul24 0:11 sw-cp-server: worker process