<div dir="ltr"><div>Great!<br></div><div><br></div><div>Regarding libusb and nut-scanner, I think the *.so (exact) symlinks are part of *-devel packages.</div><div><br></div><div>This was solved in NUT recently (maybe after 2.8.2 release already) by detecting and stashing the basename of realpath of the library present during build, so the exact *.so.X.Y.Z would be also tried.</div><div><br></div><div>Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile bus/busport/device numbers by default.</div><div><br></div><div>Jim</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Nov 10, 2024 at 7:42 PM Bill Gee <<a href="mailto:bgee@campercaver.net">bgee@campercaver.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for the tip, Jim. I just figured out what is going on. The <br>
system is now working. ==> This one is on me. <==<br>
<br>
The root cause was the specification of the bus number in the ups.conf <br>
file. Here is what it looks like now:<br>
<br>
============<br>
[cyberpower]<br>
driver = "usbhid-ups"<br>
port = "auto"<br>
vendorid = "0764"<br>
productid = "0501"<br>
product = "UPS CP1000AVRLCD"<br>
vendor = "CPS"<br>
# bus = "006"<br>
================<br>
<br>
It had been running with the bus= line uncommented. I don't remember <br>
why that was needed, but sometime in the dark past I added it. <br>
Commenting it out and restarting both nut-server and nut-monitor brought <br>
everything to life.<br>
<br>
Charles' reply below had the seed of the answer when he mentioned how <br>
the UPS will appear in the /dev/ directory. I had been looking at every <br>
other file except ups.conf and so the bus number was not top of mind.<br>
<br>
The documentation linked by Jim says that the DEBUG_MIN setting is <br>
supported in all of the .conf files. I changed it in upsd.conf, then <br>
went looking in other files. That is when I noticed the bus number in <br>
ups.conf. A very big DOH slap was promptly administered!<br>
<br>
I think the messages about permissions were the result of not having bus <br>
number 6 at all. There was no /dev device to connect to and that was <br>
interpreted as lack of permissions.<br>
<br>
As for the messages about missing libusb ... I am still puzzled over <br>
that. nut-scanner still complains about it. It is hard to argue with <br>
success, though, so that question is now sort of moot. "upsc cyberpower" <br>
returns valid information and nut-monitor is no longer attempting <br>
restart once per minute.<br>
<br>
Thanks everyone for the help.<br>
<br>
===============<br>
Bill Gee<br>
<br>
On 11/10/24 11:45, Jim Klimov wrote:<br>
> Can you try starting the driver with higher debug verbosity to see more <br>
> details, e.g. add `debug_min = 6` to the `ups.conf` section, or stop the <br>
> auto-starting driver attempts and run the driver program with CLI options?<br>
> <br>
> * <a href="https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-</a> <br>
> verbosity <<a href="https://github.com/networkupstools/nut/wiki/Changing-NUT-" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/wiki/Changing-NUT-</a> <br>
> daemon-debug-verbosity><br>
> <br>
> With `upsdrvctl` driven attempts, you may also be in conflict with a <br>
> generated `nut-driver@cyberpower.service` instance (although this is not <br>
> the only problem, as the unit seems to fail starting for you too), more <br>
> details about such units at:<br>
> <br>
> * <a href="https://github.com/networkupstools/nut/wiki/" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/wiki/</a> <br>
> nut%E2%80%90driver%E2%80%90enumerator-(NDE) <<a href="https://github.com/" rel="noreferrer" target="_blank">https://github.com/</a> <br>
> networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)><br>
> <br>
> Jim<br>
> <br>
> <br>
> On Sun, Nov 10, 2024 at 4:47 PM Bill Gee <<a href="mailto:bgee@campercaver.net" target="_blank">bgee@campercaver.net</a> <br>
> <mailto:<a href="mailto:bgee@campercaver.net" target="_blank">bgee@campercaver.net</a>>> wrote:<br>
> <br>
> I also am wondering if the message about libusb driver missing might be<br>
> the real problem.<br>
> <br>
> Checking my system, I see this:<br>
> <br>
> ===================<br>
> [root@mythtv dev]# ll /dev/bus/usb/001<br>
> total 0<br>
> crw-rw-r--+ 1 root root 189, 0 Nov 9 08:21 001<br>
> crw-rw-r--+ 1 root root 189, 1 Nov 9 08:21 002<br>
> crw-rw-r--+ 1 root root 189, 2 Nov 9 08:21 003<br>
> crw-rw-r--+ 1 root dialout 189, 3 Nov 10 09:43 004<br>
> ==================<br>
> <br>
> That looks to me like the udev rule worked.<br>
> <br>
> ===============<br>
> Bill Gee<br>
> <br>
> On 11/10/24 08:38, Charles Lepple via Nut-upsuser wrote:<br>
> > On Nov 9, 2024, at 8:09 PM, Tim Dawson <<a href="mailto:tadawson@tpcsvc.com" target="_blank">tadawson@tpcsvc.com</a><br>
> <mailto:<a href="mailto:tadawson@tpcsvc.com" target="_blank">tadawson@tpcsvc.com</a>>> wrote:<br>
> >><br>
> >> Check /dev/hidraw6, as noted in your dmesg output (and any other<br>
> *hid*<br>
> >> devices under /dev). User nut has almost zero privs to devices<br>
> unless<br>
> >> a udev rule changes the perms on the dev for nut . . .<br>
> ><br>
> > I admit I am not fully tracking the latest NUT developments, but<br>
> I don't<br>
> > think the current drivers use /dev/hidraw*, especially when the<br>
> drivers<br>
> > mention libusb. (Once the libusb-based drivers start, they should<br>
> detach<br>
> > the kernel's HID drivers such that the corresponding /dev/hidraw*<br>
> device<br>
> > disappears.)<br>
> ><br>
> > You are correct that the udev rules need to change permissions on<br>
> one of<br>
> > the UPS /dev nodes, though.<br>
> ><br>
> > From Bill's lsusb output:<br>
> ><br>
> > [root@mythtv ups]# lsusb<br>
> > ...<br>
> > Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500<br>
> AVR UPS<br>
> ><br>
> > The libusb path for this UPS would typically be /dev/bus/usb/001/004<br>
> ><br>
> > --<br>
> > Charles Lepple<br>
> > clepple@gmail<br>
> ><br>
> ><br>
> >> _______________________________________________<br>
> >> Nut-upsuser mailing list<br>
> >> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a> <mailto:<a href="mailto:Nut-upsuser@alioth-" target="_blank">Nut-upsuser@alioth-</a><br>
> <a href="http://lists.debian.net" rel="noreferrer" target="_blank">lists.debian.net</a>><br>
> >> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-</a><br>
> upsuser <<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/</a><br>
> nut-upsuser><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Nut-upsuser mailing list<br>
> > <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a> <mailto:<a href="mailto:Nut-upsuser@alioth-" target="_blank">Nut-upsuser@alioth-</a><br>
> <a href="http://lists.debian.net" rel="noreferrer" target="_blank">lists.debian.net</a>><br>
> > <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-</a><br>
> upsuser <<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/</a><br>
> nut-upsuser><br>
> <br>
> <br>
> _______________________________________________<br>
> Nut-upsuser mailing list<br>
> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a> <mailto:<a href="mailto:Nut-upsuser@alioth-" target="_blank">Nut-upsuser@alioth-</a><br>
> <a href="http://lists.debian.net" rel="noreferrer" target="_blank">lists.debian.net</a>><br>
> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
> <<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a>><br>
> <br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>