Error "502 Bad Gateway nginx" while entering Web-GUI after upgrading from OMV4 to OMV 5

Raz3r · 27. September 2020

Hello,

I just upgraded OMV form 4 to 5 and thought everything is great. After I finished my work I restart the Server and get the Error

Zitat

502 Bad Gateway nginx

I tried to fix it via omv-firstaid and I tried this solution

Code

omv-salt deploy run nginx
omv-salt deploy run phpfpm

with no success.

The first command "omv-salt deploy run nginx" runs without any error,

the second one gives me this error:

Code

root@NAS:~# omv-salt deploy run phpfpm
NAS.local:
----------
          ID: configure_phpfpm_webgui
    Function: file.managed
        Name: /etc/php/7.3/fpm/pool.d/openmediavault-webgui.conf
      Result: True
     Comment: File /etc/php/7.3/fpm/pool.d/openmediavault-webgui.conf is in the correct state
     Started: 19:00:59.757217
    Duration: 14.12 ms
     Changes:
----------
          ID: prereq_phpfpm_service_monit
    Function: salt.state
      Result: True
     Comment: States ran successfully. Updating NAS.local.
     Started: 19:00:59.772055
    Duration: 335.107 ms
     Changes:
              NAS.local:
              ----------
                        ID: configure_monit_collectd_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-collectd.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-collectd.conf is in the correct state
                   Started: 19:01:00.009540
                  Duration: 5.245 ms
                   Changes:
              ----------
                        ID: configure_monit_filesystem_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-filesystem.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf is in the correct state
                   Started: 19:01:00.014857
                  Duration: 6.356 ms
                   Changes:
              ----------
                        ID: configure_monit_nginx_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-nginx.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-nginx.conf is in the correct state
                   Started: 19:01:00.021286
                  Duration: 4.644 ms
                   Changes:
              ----------
                        ID: configure_monit_nut_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-nut.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-nut.conf is in the correct state
                   Started: 19:01:00.026001
                  Duration: 6.021 ms
                   Changes:
              ----------
                        ID: configure_monit_omv-engined_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-engined.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-engined.conf is in the correct state
                   Started: 19:01:00.032097
                  Duration: 4.467 ms
                   Changes:
              ----------
                        ID: configure_monit_php-fpm_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-phpfpm.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-phpfpm.conf is in the correct state
                   Started: 19:01:00.036638
                  Duration: 4.381 ms
                   Changes:
              ----------
                        ID: remove_monit_proftpd_service
                  Function: file.absent
                      Name: /etc/monit/conf.d/openmediavault-proftpd.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-proftpd.conf is not present
                   Started: 19:01:00.041092
                  Duration: 0.374 ms
                   Changes:
              ----------
                        ID: configure_monit_rrdcached_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-rrdcached.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-rrdcached.conf is in the correct state
                   Started: 19:01:00.041519
                  Duration: 4.425 ms
                   Changes:
              ----------
                        ID: configure_monit_system_service
                  Function: file.managed
                      Name: /etc/monit/conf.d/openmediavault-system.conf
                    Result: True
                   Comment: File /etc/monit/conf.d/openmediavault-system.conf is in the correct state
                   Started: 19:01:00.046019
                  Duration: 9.898 ms
                   Changes:
              ----------
                        ID: configure_default_monit
                  Function: file.managed
                      Name: /etc/default/monit
                    Result: True
                   Comment: File /etc/default/monit is in the correct state
                   Started: 19:01:00.055987
                  Duration: 1.275 ms
                   Changes:
              ----------
                        ID: configure_monit_monitrc
                  Function: file.managed
                      Name: /etc/monit/monitrc
                    Result: True
                   Comment: File /etc/monit/monitrc is in the correct state
                   Started: 19:01:00.057322
                  Duration: 9.173 ms
                   Changes:
              ----------
                        ID: test_monit_config
                  Function: cmd.run
                      Name: monit -t
                    Result: True
                   Comment: Command "monit -t" run
                   Started: 19:01:00.066966
                  Duration: 6.97 ms
                   Changes:
                            ----------
                            pid:
                                17994
                            retcode:
                                0
                            stderr:
                                /etc/monit/conf.d/openmediavault-nut.conf:14: Program does not exist: '/usr/sbin/upsdrvctl'
                            stdout:
                                Control file syntax OK
              ----------
                        ID: reload_monit_service
                  Function: service.running
                      Name: monit
                    Result: True
                   Comment: The service monit is already running
                   Started: 19:01:00.082590
                  Duration: 22.612 ms
                   Changes:

              Summary for NAS.local
              -------------
              Succeeded: 13 (changed=1)
              Failed:     0
              -------------
              Total states run:     13
              Total run time:   85.841 ms
