502 error attempting to log into web gui after reboot and latest updates (Compose: 7.2.9 and OMV: 7.4.9-2)

phborg · Oct 7th 2024

Not sure if omv-firstaid or omv-salt stage run deploy is a better way to go about fixing/diagnosing this. It would also be helpfull to know what the relationship of omv-firstaid options and omv-salt commands is...

I have attached the output of

Code

omv-salt stage run deploy > broken.txt
Fetched 114 kB in 1s (104 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
philipb@bs3:~$ sudo omv-salt stage run deploy >broken.txt
[sudo] password for philipb:
[ERROR   ] Command 'blkid' failed with return code: 2
[ERROR   ] retcode: 2
[ERROR   ] Command 'blkid' failed with return code: 2
[ERROR   ] output:
[ERROR   ] Service nut-server is already enabled, and is dead
[ERROR   ] Command '/usr/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r27fa8f7a19554e349045103deb48e085.scope
Job for php8.2-fpm.service failed because the control process exited with error code.
See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for php8.2-fpm.service failed because the control process exited with error code.
See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details.
[ERROR   ] {'out': 'highstate', 'ret': {'debian': {'file_|-configure_apt_sources_list_openmediavault_|-/etc/apt/sources.list.d/openmediavault.list_|-managed': {'changes': {}, 'comment': 'File /etc/apt/sources.list.d/openmediavault.list is in the correct state', 'name': '/etc/apt/sources.list.d/openmediavault.list', 'result': True, '__sls__': 'omv.deploy.apt.10default', '__run_num__': 0, 'start_time': '11:21:16.799260', 'duration': 72.386, '__id__': 'configure_apt_sources_list_openmediavault'}, 'file_|-remove_apt_proxy_|-/etc/apt/apt.conf.d/99openmediavault-proxy_|-absent': {'name': '/etc/apt/apt.conf.d/99openmediavault-proxy', 'changes': {}, 'result': True, 'comment': 'File /etc/apt/apt.conf.d/99openmediavault-proxy is not present', '__sls__': 'omv.deploy.apt.10default', '__run_num__': 1, 'start_time': '11:21:16.871722', 'duration': 0.334, '__id__': 'remove_apt_proxy'}, 'file_|-configure_apt_pref_kernel_backports_|-/etc/apt/preferences.d/openmediavault-kernel-backports.pref_|-managed': {'changes': {}, 'comment': 'File /etc/apt/preferences.d/openmediavault-kernel-backports.pref is in the correct state', 'name': '/etc/apt/preferences.d/openmediavault-kernel-backports.pref', 'result': True, '__sls__': 'omv.deploy.apt.10default', '__run_num__': 2, 'start_time': '11:21:16.872112', 'duration': 63.04, '__id__': 'configure_apt_pref_kernel_backports'}, 'file_|-configure_apt_sources_list_kernel_backports_|-/etc/apt/sources.list.d/openmediavault-kernel-backports.list_|-managed': {'changes': {}, 'comment': 'File /etc/apt/sources.list.d/openmediavault-kernel-backports.list is in the correct state', 'name': '/etc/apt/sources.list.d/openmediavault-kernel-backports.list', 'result': True, '__sls__': 'omv.deploy.apt.10default', '__run_num__': 3, 'start_time': '11:21:16.935224', 'duration': 63.687, '__id__': 'configure_apt_sources_list_kernel_backports'}, 'file_|-remove_apt_sources_list_omv_security_obsolete_|-/etc/apt/sources.list.d/openmediavault-debian-security.list_|-absent': {'name': '/etc/apt/sources.list.d/openmediavault-debian-security.list', 'changes': {}, 'result': True, 'comment': 'File /etc/apt/sources.list.d/openmediavault-debian-security.list is not present', '__sls__': 'omv.deploy.apt.10default', '__run_num__': 4, 'start_time': '11:21:16.999006', 'duration': 0.342, '__id__': 'remove_apt_sources_list_omv_security_obsolete'}, 'file_|-remove_apt_sources_list_security_0_|-/etc/apt/sources.list.d/openmediavault-os-security.list_|-line': {'name': '/etc/apt/sources.list.d/openmediavault-os-security.list', 'changes': {'diff': '--- \n+++ \n@@ -1,2 +1 @@\n-deb [signed-by=/usr/share/keyri

Many more lines...

Display More

Soma · Oct 7th 2024

Quote from phborg

Not sure if omv-firstaid or omv-salt stage run deploy is a better way to go about fixing/diagnosing this

Is there a question anywhere?

Why would you think omv-salt stage run deploy is needed?

The error's showing tell you which commands to run to find better info on what is wrong:

Quote from phborg

Job for php8.2-fpm.service failed because the control process exited with error code.
See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details

phborg · Oct 7th 2024

Quote

Is there a question anywhere?

How about is omv-firstaid option 3 or omv-salt stage run deploy a better first step in fixing web page broken problems?

Quote

Why would you think omv-salt stage run deploy is needed?

Best guess based on other forum posts that this is the first step in diagnosing/ fixing problems. It did give the messages you said to check...

Quote

The error's showing tell you which commands to run to find better info on what is wrong:

Sorry I missed those because of the nut errors above in the output and the volume of output.

I did not see anything obvious in the output of those commands still not sure how to proceed.

Code

 sudo systemctl status php8.2-fpm.service
× php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager
     Loaded: loaded (/lib/systemd/system/php8.2-fpm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2024-10-07 14:09:12 EDT; 1min 28s ago
       Docs: man:php-fpm8.2(8)
    Process: 289182 ExecStart=/usr/sbin/php-fpm8.2 --nodaemonize --fpm-config /etc/php/8.2/fpm/php-fpm.conf (code=exited, status=78)
    Process: 289183 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/8.2/fpm/pool.d/www.conf 82 (code=exited, status=0/SUCCESS)
   Main PID: 289182 (code=exited, status=78)
        CPU: 32ms

Oct 07 14:09:11 bs3 systemd[1]: Starting php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager...
Oct 07 14:09:12 bs3 php-fpm8.2[289182]: [07-Oct-2024 14:09:12] ERROR: unable to bind listening socket for address '/run/php/php8.2-fpm-openmediavault-webgui.sock': No such>
Oct 07 14:09:12 bs3 php-fpm8.2[289182]: [07-Oct-2024 14:09:12] ERROR: FPM initialization failed
Oct 07 14:09:12 bs3 systemd[1]: php8.2-fpm.service: Main process exited, code=exited, status=78/CONFIG
Oct 07 14:09:12 bs3 systemd[1]: php8.2-fpm.service: Failed with result 'exit-code'.
Oct 07 14:09:12 bs3 systemd[1]: Failed to start php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.

Display More

Code

Oct 07 10:02:26 bs3 systemd[1]: Starting php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager...
░░ Subject: A start job for unit php8.2-fpm.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit php8.2-fpm.service has begun execution.
░░ 
░░ The job identifier is 179.
Oct 07 10:02:27 bs3 php-fpm8.2[1279]: [07-Oct-2024 10:02:27] ERROR: unable to bind listening socket for address '/run/php/php8.2-fpm-openmediavault-webgui.sock': No such file or directory (2)
Oct 07 10:02:27 bs3 php-fpm8.2[1279]: [07-Oct-2024 10:02:27] ERROR: FPM initialization failed
Oct 07 10:02:27 bs3 systemd[1]: php8.2-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 php8.2-fpm.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 78.
Oct 07 10:02:27 bs3 systemd[1]: php8.2-fpm.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit php8.2-fpm.service has entered the 'failed' state with result 'exit-code'.
Oct 07 10:02:27 bs3 systemd[1]: Failed to start php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.
░░ Subject: A start job for unit php8.2-fpm.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit php8.2-fpm.service has finished with a failure.
░░ 
░░ The job identifier is 179 and the job result is failed.


Continues repeating

Display More

Soma · Oct 7th 2024

sudo omv-salt deploy run phpfpm

phborg · Oct 11th 2024

I still have not solved this.

sudo omv-salt deploy run phpfpm

returns the same errors. posted again below. Is it possible there is a port conflict and if so what port(s) does the php8.2-fpm service need?

How do I manually stop all omv docker seasons if one is causing a port conflict? ie where is the main compose .yaml file?

Code

----------
          ID: restart_phpfpm_service
    Function: service.running
        Name: php8.2-fpm
      Result: False
     Comment: Job for php8.2-fpm.service failed because the control process exited with error code.
              See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details.
     Started: 15:56:03.840862
    Duration: 193.017 ms
     Changes:   
----------
          ID: monitor_phpfpm_service
    Function: module.run
      Result: False
     Comment: One or more requisite failed: omv.deploy.phpfpm.default.restart_phpfpm_service
     Started: 15:56:04.034375
    Duration: 0.004 ms
     Changes:   

Summary for debian
-------------
Succeeded: 19 (changed=14)
Failed:     2
-------------
Total states run:     21
Total run time:    1.186 s
[ERROR   ] Command '/usr/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r551a95dcad0443d3b7296512868d2d1d.scope
Job for php8.2-fpm.service failed because the control process exited with error code.
See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details.
[ERROR   ] retcode: 1
[ERROR   ] Job for php8.2-fpm.service failed because the control process exited with error code.
See "systemctl status php8.2-fpm.service" and "journalctl -xeu php8.2-fpm.service" for details.

##################################
philipb@bs3:~$ sudo systemctl status php8.2-fpm.service
× php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager
     Loaded: loaded (/lib/systemd/system/php8.2-fpm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2024-10-11 15:56:24 EDT; 22s ago
       Docs: man:php-fpm8.2(8)
    Process: 1483502 ExecStart=/usr/sbin/php-fpm8.2 --nodaemonize --fpm-config /etc/php/8.2/fpm/php-fpm.conf (code=exited, status=78)
    Process: 1483527 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/8.2/fpm/pool.d/www.conf 82 (code=exit>
   Main PID: 1483502 (code=exited, status=78)
        CPU: 33ms

Oct 11 15:56:24 bs3 systemd[1]: Starting php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager...
Oct 11 15:56:24 bs3 php-fpm8.2[1483502]: [11-Oct-2024 15:56:24] ERROR: unable to bind listening socket for address '/run/php/php8.2-fpm-openmedi>
Oct 11 15:56:24 bs3 php-fpm8.2[1483502]: [11-Oct-2024 15:56:24] ERROR: FPM initialization failed
Oct 11 15:56:24 bs3 systemd[1]: php8.2-fpm.service: Main process exited, code=exited, status=78/CONFIG
Oct 11 15:56:24 bs3 systemd[1]: php8.2-fpm.service: Failed with result 'exit-code'.
Oct 11 15:56:24 bs3 systemd[1]: Failed to start php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.

##############################
philipb@bs3:~$ sudo journalctl -xeu php8.2-fpm.service
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit php8.2-fpm.service has finished with a failure.
░░ 
░░ The job identifier is 20330570 and the job result is failed.
Oct 11 15:56:24 bs3 systemd[1]: Starting php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager...
░░ Subject: A start job for unit php8.2-fpm.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit php8.2-fpm.service has begun execution.
░░ 
░░ The job identifier is 20332142.
Oct 11 15:56:24 bs3 php-fpm8.2[1483502]: [11-Oct-2024 15:56:24] ERROR: unable to bind listening socket for address '/run/php/php8.2-fpm-openmedi>
Oct 11 15:56:24 bs3 php-fpm8.2[1483502]: [11-Oct-2024 15:56:24] ERROR: FPM initialization failed
Oct 11 15:56:24 bs3 systemd[1]: php8.2-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 php8.2-fpm.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 78.
Oct 11 15:56:24 bs3 systemd[1]: php8.2-fpm.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit php8.2-fpm.service has entered the 'failed' state with result 'exit-code'.
Oct 11 15:56:24 bs3 systemd[1]: Failed to start php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.
░░ Subject: A start job for unit php8.2-fpm.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit php8.2-fpm.service has finished with a failure.
░░ 
░░ The job identifier is 20332142 and the job result is failed.

Display More

Soma · Oct 11th 2024

Try to change the omv-workbench port to something different (for eg 50000) via omv-firstaid and try again with access with http://LAN_IP:50000

phborg · Oct 16th 2024

I finally found my problem, the fact that my ssh keys were not working should have been a clue...

Somehow I had managed to change the owner of / to a different user. It was probably a typo when changing the owner of one of my docker config directories.

Thanks for attempting to help.

Participate now!