NUT on 9.1

H

Held

New Member
Jul 15, 2024
9
2
3
I've upgraded/reinstalled my Proxmox 8.4 installation to 9.1 through a new ISO install, but I cannot seem to get NUT to work any longer on my host. It used to work under 8.4.

Nut-scanner seems to operate normally (using USB so the missing libs shouldn't be an issue):

root@host1:/etc/nut# nut-scanner
Cannot load SNMP library (libnetsnmp.so.40) : file not found. SNMP search disabled.
Cannot load XML library (libneon.so.27) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so.17) : file not found. IPMI search disabled.
Scanning USB bus.
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
Failed to create Avahi client: Daemon not running
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "06DA"
productid = "FFFF"
product = "Innova Unity"
serial = "CPANN1218240022"
vendor = "PHOENIXTEC"
bus = "001"
device = "002"
busport = "004"
###NOTMATCHED-YET###bcdDevice = "0202"
Click to expand...

After I configure the above into /etc/nut/ups.conf:
[PW3000]
driver = "usbhid-ups"
port = "auto"
vendorid = "06DA"
productid = "FFFF"
product = "Innova Unity"
serial = "CPANN1218240022"
vendor = "PHOENIXTEC"
bus = "001"
device = "002"
busport = "004"
Click to expand...

and setting "MODE=netserver" in /etc/nut/nut.conf, and configuring following users in /etc/nut/upsd.users:

[upsmon]
password = xxx

[upsmonremote]
password = xxx
upsmon slave
Click to expand...

and setting following monitoring in /etc/nut/upsmon.conf:

MONITOR PW3000@localhost 1 upsmon xxx master
Click to expand...

, I get issues such as the below:

root@host1:/etc/nut# upsc PW3000@localhost
Init SSL without certificate database
Error: Driver not connected

Logs:
Feb 15 18:56:18 host1 nut-server[65979]: Can't connect to UPS [PW3000] (usbhid-ups-PW3000): No such file or directory
Feb 15 18:56:18 host1 upsd[65979]: Can't connect to UPS [PW3000] (usbhid-ups-PW3000): No such file or directory
Click to expand...


The /run/nut ownership seems fine (nut:nut):
root@host1:/etc/nut# ls -ld /run/nut
drwxrwx--- 3 nut nut 60 Feb 15 19:14 /run/nut
Click to expand...

The USB device is visible:
root@host1:/etc/nut# lsusb | grep 06da
Bus 001 Device 002: ID 06da:ffff Phoenixtec Power Co., Ltd Innova Unity
Click to expand...

However the driver did not seem to have started:
root@host1:/etc/nut# ps aux | grep usbhid
root 109845 0.0 0.0 6532 1976 pts/0 S+ 19:16 0:00 grep usbhid
root@host1:/etc/nut#
Click to expand...

Jouarnalctl shows:
Feb 15 19:15:10 host1 systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Feb 15 19:15:10 host1 systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Feb 15 19:15:10 host1 nut-server[109038]: fopen /run/nut/upsd.pid: No such file or directory
Feb 15 19:15:10 host1 nut-server[109038]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Feb 15 19:15:10 host1 nut-server[109038]: listening on 127.0.0.1 port 3493
Feb 15 19:15:10 host1 nut-server[109038]: listening on 10.0.0.40 port 3493
Feb 15 19:15:10 host1 upsd[109038]: listening on 127.0.0.1 port 3493
Feb 15 19:15:10 host1 upsd[109038]: listening on 10.0.0.40 port 3493
Feb 15 19:15:10 host1 nut-server[109038]: Can't connect to UPS [PW3000] (usbhid-ups-PW3000): No such file or directory
Feb 15 19:15:10 host1 nut-server[109038]: Found 1 UPS defined in ups.conf
Feb 15 19:15:10 host1 upsd[109038]: Can't connect to UPS [PW3000] (usbhid-ups-PW3000): No such file or directory
Feb 15 19:15:10 host1 upsd[109038]: Found 1 UPS defined in ups.conf
Feb 15 19:15:10 host1 nut-server[109038]: Running as foreground process, not saving a PID file
Feb 15 19:15:10 host1 upsd[109038]: Running as foreground process, not saving a PID file
Feb 15 19:15:10 host1 nut-server[109038]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Feb 15 19:15:10 host1 nut-server[109038]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 15 19:15:10 host1 nut-server[109038]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Feb 15 19:15:10 host1 upsd[109038]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Feb 15 19:15:10 host1 upsd[109038]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 15 19:15:10 host1 upsd[109038]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Click to expand...