----------
          ID: test_phpfpm_service_config
    Function: cmd.run
        Name: php-fpm7.3 --test
      Result: True
     Comment: Command "php-fpm7.3 --test" run
     Started: 19:01:00.107812
    Duration: 116.479 ms
     Changes:
              ----------
              pid:
                  18002
              retcode:
                  0
              stderr:
                  [27-Sep-2020 19:01:00] NOTICE: configuration file /etc/php/7.3/fpm/php-fpm.conf test is successful
              stdout:
----------
          ID: restart_phpfpm_service
    Function: service.running
        Name: php7.3-fpm
      Result: False
     Comment: Job for php7.3-fpm.service failed because the control process exited with error code.
              See "systemctl status php7.3-fpm.service" and "journalctl -xe" for details.
     Started: 19:01:00.235876
    Duration: 73.895 ms
     Changes:
----------
          ID: monitor_phpfpm_service
    Function: module.run
        Name: monit.monitor
      Result: False
     Comment: One or more requisite failed: omv.deploy.phpfpm.default.restart_phpfpm_service
     Started: 19:01:00.311241
    Duration: 0.003 ms
     Changes:

Summary for NAS.local
------------
Succeeded: 3 (changed=2)
Failed:    2
------------
Total states run:     5
Total run time: 539.604 ms

Alles anzeigen

Output from

Code

systemctl status php7.3-fpm.service

is

Code

● php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-09-27 19:20:38 CEST; 1min 3s ago
     Docs: man:php-fpm7.3(8)
  Process: 19682 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
 Main PID: 19682 (code=exited, status=78)

Sep 27 19:20:38 NAS.local systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
Sep 27 19:20:38 NAS.local php-fpm7.3[19682]: [27-Sep-2020 19:20:38] ERROR: unable to bind listening socket for address '/run/php/php7.3-fpm-openmediavau
lt-webgui.sock': No such file or directory (2)
Sep 27 19:20:38 NAS.local php-fpm7.3[19682]: [27-Sep-2020 19:20:38] ERROR: FPM initialization failed
Sep 27 19:20:38 NAS.local systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
Sep 27 19:20:38 NAS.local systemd[1]: php7.3-fpm.service: Failed with result 'exit-code'.
Sep 27 19:20:38 NAS.local systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.

Alles anzeigen

Raz3r · 27. September 2020

Output from

Code

journalctl -xe

is very long so I only post a part of it

Code

