I was running OMV 6.1.1-1 (Shaitan) with Nut plugin openmediavault-nut 6.0.1-1.
This morning, I went to apply updates and after a reboot the nut plugin stopped working.
I received this email from the system:
Host: pinas
Date: Fri, 23 Dec 2022 07:32:18
Service: nut-monitor
Event: Execution failed
Description: failed to start (exit status 4) -- '/bin/systemctl start nut-monitor': Failed to start nut-monitor.service: Transaction for nut-monitor.service/start is destructive (systemd-sysctl.service has 'stop' job queued, but 'start' is included in transaction).
See system logs and 'systemctl status nut-monitor.service' for details.
and
Host: pinas
Date: Fri, 23 Dec 2022 07:32:17
Service: nut-monitor
Event: Does not exist
Description: process is not running
This triggered the monitoring system to: restart
I then SSH'd into the OMV system and ran:
admin@pinas:~$ sudo upsd apc-server@192.168.73.28
upsd disabled, please adjust the configuration to your needs
Then set MODE to a suitable value in /etc/nut/nut.conf to enable it
Things I tried to get it to resolve:
- Disabling the nut service, rebooting, re-enabling the nut service.
- Uninstalling the nut plugin, rebooting, reinstalling the nut plugin, reconfiguring it.
- Multiple reboots.
These steps still resulted in the above emails and upsd messages.
I then used DD with a LiveBoot and DD (backup image was 13 days old thank goodness) to restore my system back to a working state.
When the system was in a "bad" state after the updates (and reboot) I did a status on a few of these services:
admin@pinas:/etc/nut$ sudo systemctl status nut-monitor
● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-12-23 07:43:27 CST; 2min 37s ago
Main PID: 10235 (upsmon)
Tasks: 2 (limit: 8982)
CPU: 27ms
CGroup: /system.slice/nut-monitor.service
├─10234 /lib/nut/upsmon
└─10235 /lib/nut/upsmon
admin@pinas:/etc/nut$ sudo systemctl status nut-client
● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-12-23 07:43:27 CST; 2min 56s ago
Main PID: 10235 (upsmon)
Tasks: 2 (limit: 8982)
CPU: 28ms
CGroup: /system.slice/nut-monitor.service
├─10234 /lib/nut/upsmon
└─10235 /lib/nut/upsmon
These were the upgrades that I applied right before the problem happened:
The following packages will be upgraded:
containerd.io libksba8 openmediavault
shaitan/main arm64 openmediavault all 6.1.2-1 [2610 kB]
bullseye/stable arm64 containerd.io arm64 1.6.14-1 [19.9 MB]
bullseye-security/main arm64 libksba8 arm64 1.5.0-3+deb11u2 [115 kB]
Looking at details on the packages my guess is that openmediavault 6.1.2-1 would be the source of the break with the plugin.
Here was my system info prior to update:
System Information
Hostname: pinas
Version: 6.1.1-1 (Shaitan)
Processor: BCM2835
Kernel: Linux 5.15.32-v8
Here are my OVM UPS settings for Nut:
Enabled
Mode: Netclient
Identifier: apc-server
Comment:
Netclient hostname: 192.168.73.28
Netclient user name: admin
Netclient password: <redacted>
Powervalue: 1
Shutdown mode: UPS reaches low battery
I have the following omv environment variable set (my nut server is responsible for UPS shutdown so the client have this set):
sudo omv-env set -- OMV_UPSMON_POWERDOWNFLAG "/dev/null"
sudo omv-salt stage run prepare
sudo omv-salt stage run deploy
Is anyone else running a Nut netclient having issues with the latest OMV build?
