NUT-MONITOR not working any more after in place upgrade to PVE9

aheinz

New Member
Mar 26, 2025
4
0
1
Issue:
1759682804656.png
I previously used this howto and it was working just fine...

Now i get this in lxc syslog:
2025-10-05T16:43:07.635272+00:00 nutmonitor nut-monitor[1112]: UPS ups@192.168.10.251 is unavailable
2025-10-05T16:43:07.636376+00:00 nutmonitor nut-monitor[1191]: Network UPS Tools upsmon 2.8.1
2025-10-05T16:43:07.636792+00:00 nutmonitor nut-monitor[1191]: Warning: no shutdown command defined!
2025-10-05T16:45:01.006066+00:00 nutmonitor CRON[1197]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2025-10-05T16:45:26.896825+00:00 nutmonitor nut-monitor[1112]: UPS [ups@192.168.10.251]: connect failed: Connection failure: Connection timed out


Network UPS Tools runs direct on the PVE9 host and looks fine for me...

[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0463"
productid = "FFFF"
product = "Ellipse PRO"
serial = "G364P14018"
vendor = "EATON"
bus = "001"
device = "002"
busport = "006"
###NOTMATCHED-YET###bcdDevice = "0100"

root@proxmox:/etc/nut# systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-10-05 17:37:05 CEST; 1h 14min ago
Invocation: 93dafe367e2f422a9371cf0fbc367fdc
Process: 791362 ExecStartPre=/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
Main PID: 791363 (upsd)
Tasks: 1 (limit: 38164)
Memory: 544K (peak: 1.7M)
CPU: 630ms
CGroup: /system.slice/nut-server.service
└─791363 /lib/nut/upsd -F

Oct 05 17:37:50 proxmox upsd[791363]: Can't connect to UPS [heartbeat] (dummy-ups-heartbeat): No such file or directory
Oct 05 17:37:50 proxmox nut-server[791363]: Can't connect to UPS [heartbeat] (dummy-ups-heartbeat): No such file or directory
Oct 05 17:38:08 proxmox nut-server[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat
Oct 05 17:38:08 proxmox upsd[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat
Oct 05 17:38:15 proxmox nut-server[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat
Oct 05 17:38:15 proxmox upsd[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat
Oct 05 17:38:19 proxmox nut-server[791363]: Connected to UPS [ups]: usbhid-ups-ups
Oct 05 17:38:19 proxmox upsd[791363]: Connected to UPS [ups]: usbhid-ups-ups
Oct 05 17:38:30 proxmox nut-server[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat
Oct 05 17:38:30 proxmox upsd[791363]: Connected to UPS [heartbeat]: dummy-ups-heartbeat

Does anyone had the same experiance or even already a solution?
 
Last edited:
Resolution:
I noticed after the upgrade from PVE 8 to PVE 9, in the NUT install folder, the installer must have renamed my original config files and created new ones. See screenshot bellow, note the dates

command to browse to the NUT install folder

cd /etc/nut

Run this command to list all files and creation "birth" date

ls --time=birth -l

1779646130126.png

I then renamed the new files to .default, and renamed the original config files with .dpkg-old back to .conf

Code:
mv nut.conf nut.conf.default
mv ups.conf ups.conf.default
mv upsd.conf upsd.conf.default
mv upsd.users upsd.users.default
mv upsmon.conf upsmon.conf.default
mv upssched.conf upssched.conf.default
mv nut.conf.dpkg-old nut.conf
mv ups.conf.dpkg-old ups.conf
mv upsd.conf.dpkg-old upsd.conf
mv upsd.users.dpkg-old upsd.users
mv upsmon.conf.dpkg-old upsmon.conf
mv upssched.conf.dpkg-old upssched.conf

Finally, rebooted the PVE. All set!