<html><head></head><body><div dir="auto">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?</div><br><br><div class="gmail_quote"><div dir="auto">On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee@campercaver.net> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB.<br><br>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:<hr>[root@mythtv rules.d]# upsc cyberpower<br>Error: Driver not connected<br><br>[root@mythtv rules.d]# upsdrvctl start<br>Network UPS Tools - UPS driver controller 2.8.2<br>Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br>USB communication driver (libusb 1.0) 0.47<br>libusb1: Could not open any HID devices: insufficient permissions on everything<br>No matching HID UPS found<br>upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it<br>Driver failed to start (exit status=1)<br><br>[root@mythtv ~]# nut-scanner<br>Cannot load USB library (libusb-1.0.so) : file not found. USB search disabled.<br>Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search disabled.<br>Cannot load XML library (libneon.so) : file not found. XML search disabled.<br>Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI search disabled.<br>Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.<br>Cannot load NUT library (libupsclient.so) : file not found. NUT search disabled.<br>No start IP, skipping NUT bus (old connect method)<br>Scanning NUT simulation devices.<br><br>[root@mythtv ~]# cd /usr/lib64<br>[root@mythtv lib64]# ll libusb*<br>lrwxrwxrwx 1 root root 19 Jan 24 2024 libusb-0.1.so.4 -> libusb-0.1.so.4.4.4<br>-rwxr-xr-x 1 root root 28224 Jan 24 2024 libusb-0.1.so.4.4.4<br>lrwxrwxrwx 1 root root 19 May 7 2024 libusb-1.0.so.0 -> libusb-1.0.so.0.4.0<br>-rwxr-xr-x 1 root root 119760 May 7 2024 libusb-1.0.so.0.4.0<br>lrwxrwxrwx 1 root root 23 Jan 24 2024 libusbmuxd-2.0.so.6 -> libusbmuxd-2.0.so.6.0.0<br>-rwxr-xr-x 1 root root 40736 Jan 24 2024 libusbmuxd-2.0.so.6.0.0<br><br>The last few lines from "journalctl -u nut-driver@cyberpower.service":<br><br>Nov 09 08:50:46 mythtv.billgee.local systemd[1]: nut-driver@cyberpower.service: Scheduled restart job, restart counter ><br>Nov 09 08:50:46 mythtv.billgee.local systemd[1]: Starting nut-driver@cyberpower.service - Network UPS Tools - device dr><br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: USB communication driver (libusb 1.0) 0.47<br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: libusb1: Could not open any HID devices: insufficient><br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: No matching HID UPS found<br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: upsnotify: failed to notify about state 4: no notific><br>Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4637]: Driver failed to start (exit status=1)<br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: USB communication driver (libusb 1.0) 0.47<br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: libusb1: Could not open any HID devices: insufficient><br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: No matching HID UPS found<br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: upsnotify: failed to notify about state 4: no notific><br>Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4637]: Driver failed to start (exit status=1)<br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: USB communication driver (libusb 1.0) 0.47<br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: libusb1: Could not open any HID devices: insufficient><br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: No matching HID UPS found<br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: upsnotify: failed to notify about state 4: no notific><br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4637]: Driver failed to start (exit status=1)<br>Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4637]: Network UPS Tools - UPS driver controller 2.8.2<br>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-driver@cyberpower.service: Control process exited, code=exited, st><br>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-driver@cyberpower.service: Failed with result 'exit-code'.<br>Nov 09 08:50:56 mythtv.billgee.local systemd[1]: Failed to start nut-driver@cyberpower.service - Network UPS Tools - de><hr>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.<br><br>Nut-server.service is running, but complains it cannot connect to anything. I also see messages about "Insufficient permissions on everything".<br><br>Is this - at base - a problem with USB permissions? Missing .so files? Or something else??<br><br>Thanks!<br></div></pre></blockquote></div><div dir="auto"><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>