Problems after update to latest 5.6.23

Hi,

a long running +/- 20 Days 5.6 omv server was updated to the latest version in question and now i cannot access the web interface.

The nginx error log shows:

2022/01/12 15:30:46 [crit] 8285#8285: *3 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client:

as there are a lot of dfferent "solutions" around here abou web interface issues, i want to ask first what to do, cause everything else seems to work fine. I have nothing changed, only did the install of the latest update.

What should i do now?

[EDIT=Solution Found]

• the problem was drilled down to the directory /run/php which wasn't created during boot time
• several steps here in the thread didn't helped
• found out that the flashram plugin was the culprit
• removing the plugin solved the problem. During boot the directory was created again
• reinstalling the plugin after reboot worked also
• so everything is working with the plugin running again

[/EDIT]

oh didn't expect that this is such an easy one.....

.....created directory /run/php/

created file php7.3-fpm-openmediavault-webgui.sock

web gui access restored.

Huh?

I know i'm the greatest.. :-)... but why was this happening in the first place?

now the only remaining issue, is that the UPS plugin won't run anymore. Cannot connect to the UPS. Also this was running for a long time and i've nothing changed.....

Zitat von Zoki

What is the output of systemctl status php7.3-fpm

This should fix it:

omv-salt deploy run phpfpm

omv-salt deploy run nginx

Alles anzeigen

● 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: active (running) since Wed 2022-01-12 15:52:43 CET; 7min ago

Docs: man:php-fpm7.3(8)

Main PID: 21416 (php-fpm7.3)

Status: "Processes active: 0, idle: 7, Requests: 350, slow: 0, Traffic: 0.3req/sec"

Tasks: 8 (limit: 4915)

Memory: 29.5M

CGroup: /system.slice/php7.3-fpm.service

├─ 1616 php-fpm: pool openmediavault-webgui

├─ 7920 php-fpm: pool openmediavault-webgui

├─ 9827 php-fpm: pool openmediavault-webgui

├─11355 php-fpm: pool openmediavault-webgui

├─21416 php-fpm: master process (/etc/php/7.3/fpm/php-fpm.conf)

├─21417 php-fpm: pool www

├─21418 php-fpm: pool www

└─28959 php-fpm: pool openmediavault-webgui

omv-salt deploy run phpfpm

omv-salt deploy run nginx

i have also run. the above commands.

So as mentioned in an earlier post web gui was already restored. Your help is really appreciated and i've did your steps, i've still web gui acces, but also still no UPS connection. I cannot enable the plugin anymore:

failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color nut 2>&1' with exit code '1': debian: ---------- ID: configure_nut_nut_conf Function: file.managed Name: /etc/nut/nut.conf Result: True Comment: File /etc/nut/nut.conf is in the correct state Started: 16:02:55.653248 Duration: 30.739 ms Changes: ---------- ID: configure_nut_ups_conf Function: file.managed Name: /etc/nut/ups.conf Result: True Comment: File /etc/nut/ups.conf is in the correct state Started: 16:02:55.684133 Duration: 9.073 ms Changes: ---------- ID: configure_nut_upsd_conf Function: file.managed Name: /etc/nut/upsd.conf Result: True Comment: File /etc/nut/upsd.conf is in the correct state Started: 16:02:55.693338 Duration: 11.662 ms Changes: ---------- ID: configure_nut_upsd_users Function: file.managed Name: /etc/nut/upsd.users Result: True Comment: File /etc/nut/upsd.users updated Started: 16:02:55.705130 Duration: 12.877 ms Changes: ---------- diff: --- +++ @@ -1,13 +1,13 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. [admin] -password = cptOnP1hAak4IzJZ +password = M72H5GST1UPpVnXT actions = set actions = fsd instcmds = ALL [monmaster] -password = K4tpR9wnO28tAfvf +password = GsbBCcj4K07DTz06 upsmon master [markus] password = KatzeLula6 ---------- ID: configure_nut_upsmon_conf Function: file.managed Name: /etc/nut/upsmon.conf Result: True Comment: File /etc/nut/upsmon.conf updated Started: 16:02:55.718138 Duration: 19.364 ms Changes: ---------- diff: --- +++ @@ -1,6 +1,6 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. -MONITOR ups 1 monmaster K4tpR9wnO28tAfvf master +MONITOR ups 1 monmaster GsbBCcj4K07DTz06 master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "/sbin/upssched" ---------- ID: configure_nut_upssched_conf Function: file.managed Name: /etc/nut/upssched.conf Result: True Comment: File /etc/nut/upssched.conf is in the correct state Started: 16:02:55.737654 Duration: 10.207 ms Changes: ---------- ID: configure_nut_default_upssched_cmd Function: file.managed Name: /etc/default/upssched-cmd Result: True Comment: File /etc/default/upssched-cmd is in the correct state Started: 16:02:55.747991 Duration: 1.89 ms Changes: ---------- ID: remove_nut_udev_serialups_rule Function: file.absent Name: /etc/udev/rules.d/99-openmediavault-nut-serialups.rules Result: True Comment: File /etc/udev/rules.d/99-openmediavault-nut-serialups.rules is not present Started: 16:02:55.750008 Duration: 0.585 ms Changes: ---------- ID: start_nut_driver_service Function: service.running Name: nut-driver Result: False Comment: Job for nut-driver.service failed because the control process exited with error code. See "systemctl status nut-driver.service" and "journalctl -xe" for details. Started: 16:02:55.768027 Duration: 91.673 ms Changes: ---------- ID: start_nut_server_service Function: service.running Name: nut-server Result: False Comment: Job for nut-server.service failed because the control process exited with error code. See "systemctl status nut-server.service" and "journalctl -xe" for details. Started: 16:02:55.969803 Duration: 109.016 ms Changes: ---------- ID: monitor_nut_server_service Function: module.run Result: True Comment: monit.monitor: True Started: 16:02:56.082173 Duration: 19.338 ms Changes: ---------- monit.monitor: True ---------- ID: start_nut_monitor_service Function: service.running Name: nut-monitor Result: False Comment: Job for nut-monitor.service failed because a timeout was exceeded. See "systemctl status nut-monitor.service" and "journalctl -xe" for details. Started: 16:03:44.917696 Duration: 90248.706 ms Changes: ---------- ID: monitor_nut_monitor_service Function: module.run Result: True Comment: monit.monitor: True Started: 16:05:15.166748 Duration: 14.674 ms Changes: ---------- monit.monitor: True Summary for debian ------------- Succeeded: 10 (changed=4) Failed: 3 ------------- Total states run: 13 Total run time: 90.580 s

-- An ExecStart= process belonging to unit nut-server.service has exited.

--

-- The process' exit code is 'exited' and its exit status is 1.

Jan 12 16:27:31 omvserver systemd[1]: nut-server.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- The unit nut-server.service has entered the 'failed' state with result 'exit-code'.

Jan 12 16:27:31 omvserver systemd[1]: Failed to start Network UPS Tools - power devices information server.

-- Subject: A start job for unit nut-server.service has failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- A start job for unit nut-server.service has finished with a failure.

--

-- The job identifier is 18278 and the job result is failed.

Jan 12 16:27:36 omvserver upsmon[11113]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:27:41 omvserver upsmon[11113]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:27:46 omvserver upsmon[11113]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:27:49 omvserver sudo[14319]: root : TTY=pts/0 ; PWD=/run ; USER=root ; COMMAND=/usr/bin/journalctl -xe

Jan 12 16:27:49 omvserver sudo[14319]: pam_unix(sudo:session): session opened for user root by (uid=0)

● nut-driver.service - Network UPS Tools - power device driver controller

Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled)

Active: failed (Result: exit-code) since Wed 2022-01-12 16:27:31 CET; 1min 18s ago

Process: 13718 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAILURE)

Jan 12 16:27:31 omvserver systemd[1]: Starting Network UPS Tools - power device driver controller...

Jan 12 16:27:31 omvserver upsdrvctl[13718]: Can't chdir to /var/run/nut: No such file or directory

Jan 12 16:27:31 omvserver upsdrvctl[13718]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)

Jan 12 16:27:31 omvserver upsdrvctl[13718]: USB communication driver 0.33

Jan 12 16:27:31 omvserver upsdrvctl[13718]: Driver failed to start (exit status=1)

Jan 12 16:27:31 omvserver upsdrvctl[13718]: Network UPS Tools - UPS driver controller 2.7.4

Jan 12 16:27:31 omvserver systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE

Jan 12 16:27:31 omvserver systemd[1]: nut-driver.service: Failed with result 'exit-code'.

Jan 12 16:27:31 omvserver systemd[1]: Failed to start Network UPS Tools - power device driver controller.

● nut-server.service - Network UPS Tools - power devices information server

Loaded: loaded (/lib/systemd/system/nut-server.service; disabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Wed 2022-01-12 16:29:05 CET; 22s ago

Process: 19948 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE)

