<html><head></head><body><div dir="auto">Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . </div><br><br><div class="gmail_quote"><div dir="auto">On November 9, 2024 1:25:29 PM 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">Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level.<br><br>I looked through /dev/ but did not see a device that jumps out as the UPS.<hr>[root@mythtv rules.d]# dmesg | grep -i 0764<br>[ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01<br>[ 2.049515] hid-generic 0003:0764:0501.0007: hiddev98,hidraw6: USB HID v1.10 Device [CPS UPS CP1000AVRLCD] on usb-0000:00:1d.0-1.8/input0<br>[root@mythtv rules.d]#<br><br>[root@mythtv rules.d]# ll 62*<br>-rw-r--r-- 1 root root 4541 Jan 23 2024 62-multipath.rules<br>-rw-r--r-- 1 root root 184 Apr 2 2024 62-nut-ipmipsu.rules<br>-rw-r--r-- 1 root root 15921 Apr 2 2024 62-nut-usbups.rules<br>[root@mythtv rules.d]#<br><br>[root@mythtv ups]# lsusb<br>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub<br>Bus 001 Device 003: ID 05af:0408 Jing-Mold Enterprise Co., Ltd 2.4G USB RF KeyBoard<br>Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS<br>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub<br>Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller<br>Bus 002 Device 004: ID 0c45:7663 Microdia USB Keyboard<br><br>[root@mythtv system]# ps -U nut<br> PID TTY TIME CMD<br> 1255 ? 00:00:00 upsd<br> 1280 ? 00:00:00 upsmon<br>[root@mythtv system]#<hr>Looking through /var/log/messages, I see this issued once per minute:<hr>Nov 9 12:18:00 mythtv nut-monitor[1280]: Poll UPS [cyberpower@localhost] failed - Driver not connected<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18885]: Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18885]: USB communication driver (libusb 1.0) 0.47<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18885]: libusb1: Could not open any HID devices: insufficient permissions on everything<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18885]: No matching HID UPS found<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18885]: upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18861]: Driver failed to start (exit status=1)<br>Nov 9 12:18:00 mythtv nut-driver@cyberpower[18861]: Network UPS Tools - UPS driver controller 2.8.2<br>Nov 9 12:18:00 mythtv systemd[1]: nut-driver@cyberpower.service: Control process exited, code=exited, status=1/FAILURE<br>Nov 9 12:18:00 mythtv systemd[1]: nut-driver@cyberpower.service: Failed with result 'exit-code'.<br>Nov 9 12:18:00 mythtv systemd[1]: Failed to start nut-driver@cyberpower.service - Network UPS Tools - device driver for NUT device 'cyberpower'.<br>Nov 9 12:18:05 mythtv nut-monitor[1280]: Poll UPS [cyberpower@localhost] failed - Driver not connected<hr>Bill Gee<br><br>On 11/9/24 11:12, Tim Dawson wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><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?<br><br><br>On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee@campercaver.net> wrote:<br><br> Running NUT version 2.8.2 on Fedora 40. NUT installed from the<br> Fedora package. CyberPower CP1000AVRLCD connected by USB.<br><br> I updated the system yesterday with all the latest Fedora packages.<br> Now NUT will not run. Chasing the issue through the layers, I come<br> 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<br> everything<br> No matching HID UPS found<br> upsnotify: failed to notify about state 4: no notification tech<br> 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<br> disabled.<br> Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP<br> search disabled.<br> Cannot load XML library (libneon.so) : file not found. XML search<br> disabled.<br> Cannot load AVAHI library (libavahi-client.so) : file not found.<br> AVAHI search disabled.<br> Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI<br> search disabled.<br> Cannot load NUT library (libupsclient.so) : file not found. NUT<br> 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 -><br> 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 -><br> 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 -><br> 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-<br> driver@cyberpower.service: Scheduled restart job, restart counter ><br> Nov 09 08:50:46 mythtv.billgee.local systemd[1]: Starting nut-<br> driver@cyberpower.service - Network UPS Tools - device dr><br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]:<br> Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]:<br> USB communication driver (libusb 1.0) 0.47<br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]:<br> libusb1: Could not open any HID devices: insufficient><br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]: No<br> matching HID UPS found<br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4655]:<br> upsnotify: failed to notify about state 4: no notific><br> Nov 09 08:50:46 mythtv.billgee.local nut-driver@cyberpower[4637]:<br> Driver failed to start (exit status=1)<br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]:<br> Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]:<br> USB communication driver (libusb 1.0) 0.47<br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]:<br> libusb1: Could not open any HID devices: insufficient><br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]: No<br> matching HID UPS found<br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4657]:<br> upsnotify: failed to notify about state 4: no notific><br> Nov 09 08:50:51 mythtv.billgee.local nut-driver@cyberpower[4637]:<br> Driver failed to start (exit status=1)<br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]:<br> Network UPS Tools - Generic HID driver 0.53 (2.8.2)<br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]:<br> USB communication driver (libusb 1.0) 0.47<br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]:<br> libusb1: Could not open any HID devices: insufficient><br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]: No<br> matching HID UPS found<br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4659]:<br> upsnotify: failed to notify about state 4: no notific><br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4637]:<br> Driver failed to start (exit status=1)<br> Nov 09 08:50:56 mythtv.billgee.local nut-driver@cyberpower[4637]:<br> Network UPS Tools - UPS driver controller 2.8.2<br> Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-<br> driver@cyberpower.service: Control process exited, code=exited, st><br> Nov 09 08:50:56 mythtv.billgee.local systemd[1]: nut-<br> driver@cyberpower.service: Failed with result 'exit-code'.<br> Nov 09 08:50:56 mythtv.billgee.local systemd[1]: Failed to start<br> nut-driver@cyberpower.service - Network UPS Tools - de><hr> nut-scanner is correct! The .so file it is looking for does not<br> 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<br> anything. I also see messages about "Insufficient permissions on<br> everything".<br><br> Is this - at base - a problem with USB permissions? Missing .so<br> files? Or something else??<br><br> Thanks!<br><br><div class="k9mail-signature">-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.<hr>Nut-upsuser mailing list<br>Nut-upsuser@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br></div></div></blockquote><div dir="auto"><hr>Nut-upsuser mailing list<br>Nut-upsuser@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><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>