Resolved Plesk is showing 502 bad gateway error on login page

[Hassaan]

Plesk is not showing Login page of administrator panel. The issue seems like with `sw-engine`. Outputs are following with commands.



`service sw-engine start` output

Starting sw-engine (via systemctl): Job for sw-engine.service failed because the control process exited with error code. See "systemctl status sw-engine.service" and "journalctl -xe" for details.


`systemctl status sw-engine.service` output

● sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/usr/lib/systemd/system/sw-engine.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-03-03 20:38:01 PKT; 1min 31s ago
Process: 30789 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 30787 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=127)
Main PID: 30787 (code=exited, status=127)

Mar 03 20:38:01 ns503772.ip-192-99-100.net systemd[1]: Starting Startup script for Panel sw-engine...
Mar 03 20:38:01 ns503772.ip-192-99-100.net sw-engine-fpm[30787]: /usr/sbin/sw-engine-fpm: error while loading shared libraries: libl...ctory
Mar 03 20:38:01 ns503772.ip-192-99-100.net systemd[1]: sw-engine.service: main process exited, code=exited, status=127/n/a
Mar 03 20:38:01 ns503772.ip-192-99-100.net systemd[1]: Failed to start Startup script for Panel sw-engine.
Mar 03 20:38:01 ns503772.ip-192-99-100.net systemd[1]: Unit sw-engine.service entered failed state.
Mar 03 20:38:01 ns503772.ip-192-99-100.net systemd[1]: sw-engine.service failed.
Hint: Some lines were ellipsized, use -l to show in full.


`service psa start` output


Starting sw_engine service... failed
Starting sw_cp_server service... already started
Starting mysql service... already started
Starting named service... already started
Starting mailer service... already started
Starting spamfilter service... not installed
Starting drweb service... unused
Starting tomcat service... not installed
Starting apache service... already started
Starting xinetd service... already started

 

[Bitpalast]

Mar 03 20:38:01 ns503772.ip-192-99-100.net sw-engine-fpm[30787]: /usr/sbin/sw-engine-fpm: error while loading shared libraries: libl...ctory

Unfortunately, that is exactly the line that is interesting. What is in the ellipsis libl...ctory?

 

[Hassaan]

Unfortunately, that is exactly the line that is interesting. What is in the ellipsis libl...ctory?

what is the solution sir? Can you help in fixing this error?

 

[Bitpalast]

Please provide full error message line. Exactly the interesting part where the problematic library is mentioned is omitted in your output. Widen your SSH window to see the rest or take a look at your log files. The error message will be included in the logs, too.

 

[Hassaan]

Sure, full output is following

[root@ns503772 ~]# systemctl status sw-engine.service -l
● sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/usr/lib/systemd/system/sw-engine.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-03-03 20:40:39 PKT; 2h 32min ago
Process: 3710 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 3708 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=127)
Main PID: 3708 (code=exited, status=127)

Mar 03 20:40:39 ns503772.ip-192-99-100.net systemd[1]: Starting Startup script for Panel sw-engine...
Mar 03 20:40:39 ns503772.ip-192-99-100.net sw-engine-fpm[3708]: /usr/sbin/sw-engine-fpm: error while loading shared libraries: liblog4cplus-1.1.so.9: cannot open shared object file: No such file or directory
Mar 03 20:40:39 ns503772.ip-192-99-100.net systemd[1]: sw-engine.service: main process exited, code=exited, status=127/n/a
Mar 03 20:40:39 ns503772.ip-192-99-100.net systemd[1]: Failed to start Startup script for Panel sw-engine.
Mar 03 20:40:39 ns503772.ip-192-99-100.net systemd[1]: Unit sw-engine.service entered failed state.
Mar 03 20:40:39 ns503772.ip-192-99-100.net systemd[1]: sw-engine.service failed.

Please provide full error message line. Exactly the interesting part where the problematic library is mentioned is omitted in your output. Widen your SSH window to see the rest or take a look at your log files. The error message will be included in the logs, too.

 

[Bitpalast]

Please refer to the solution provided in this thread:
https://talk.plesk.com/threads/httpdmng-liblog4cplus-1-1-so-9-cannot-open-shared-object-file.341347/