Admin Panel: Error 502 Bad Gateway after Update 1.4.3

**Revi** · Apr 21st 2017

The update installation from version 1.3.7 to 1.4.3 broke down with an error supposedly at the end (screenshot).
Even after several restarts the Admin Panel at the URL (https://admin.srv.revicomp.de:4443/) is unreachable by: 502 Bad Gateway nginx

Please help

**UncleJ** · Apr 22nd 2017

Hello Revi,

please remember the reporting rules. Without further information it is hard to help.

Regards Jörg

**Nuxwin** · Apr 22nd 2017

@Revi

Without further information we cannot help you. Output of service imscp_panel status?

If you cannot figure out alone, give us acess to your server.

**Revi** · Apr 22nd 2017

Dear Nuxwin and UncleJ ,

thanks for your patience, information and Engagement.

I searched in different logfiles and collected the hopefull needed information for you.

So here is what i found out:

Code

root@srv:~# cat /etc/debian_version
8.7 Codename: jessie
The Logfile /var/logs/imscp_panel.log is empty
root@srv:~# php -v
PHP 5.6.30-10+0~20170412071212.32+jessie~1.gbp3dd061 (cli)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
root@srv:~# service imscp_panel status
? imscp_panel.service - PHP FastCGI process Manager Daemon for i-MSCP FrontEnd
Loaded: loaded (/etc/systemd/system/imscp_panel.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-04-22 13:37:05 CEST; 4h 51min ago
Main PID: 513 (code=exited, status=203/EXEC)
Apr 22 13:37:05 srv systemd[1]: Starting PHP FastCGI process Manager Daemon for i-MSCP FrontEnd...
Apr 22 13:37:05 srv systemd[1]: imscp_panel.service: main process exited, code=exited, status=203/EXEC
Apr 22 13:37:05 srv systemd[1]: Failed to start PHP FastCGI process Manager Daemon for i-MSCP FrontEnd.
Apr 22 13:37:05 srv systemd[1]: Unit imscp_panel.service entered failed state.
root@srv:~# service imscp_panel start
Job for imscp_panel.service failed. See 'systemctl status imscp_panel.service' and 'journalctl -xn' for details.
root@srv:~# systemctl status imscp_panel.service
? imscp_panel.service - PHP FastCGI process Manager Daemon for i-MSCP FrontEnd
Loaded: loaded (/etc/systemd/system/imscp_panel.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-04-22 18:28:41 CEST; 29s ago
Process: 6482 ExecStart=/usr/local/sbin/imscp_panel --nodaemonize --fpm-config /usr/local/etc/imscp_panel/php-fpm.conf -c /usr/local/etc/imscp_panel/php.ini (code=exited, status=203/EXEC)
Main PID: 6482 (code=exited, status=203/EXEC)
Apr 22 18:28:41 srv systemd[1]: imscp_panel.service: main process exited, code=exited, status=203/EXEC
Apr 22 18:28:41 srv systemd[1]: Failed to start PHP FastCGI process Manager Daemon for i-MSCP FrontEnd.
Apr 22 18:28:41 srv systemd[1]: Unit imscp_panel.service entered failed state.
root@srv:~# journalctl -xn
-- Logs begin at Sat 2017-04-22 13:37:01 CEST, end at Sat 2017-04-22 18:29:40 CEST. --
Apr 22 18:29:17 srv authdaemond[604]: restarting authdaemond children
Apr 22 18:29:17 srv authdaemond[604]: modules="authmysql authpam", daemons=5
Apr 22 18:29:17 srv authdaemond[604]: Uninstalling authmysql
Apr 22 18:29:17 srv authdaemond[604]: Uninstalling authpam
Apr 22 18:29:17 srv authdaemond[604]: Installing libauthmysql
Apr 22 18:29:17 srv postfix/smtpd[6489]: disconnect from unknown[80.82.70.210]
Apr 22 18:29:17 srv authdaemond[604]: Installation complete: authmysql
Apr 22 18:29:17 srv authdaemond[604]: Installing libauthpam
Apr 22 18:29:17 srv authdaemond[604]: Installation complete: authpam
Apr 22 18:29:40 srv sshd[6496]: Received disconnect from 221.229.162.204: 11: [preauth]

Display More

Beside this I sent an eMail to Nuxwin for the chance that you would ckeck some things at the server yourself

I thank you a lot!

Greetings from Bonn, Germany,
Revi

**Revi** · Apr 23rd 2017

@Nuxwin worked hard on my Server to find and resolve the problem

However this could happen there was a bad symlink for the panel PHP binary

Just about the history of this Server:
Fresh Installation with Debian Jessie 8 and i-mscp 1.2.17 in 03/2016
Update to i-mscp 1.3.7 in 11/2017
Update to i-mscp 1.4.3 yesterday.

I got the advice from @Nuxwin to update more often

I thank you a lot for your hours

Admin Panel: Error 502 Bad Gateway after Update 1.4.3

Share

Daily visitors