Issue Unable to access to my Plesk interface (502 Bad Gateway)

[Tomulus06]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

Plesk Obsidian 18.0.60.0

Hi,

I can no longer access my Plesk interface since I restarted my server. I have the following error: 502 Bad Gateway.

The repair kit tells me that the sw-engine.service is stopped. I tried to restart my server but the error persists. When I restart sw-engine.service, the process stops immediately.

I couldn't find a solution that works in my case on the forum. Here are my different logs:

- systemctl status sw-engine.service :

sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/usr/lib/systemd/system/sw-engine.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/sw-engine.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-04-26 14:02:14 UTC; 4s ago
Process: 5814 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 5813 ExecStart=/usr/sbin/sw-engine-fpm --fpm-config /etc/sw-engine/sw-engine-fpm.conf -c /usr/local/psa/admin/conf/php.ini --nodaemonize --pid /run/sw-engine.pid (code=exited, status=1/FAILURE)
Main PID: 5813 (code=exited, status=1/FAILURE)
CGroup: /system.slice/sw-engine.service

Failed to start Startup script for Panel sw-engine.
Unit sw-engine.service entered failed state.
sw-engine.service failed.

- journalctl -xe :

-- Subject: Unit plesk-web-socket.service has finished shutting down
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished shutting down.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Started Plesk Web Socket Service.
-- Subject: Unit plesk-web-socket.service has finished start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished starting up.
--
-- The start-up result is done.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_filesystem-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_regex-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_thread-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_serialization-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-fpm[6844]: /usr/sbin/sw-engine-fpm: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: sw-engine.service: main process exited, code=exited, status=1/FAILURE
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_filesystem-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_regex-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_thread-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_serialization-plesk.so.1.84.0)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page sw-engine-pleskrun[6845]: /usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Failed to start Startup script for Panel sw-engine.
-- Subject: Unit sw-engine.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit sw-engine.service has failed.
--
-- The result is failed.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Unit sw-engine.service entered failed state.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: sw-engine.service failed.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: plesk-web-socket.service: main process exited, code=exited, status=1/FAILURE
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: Unit plesk-web-socket.service entered failed state.
Apr 26 14:07:13 exciting-banach.51-75-93-252.plesk.page systemd[1]: plesk-web-socket.service failed.

thanks !

 

[Kaspar]

That looks serious. I wish I had a solution, best advice I have is to contact the Plesk support team if it's urgent. They can investigate the issue on your server.