502 bad gateway problem

Tempest

Basic Pleskian
Username:

TITLE

502 bad gateway problem

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

debian 10

PROBLEM DESCRIPTION

Hi,
It looks like I'm stuck with a 502 admin login page only giving me option to log in to the repair kit, and I cannot log in to that either.

via ssh it's not possible to restart sw-cp-server

the journalctl mentions license problem, but I do have a valid license.

Is there something obvious I'm missing?

STEPS TO REPRODUCE

when I run journalctl -xe

ACTUAL RESULT

~$ journalctl -xe


-- The process' exit code is 'exited' and its exit status is 1.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: imunify-agent-proxy.service: Failed with result 'exit-code'.


-- Subject: Unit failed


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- The unit imunify-agent-proxy.service has entered the 'failed' state with result 'exit-code'.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc+


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc+


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: plesk-web-socket.service: Main process exited, code=exited, status=1/FAILURE


-- Subject: Unit process exited


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- An ExecStart= process belonging to unit plesk-web-socket.service has exited.


--


-- The process' exit code is 'exited' and its exit status is 1.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: plesk-web-socket.service: Failed with result 'exit-code'.


-- Subject: Unit failed


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- The unit plesk-web-socket.service has entered the 'failed' state with result 'exit-code'.


lines 3485-3507/3507 (END)


-- The process' exit code is 'exited' and its exit status is 1.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: imunify-agent-proxy.service: Failed with result 'exit-code'.


-- Subject: Unit failed


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- The unit imunify-agent-proxy.service has entered the 'failed' state with result 'exit-code'.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /usr


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /usr


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: plesk-web-socket.service: Main process exited, code=exited, status=1/FAILURE


-- Subject: Unit process exited


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- An ExecStart= process belonging to unit plesk-web-socket.service has exited.


--


-- The process' exit code is 'exited' and its exit status is 1.


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net systemd[1]: plesk-web-socket.service: Failed with result 'exit-code'.


-- Subject: Unit failed


-- Defined-By: systemd


-- Support: Debian -- User Support


--


-- The unit plesk-web-socket.service has entered the 'failed' state with result 'exit-code'.

EXPECTED RESULT

have a working Plesk
being able to log in to Plesk again

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
unfortunately it hasn't.
It actually was triggered by a reboot. But I tried again, also using a snapshot from before it happened. none worked. Another thing is Plesk couldn't update since August.
 
Hi, @Tempest . The errors you get:

Code:
Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /usr


Nov 28 03:29:19 vps-17cc9899.vps.ovh.net sw-engine-pleskrun[27588]: /usr/bin/sw-engine: /usr/lib/x86_64-linux-gnu/c++-plesk-13.3.0/lib64/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /usr

could be due to package corruptions, duplicate packages, repository misconfiguration, etc. I can't easily identify the exact cause for the issue. If you have the option, I would suggest opening a ticket with Plesk support for further investigation with server access.

What you can try removing sw-engine and re-installing it according to:

 
Hi @Sebahat.hadzhi, thanks that was helpful. Not out of the woods yet.

It looks like the Plesk version installed is 18.0.72:
cat /usr/local/psa/version
18.0.72 Debian 10.0 1800250915.05


but the sw-engine version installed is from 18.0.71:
dpkg -l | grep sw-engine
ii sw-engine 7.71.1-debian.10.250709.0854 amd64 Plesk panel interpreter


so, I tried to remove that and install the one from 18.0.72 as per the article link you posted.
But during installation 5 libraries dependancies mismatched as being from the previous version:
sudo dpkg -i sw-engine_7.72.1-debian.10.250807.1639_amd64.deb
Selecting previously unselected package sw-engine.
(Reading database ... 103952 files and directories currently installed.)
Preparing to unpack sw-engine_7.72.1-debian.10.250807.1639_amd64.deb ...
Unpacking sw-engine (7.72.1-debian.10.250807.1639) ...
dpkg: dependency problems prevent configuration of sw-engine:
sw-engine depends on libaps (>= 1.0.17); however:
Version of libaps on system is 1.0.16-debian.10.250709.0854.
sw-engine depends on plesk-lmlib (>= 0.2.8); however:
Version of plesk-lmlib on system is 0.2.7-debian.10.250709.0854.
sw-engine depends on plesk-libboost-regex1.88; however:
Package plesk-libboost-regex1.88 is not installed.
sw-engine depends on plesk-libboost-serialization1.88; however:
Package plesk-libboost-serialization1.88 is not installed.
sw-engine depends on plesk-libboost-thread1.88; however:
Package plesk-libboost-thread1.88 is not installed.
dpkg: error processing package sw-engine (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
sw-engine



Would you have advice on the best way to mix the mismatch?
 
Back
Top