Hello,
> The three *Cannot load* errors...
These should not be a problem. The nut-scanner takes a truly dynamic
approach to optionally loading dynamic libraries, so it does not have
run-time (and packaging) dependencies on capabilities a particular NUT
deployment does not need. In your case it did not complain about a missing
libusb implementation, and did find a usb device, so far so good.
> My UPS is... usbhid-ups
I am not sure if you meant the older UPS (in config backup), or the one you
replaced it with? Anyhow, vendorid = "0665" productid =
"5161" in NUT
sources is only associated with nutdrv_qx (or the older blazer_usb) drivers
for a dialect of Megatec Q<x> protocol family. So I would be very
surprised
if that device does actually work with USB HID protocol (also? instead?)
> Network UPS Tools - UPS driver controller 2.8.1
This is somewhat aged now, the latest NUT release is 2.8.4. But sadly seems
normal for a stable distro who set a base line and do not change it for
half a decade. At least they do not offer 2.7.4 as the latest anymore ;)
> When I execute *upsdrvctl start* I get...
This older way of directly starting the drivers may collide with systemd
units automatically generated to wrap each driver instance independently,
fo more details please see
https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)
TLDR: Either use `systemctl start/stop/restart nut-driver at upsname` (or the
new `upsdrvsvcctl` tool), or temporarily stop/mask the NDE service and the
nut-driver@ service instance, while you experiment with the driver
configuration. In that case you may want to first run the driver program
directly and list all the options you would later copy into `ups.conf`,
e.g.
:; /lib/nut/usbhid-ups -s test -x port=....
and at this point you may want to bump the driver's debug verbosity to see
more precisely what it complains about - see
https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity
Hope this helps,
Jim Klimov
On Thu, Oct 23, 2025 at 9:18?AM Alan Bonnici via Nut-upsuser <
nut-upsuser at alioth-lists.debian.net> wrote:
> Hi,
>
> I had a stable NUT environment for quite a while until I had to change UPS
> and reinstalled my Proxmox environment.
>
> I had a backup of my /etc/nut directory and have only used it as
> reference.
>
> My UPS is a Powerwalker VI 2200 IEC/UK and that corresponded to
> *usbhid-ups*.
>
> *nut-scanner -U* returns the following
> 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.
> [nutdev1]
> driver = "nutdrv_qx"
> port = "auto"
> vendorid = "0665"
> productid = "5161"
> product = "USB to Serial"
> serial = "20100826"
> vendor = "INNO TECH"
> bus = "001"
> device = "003"
> busport = "003"
> ###NOTMATCHED-YET###bcdDevice = "0002"
>
> The three *Cannot load* errors are not present in my notes and I suspect
> they could be the root cause of successive errors.
>
> My */etc/nut/ups.conf* is as follows:
>
> # Wait 10 seconds for the driver to finish starting.
> maxstartdelay = 10
>
> # Try 3 times to start the driver, before giving up.
> maxretry = 3
>
> # Wait 5 seconds between attempts to start the driver.
> retrydelay = 5
>
> # Poll the ups every 5 seconds
> pollinterval = 5
>
> [pve1]
> # PowerWalker
> driver = usbhid-ups
> port = auto
> desc = "Cypress Semiconductor USB to Serial"
> vendorid = 0665
> productid = 5161
> # if the charge is less than 75 percent trigger a LB status
> override.battery.charge.low = 75
> # Some drivers reset battery.charge.low. lowbatt addresses this
> lowbatt = 75
> # if the remaining charge is less than 1200s (20 minutes) trigger a low
> battery status
> override.battery.runtime.low = 1200
> # Wait 10 minutes before attempting to restart the ups load after a
> power cut
> ondelay = 600
> # wait 5 minutes for ups to power off
> override.ups.delay.shutdown = 300
> # Could offdelay act as an override for override.ups.delay.shutdown?
> offdelay = 300
> serial = 20100826
>
>
> When I execute *upsdrvctl start* I get the following repeated 3 times
> Network UPS Tools - UPS driver controller 2.8.1
> Network UPS Tools - Generic HID driver 0.52 (2.8.1)
> USB communication driver (libusb 1.0) 0.46
> libusb1: Could not open any HID devices: insufficient permissions on
> everything
> No matching HID UPS found
> upsnotify: notify about state 4 with libsystemd: was requested, but not
> running as a service unit now, will not spam more about it
> upsnotify: failed to notify about state 4: no notification tech defined,
> will not spam more about it
> Driver failed to start (exit status=1)
>
> Thanks,
> Alan
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251023/76d5a14c/attachment.htm>