[Nut-upsuser] NUT stopped working after an upgrade

[Tim Dawson]

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as?

On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote:
>Running NUT version 2.8.2 on Fedora 40.  NUT installed from the Fedora package.  CyberPower CP1000AVRLCD connected by USB.
>
>I updated the system yesterday with all the latest Fedora packages.  Now NUT will not run.  Chasing the issue through the layers, I come to this:
>
>=====================
>[root at mythtv rules.d]# upsc cyberpower
>Error: Driver not connected
>
>[root at mythtv rules.d]# upsdrvctl start
>Network UPS Tools - UPS driver controller 2.8.2
>Network UPS Tools - Generic HID driver 0.53 (2.8.2)
>USB communication driver (libusb 1.0) 0.47
>libusb1: Could not open any HID devices: insufficient permissions on everything
>No matching HID UPS found
>upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
>Driver failed to start (exit status=1)
>
>[root at mythtv ~]# nut-scanner
>Cannot load USB library (libusb-1.0.so) : file not found. USB search disabled.
>Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search disabled.
>Cannot load XML library (libneon.so) : file not found. XML search disabled.
>Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI search disabled.
>Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
>Cannot load NUT library (libupsclient.so) : file not found. NUT search disabled.
>No start IP, skipping NUT bus (old connect method)
>Scanning NUT simulation devices.
>
>[root at mythtv ~]# cd /usr/lib64
>[root at mythtv lib64]# ll libusb*
>lrwxrwxrwx 1 root root     19 Jan 24  2024 libusb-0.1.so.4 -> libusb-0.1.so.4.4.4
>-rwxr-xr-x 1 root root  28224 Jan 24  2024 libusb-0.1.so.4.4.4
>lrwxrwxrwx 1 root root     19 May  7  2024 libusb-1.0.so.0 -> libusb-1.0.so.0.4.0
>-rwxr-xr-x 1 root root 119760 May  7  2024 libusb-1.0.so.0.4.0
>lrwxrwxrwx 1 root root     23 Jan 24  2024 libusbmuxd-2.0.so.6 -> libusbmuxd-2.0.so.6.0.0
>-rwxr-xr-x 1 root root  40736 Jan 24  2024 libusbmuxd-2.0.so.6.0.0
>
>The last few lines from "journalctl -u nut-driver at cyberpower.service":
>
>Nov 09 08:50:46 mythtv.billgee.local systemd[1]: nut-driver at cyberpower.service: Scheduled restart job, restart counter >
>Nov 09 08:50:46 mythtv.billgee.local systemd[1]: Starting nut-driver at cyberpower.service - Network UPS Tools - device dr>
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4655]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4655]: USB communication driver (libusb 1.0) 0.47
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4655]: libusb1: Could not open any HID devices: insufficient>
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4655]: No matching HID UPS found
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4655]: upsnotify: failed to notify about state 4: no notific>
>Nov 09 08:50:46 mythtv.billgee.local nut-driver at cyberpower[4637]: Driver failed to start (exit status=1)
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4657]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4657]: USB communication driver (libusb 1.0) 0.47
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4657]: libusb1: Could not open any HID devices: insufficient>
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4657]: No matching HID UPS found
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4657]: upsnotify: failed to notify about state 4: no notific>
>Nov 09 08:50:51 mythtv.billgee.local nut-driver at cyberpower[4637]: Driver failed to start (exit status=1)
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4659]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4659]: USB communication driver (libusb 1.0) 0.47
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4659]: libusb1: Could not open any HID devices: insufficient>
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4659]: No matching HID UPS found
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4659]: upsnotify: failed to notify about state 4: no notific>
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4637]: Driver failed to start (exit status=1)
>Nov 09 08:50:56 mythtv.billgee.local nut-driver at cyberpower[4637]: Network UPS Tools - UPS driver controller 2.8.2
>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-driver at cyberpower.service: Control process exited, code=exited, st>
>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-driver at cyberpower.service: Failed with result 'exit-code'.
>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: Failed to start nut-driver at cyberpower.service - Network UPS Tools - de>
>
>================
>
>nut-scanner is correct!  The .so file it is looking for does not exist. What the heck happened to it?  Was it ever there?  I have no idea.
>
>Nut-server.service is running, but complains it cannot connect to anything.  I also see messages about "Insufficient permissions on everything".
>
>Is this - at base - a problem with USB permissions?  Missing .so files? Or something else??
>
>Thanks!
>-- 
>===============
>Bill Gee
>
>
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20241109/055db76f/attachment.htm>