Duplicate
Details
Assignee
WaqarWaqarReporter
Jean-Francois RoyJean-Francois RoyLabels
Impact
HighTime remaining
0mComponents
Fix versions
Affects versions
Priority
Low
Details
Details
Assignee
Waqar
WaqarReporter
Jean-Francois Roy
Jean-Francois RoyLabels
Impact
High
Time remaining
0m
Components
Fix versions
Affects versions
Priority
Katalon Platform
Katalon Platform
Katalon Platform
Created August 16, 2023 at 4:01 AM
Updated February 27, 2025 at 9:14 PM
Resolved August 23, 2023 at 3:48 PM
At boot, the ups driver doesn’t seem to load properly, which causes the nut-server to get in a bad state. Looking at
systemctl status nut-server.service
, there are a number of these logs:Aug 15 20:44:02 kaidame nut-server[139231]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Aug 15 20:44:02 kaidame upsd[139231]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
And of course, nut-monitor fails as well with “Driver not connected” messages.
Additionally, when the system boots, I get an email alert that says:
Communication with UPS ups lost.
UPS Statistics: 'ups'
Statistics could not be recovered
This alert quickly gets cleared, but the UPS is not in fact usable.
It is possible to make the UPS work by issuing a
upsdrvctl start
command in a root shell:root@kaidame[~]# upsdrvctl start
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Duplicate driver instance detected (PID file /run/nut/usbhid-ups-ups.pid exists)! Terminating other driver!
Using subdriver: CyberPower HID 0.6
After this,
upsc ups
returns good data.