Output of the requested usbhid-ups command:
root@host1:/etc/nut# /usr/lib/nut/usbhid-ups -a PW3000 -DD
Network UPS Tools - Generic HID driver 0.52 (2.8.1)
USB communication driver (libusb 1.0) 0.46
0.000000 [D1] Network UPS Tools version 2.8.1 (release/snapshot of 2.8.1) built with gcc (Debian 14.2.0-19) 14.2.0 and configured with flags: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --prefix=/usr --sysconfdir=/etc/nut --includedir=/usr/include --mandir=/usr/share/man --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=/usr/libexec --with-ssl --with-nss --with-cgi --with-dev --enable-static --with-statepath=/run/nut --with-altpidpath=/run/nut --with-drvpath=/usr/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/x86_64-linux-gnu/pkgconfig --with-user=nut --with-group=nut --with-udev-dir=/usr/lib/udev --with-systemdsystemunitdir=/usr/lib/systemd/system --with-systemdshutdowndir=/usr/lib/systemd/system-shutdown --with-systemdtmpfilesdir=/usr/lib/tmpfiles.d --with-python=python3 --with-python3=/usr/bin/python3 --with-doc=man
0.000014 [D1] debug level is '2'
0.000422 [D1] Succeeded to become_user(nut): now UID=109 GID=111
0.000431 [D1] upsdrv_initups (non-SHUT)...
0.000433 [D2] Initializing an USB-connected UPS with library libusb-1.0.28 (API: 0x100010a) (NUT subdriver name='USB communication driver (libusb 1.0)' ver='0.46')
0.003564 [D2] Checking device 1 of 17 (1D6B/0003)
0.003573 [D1] Failed to open device (1D6B/0003), skipping: Access denied (insufficient permissions)
0.003576 [D2] Checking device 2 of 17 (1D6B/0002)
0.003579 [D1] Failed to open device (1D6B/0002), skipping: Access denied (insufficient permissions)
0.003580 [D2] Checking device 3 of 17 (1D6B/0003)
0.003583 [D1] Failed to open device (1D6B/0003), skipping: Access denied (insufficient permissions)
0.003585 [D2] Checking device 4 of 17 (1D6B/0002)
0.003588 [D1] Failed to open device (1D6B/0002), skipping: Access denied (insufficient permissions)
0.003590 [D2] Checking device 5 of 17 (174C/3074)
0.003593 [D1] Failed to open device (174C/3074), skipping: Access denied (insufficient permissions)
0.003594 [D2] Checking device 6 of 17 (1D6B/0003)
0.003608 [D1] Failed to open device (1D6B/0003), skipping: Access denied (insufficient permissions)
0.003609 [D2] Checking device 7 of 17 (0781/5151)
0.003612 [D1] Failed to open device (0781/5151), skipping: Access denied (insufficient permissions)
0.003614 [D2] Checking device 8 of 17 (0951/1666)
0.003616 [D1] Failed to open device (0951/1666), skipping: Access denied (insufficient permissions)
0.003618 [D2] Checking device 9 of 17 (174C/2074)
0.003620 [D1] Failed to open device (174C/2074), skipping: Access denied (insufficient permissions)
0.003622 [D2] Checking device 10 of 17 (26CE/0A06)
0.003625 [D1] Failed to open device (26CE/0A06), skipping: Access denied (insufficient permissions)
0.003626 [D2] Checking device 11 of 17 (05E3/0610)
0.003629 [D1] Failed to open device (05E3/0610), skipping: Access denied (insufficient permissions)
0.003630 [D2] Checking device 12 of 17 (06DA/FFFF)
0.003633 [D1] Failed to open device (06DA/FFFF), skipping: Access denied (insufficient permissions)
0.003634 [D2] Checking device 13 of 17 (8087/0032)
0.003637 [D1] Failed to open device (8087/0032), skipping: Access denied (insufficient permissions)
0.003638 [D2] Checking device 14 of 17 (26CE/01A2)
0.003641 [D1] Failed to open device (26CE/01A2), skipping: Access denied (insufficient permissions)
0.003642 [D2] Checking device 15 of 17 (3346/1009)
0.003645 [D1] Failed to open device (3346/1009), skipping: Access denied (insufficient permissions)
0.003646 [D2] Checking device 16 of 17 (05E3/0610)
0.003648 [D1] Failed to open device (05E3/0610), skipping: Access denied (insufficient permissions)
0.003650 [D2] Checking device 17 of 17 (1D6B/0002)
0.003652 [D1] Failed to open device (1D6B/0002), skipping: Access denied (insufficient permissions)
0.003654 [D2] libusb1: No appropriate HID device found
0.003655 libusb1: Could not open any HID devices: insufficient permissions on everything
0.003657 No matching HID UPS found
0.003662 upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
0.003664 upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
root@host1:/etc/nut#
Click to expand...

Any idea what I'm doing wrong? Which permissions are not set properly?
 
Thanks. Didn't help though...

But I did a reboot of my host (after migrating a couple of workloads). After this reboot, the driver issue no longer appeared and things work just fine. Odd.
 
You must log in or register to reply here.
Top Bottom
Back