Jan 12 16:29:05 omvserver upsd[19948]: listening on 0:0:0:0:0:0:0:0 port 3493

Jan 12 16:29:05 omvserver upsd[19948]: not listening on 0.0.0.0 port 3493

Jan 12 16:29:05 omvserver upsd[19948]: listening on 0:0:0:0:0:0:0:0 port 3493

Jan 12 16:29:05 omvserver upsd[19948]: Can't chdir to /var/run/nut: No such file or directory

Jan 12 16:29:05 omvserver upsd[19948]: Network UPS Tools upsd 2.7.4

Jan 12 16:29:05 omvserver upsd[19948]: not listening on 0.0.0.0 port 3493

Jan 12 16:29:05 omvserver upsd[19948]: Can't chdir to /var/run/nut: No such file or directory

Jan 12 16:29:05 omvserver systemd[1]: nut-server.service: Control process exited, code=exited, status=1/FAILURE

Jan 12 16:29:05 omvserver systemd[1]: nut-server.service: Failed with result 'exit-code'.

Jan 12 16:29:05 omvserver systemd[1]: Failed to start Network UPS Tools - power devices information server.

● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller

Loaded: loaded (/lib/systemd/system/nut-monitor.service; disabled; vendor preset: enabled)

Active: activating (start) since Wed 2022-01-12 16:29:38 CET; 26s ago

Process: 21186 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)

Tasks: 2 (limit: 4915)

Memory: 880.0K

CGroup: /system.slice/nut-monitor.service

├─21187 /lib/nut/upsmon

└─21188 /lib/nut/upsmon

Jan 12 16:29:38 omvserver upsmon[21188]: Communications with UPS ups lost

Jan 12 16:29:38 omvserver upssched[21193]: Executing command: notify

Jan 12 16:29:43 omvserver upsmon[21188]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:29:43 omvserver upsmon[21188]: UPS ups is unavailable

Jan 12 16:29:43 omvserver upssched[21400]: Executing command: notify

Jan 12 16:29:43 omvserver upssched-cmd[21404]: Communications with the UPS ups cannot be established

Jan 12 16:29:48 omvserver upsmon[21188]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:29:53 omvserver upsmon[21188]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:29:58 omvserver upsmon[21188]: UPS [ups]: connect failed: Connection failure: Connection refused

Jan 12 16:30:03 omvserver upsmon[21188]: UPS [ups]: connect failed: Connection failure: Connection refused

____

so i would say there seems to be a problem .

Thanks for your help

now it seems there is more broken than i first discovered. Docker is working, KVM is not working. Oh well.....

i've rebooted before deleting the nut plugin. The plugin as disabled.

After reboot i'm back to the initial error (see post one). Neither your salt commands nor my folder creating in /run/php are working after reboot.

Sorry, to clarify: after reboot your commands didn't help

recreating the folder bin /run did help. Then Web Gui is back. But this cannot be the solution on every boot

I have altered the topic, as the problems add up after digging deeper into the system

- VMs not starting error is "Unable to open /dev/net/tun"

- php 7.3 has errors ... omv Webinterface only runs after creating a php folder unter /run

- nut plugin not starting anymore (plugin removed now, without solving anything)

have DELL 430 server running with standard install procedure (USB Stick)

done every update since initial install 9 months ago. Everything was working until 5.6.23

have docker and KVM running natively via OMVextra (no proxmox)

What elese can i provide to help you to help me? I'm also lost....

Zitat von Zoki

The error message is here: Can't chdir to /var/run/nut: No such file or directory

but why? ls -l /var/run

i've temporarily removed the nut plugin, as the other two problems: No WebGui and no running KVM / VMs are much more important. So i have one topic less to dig in for now.

trying to restore a DD full backup of the system drive from yesterday to a new usb drive now.

Never did this. Hope i get it right

i need further help here: i have used the backup and have both a image backup with dd and a file backup.

Now i've tried to restore the image to a identical new usb drive with this command (mac osx)

sudo dd if=./backup-omv-12-Jan-2022_00-00-01.ddfull of=/dev/rdisk2s1 bs=1m

but the usb drive isn't bootable.

Can someone tell me how to use the data from the backup plugin to create a new usb drive?

yes osx and yes partition. So you're right, doesn't work. _I just struggle to find a clear procedure here in the forum to restore either the files or the image to a new usb drive. I know now that i should have used clonezilla but that wasn't clear to me back then when i've setup the backup. I have now dd images. So i need a procedure for that.

i have rdiskX and diskX. I guess "r" for raw. Does it mather which one i use?