Sep 27 19:01:56 NAS.local systemd[1]: Starting A high performance web server and a reverse proxy server...
-- Subject: A start job for unit nginx.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nginx.service has begun execution.
--
-- The job identifier is 3283.
Sep 27 19:01:57 NAS.local systemd[1]: Started A high performance web server and a reverse proxy server.
-- Subject: A start job for unit nginx.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nginx.service has finished successfully.
--
-- The job identifier is 3283.
Sep 27 19:02:01 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:03 NAS.local collectd[1273]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure:
Connection refused
Sep 27 19:02:03 NAS.local collectd[1273]: read-function of plugin `nut/ups@localhost:3493' failed. Will suspend it for 640.000 s
econds.-
Sep 27 19:02:06 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:11 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:16 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:21 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:26 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:27 NAS.local monit[968]: 'php-fpm' process is not running
Sep 27 19:02:27 NAS.local monit[968]: 'php-fpm' trying to restart
Sep 27 19:02:27 NAS.local monit[968]: 'php-fpm' start: '/bin/systemctl start php7.3-fpm'
Sep 27 19:02:27 NAS.local systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit php7.3-fpm.service has begun execution.
--
-- The job identifier is 3374.
Sep 27 19:02:27 NAS.local php-fpm7.3[18132]: [27-Sep-2020 19:02:27] ERROR: unable to bind listening socket for address '/run/php/php7.3-fpm-openmediavau
lt-webgui.sock': No such file or directory (2)
Sep 27 19:02:27 NAS.local php-fpm7.3[18132]: [27-Sep-2020 19:02:27] ERROR: FPM initialization failed
Sep 27 19:02:27 NAS.local systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit php7.3-fpm.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 78.
Sep 27 19:02:27 NAS.local systemd[1]: php7.3-fpm.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit php7.3-fpm.service has entered the 'failed' state with result 'exit-code'.
Sep 27 19:02:27 NAS.local systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit php7.3-fpm.service has finished with a failure.
--
-- The job identifier is 3374 and the job result is failed.
Sep 27 19:02:31 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:36 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:41 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:46 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:51 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:56 NAS.local upsmon[18023]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 27 19:02:56 NAS.local systemd[1]: nut-monitor.service: Start operation timed out. Terminating.
Sep 27 19:02:56 NAS.local upsmon[18023]: Signal 15: exiting
Sep 27 19:02:56 NAS.local systemd[1]: nut-monitor.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit nut-monitor.service has entered the 'failed' state with result 'timeout'.
Sep 27 19:02:56 NAS.local systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller.
-- Subject: A start job for unit nut-monitor.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nut-monitor.service has finished with a failure.
--
-- The job identifier is 3191 and the job result is failed.
Sep 27 19:02:57 NAS.local monit[968]: 'php-fpm' failed to start (exit status 1) -- '/bin/systemctl start php7.3-fpm': Job for ph
p7.3-fpm.service failed because the control process exited with error code.
                                           See "systemctl status php7.3-fpm.service" and "journalctl -xe" for details.
Sep 27 19:02:57 NAS.local monit[968]: 'nut-server' process is not running
Sep 27 19:02:57 NAS.local monit[968]: 'nut-server' trying to restart
Sep 27 19:02:57 NAS.local monit[968]: 'nut-server' start: '/bin/systemctl start nut-server'
Sep 27 19:02:57 NAS.local systemd[1]: Starting Network UPS Tools - power device driver controller...
-- Subject: A start job for unit nut-driver.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nut-driver.service has begun execution.
--
-- The job identifier is 3556.
Sep 27 19:02:57 NAS.local upsdrvctl[18148]: Can't chdir to /var/run/nut: No such file or directory
Sep 27 19:02:57 NAS.local upsdrvctl[18148]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)
Sep 27 19:02:57 NAS.local upsdrvctl[18148]: USB communication driver 0.33
Sep 27 19:02:57 NAS.local upsdrvctl[18148]: Driver failed to start (exit status=1)
Sep 27 19:02:57 NAS.local upsdrvctl[18148]: Network UPS Tools - UPS driver controller 2.7.4
Sep 27 19:02:57 NAS.local systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit nut-driver.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Sep 27 19:02:57 NAS.local systemd[1]: nut-driver.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit nut-driver.service has entered the 'failed' state with result 'exit-code'.
Sep 27 19:02:57 NAS.local systemd[1]: Failed to start Network UPS Tools - power device driver controller.
-- Subject: A start job for unit nut-driver.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nut-driver.service has finished with a failure.
--
-- The job identifier is 3556 and the job result is failed.
Sep 27 19:02:57 NAS.local systemd[1]: Starting Network UPS Tools - power devices information server...
-- Subject: A start job for unit nut-server.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit nut-server.service has begun execution.
--
-- The job identifier is 3465.
Sep 27 19:02:57 NAS.local upsd[18150]: fopen /var/run/nut/upsd.pid: No such file or directory
Sep 27 19:02:57 NAS.local upsd[18150]: listening on 0.0.0.0 port 3493
Sep 27 19:02:57 NAS.local upsd[18150]: listening on 0.0.0.0 port 3493
Sep 27 19:02:57 NAS.local upsd[18150]: Can't chdir to /var/run/nut: No such file or directory
Sep 27 19:02:57 NAS.local upsd[18150]: Can't chdir to /var/run/nut: No such file or directory
Sep 27 19:02:57 NAS.local upsd[18150]: Network UPS Tools upsd 2.7.4
Sep 27 19:02:57 NAS.local systemd[1]: nut-server.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support

Alles anzeigen

I hope anyone can help.

Thanks in advance

gderf · 27. September 2020

Try running these commands:

Code

omv-salt deploy run nginx
omv-salt deploy run phpfpm

Raz3r · 27. September 2020

Thank you for your fast Answer but I already did this. The second command generates an error as you see above.

Raz3r · 30. September 2020

Nobody an Idea?

votdev · 30. September 2020

The error /etc/monit/conf.d/openmediavault-nut.conf:14: Program does not exist: '/usr/sbin/upsdrvctl' indicates the usrmerge has not been executed during the OS upgrade.

See RE: Issues with UPS-NUT

Running apt-get install usrmerge should fix the issue.

Raz3r · 30. September 2020

Leider nein, die Meldung war, dass usrmerge bereits vorhanden und installiert ist. Es ist nach wie vor so, dass alle Dienste laufen ich aber nicht auf die Web-GUI zugreifen kann. Es muss irgendwie mit php zusammenhängen, ich hab allerdings keine Ahnung, wie ich weitermachen soll.

in den php-logs bekomme ich die Meldungen

Code

unable to bind listening socket for address '/run/php/php7.0-fpm.sock': No such file or directory (2)

Code

unable to bind listening socket for address '/run/php/php7.3-fpm-openmediavault-webgui.sock': No such file or directory (2)

Ich bin so frei und antworte Dir auf Deutsch, falls Dir Englisch lieber ist, einfach Bescheid geben.

Raz3r · 30. September 2020

Ich habe es nun hinbekommen, dass die WebGUI wieder funktioniert. Ich habe aus einer OMV-VM die php genommen und in var und run gepackt. Zumindest bis zu einem Neustart funktioniert es jetzt wieder. Vielleicht kann ja trotzdem noch jemand helfen, das Problem dauerhaft zu lösen.

votdev · 1. Oktober 2020

Kannst Du mal bitte folgende Befehle ausführen und die Ausgaben hier posten.

Code

# dpkg -l | grep php
# apt-cache policy php7.3-cgi

Hast Du schon mal folgendes probiert apt-get install --reinstall php7.3-cgi

Raz3r · 1. Oktober 2020

Danke für Deine Hilfe.

Auch die Ausführung des Befehls apt-get install --reinstall php7.3-cgi brachte keine Verbesserung.

dpkg -l | grep php

gibt zu viele Zeichen aus, ich habe die Ausgabe als .txt angehängt.

Die Ausgabe von

apt-cache policy php7.3-cgi

ist

Code

apt-cache policy php7.3-cgi
php7.3-cgi:  Installiert:           7.3.19-1~deb10u1  Installationskandidat: 7.3.19-1~deb10u1  Versionstabelle: *** 7.3.19-1~deb10u1 500        500 http://ftp.de.debian.org/debian buster/main amd64 Packages        500 http://security.debian.org/debian-security buster/updates/main amd64 Packages        100 /var/lib/dpkg/status

votdev · 1. Oktober 2020

Wie sieht die Ausgabe von systemctl status nginx aus?

Raz3r · 1. Oktober 2020

Ich habe mich nun dazu entschlossen, das System neu aufzusetzen. Es waren einfach zu viele Baustellen und ich konnte mich nicht mehr darauf verlassen. Ich habe soweit alles wieder am Laufen aber Probleme mit meinen sharedfolders. Hierzu werde ich aber ein neues Thema erstellen. Vielen Dank für Deine Hilfe.

Error "502 Bad Gateway nginx" while entering Web-GUI after upgrading from OMV4 to OMV 5

Raz3r 27. September 2020

Jetzt mitmachen!