Bug #13997
open
NUT Package and 23.01
0%
Description
Feb 17 13:56:23 Lee_Family kernel: pid 53495 (usbhid-ups), jid 0, uid 66: exited on signal 11
Feb 17 09:20:53 Lee_Family kernel: pid 85785 (usbhid-ups), jid 0, uid 66: exited on signal 11
Something is causing the UPS package to stop working, I have performed a fresh USB based install for 23.01 and reinstalled the package, the result is the same. After a while the NUT package no longer can see the UPS. Many users are seeing the same issues.
Files
Updated by 
Updated by Greg Jacobs 3 months ago
Seeing same bug / issue
<6>1 2023-02-25T11:05:45.001935-05:00 firewall.lan kernel - - - pid 28916 (usbhid-ups), jid 0, uid 66: exited on signal 10
Partial UPS details follow
device.model CP1500AVRLCDa device.type ups driver.name usbhid-ups driver.parameter.pollfreq 30 driver.parameter.pollinterval 15 driver.parameter.port auto driver.parameter.synchronous auto driver.version 2.8.0 driver.version.data CyberPower HID 0.6 driver.version.internal 0.47 driver.version.usb libusb-1.0.0 (API: 0x1000102) ups.model CP1500AVRLCDa ups.productid 0501 ups.serial CTHHT2000335 ups.vendorid 0764
Same as reported above, seems variable time frame and usbhid-ups exits on signal 10 in my case. Prior tuning of values like pollinterval and pollfreq don't seem to help (commonly required with cyberpower and nut)
Im including my system / harwdare as its Qotom iCore5 running 23.01 as well.
[23.01-RELEASE][root@firewall.lan]/var/log: dmidecode
# dmidecode 3.4
Scanning /dev/mem for entry point.
SMBIOS 3.1.1 present.
Table at 0x8CE22000.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 5.12
Release Date: 10/31/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.12
--removed most details--
I can confirm once UPS comms are lost the process restarted restores communications.
Broadcast Message from root@firewall.lan
(no tty) at 13:39 EST...
Communications with UPS ups lost
Note that I can check and confirm process no longer running
[23.01-RELEASE][root@firewall.lan]/var/log: ps xal | grep usbhid-ups
0 33629 73271 2 20 0 12808 2668 piperd S+ 0 0:00.00 grep usbhid-ups
[23.01-RELEASE][root@firewall.lan]/var/log: /usr/local/libexec/nut/usbhid-ups -a ups -u root
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
kill: No such process
Using subdriver: CyberPower HID 0.6
Broadcast Message from root@firewall.lan
(no tty) at 13:40 EST...
Communications with UPS ups established
And once restarting usbhid-ups things work normally again.
Side note / request, can we have usbhid-ups added to the NUT Service Watchdog list of processes restarted as a workaround / secondary lift to make this more robust in the future as an option for users?
Updated by Greg Jacobs 3 months ago
Also related forum thread https://forum.netgate.com/topic/102959/nut-package/1052?lang=en-US
Updated by Greg Jacobs 3 months ago
I have applied the workaround for now per https://forum.netgate.com/topic/102959/nut-package/1072?_=1677507452044&lang=en-US
In the interim, the only known work-around using the release code (discovered by Timo M) is to add the line
interruptonly
to the Extra Arguments to driver section. This will cut down some of the information you can see about your UPS, but the important stuff needed to monitor and shutdown should still be there.