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
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