On 10/04/2025 18:57, Greg Troxel via Nut-upsuser wrote:
S Shaikh via Nut-upsuser <[email protected]> writes:
I isolated the driver to get cleaner debug messages, and have provided
them below. Once the stale message occurs, the only way to fix things
is by rebooting the host running NUT (and connected to the UPS via
USB).
Unfortunately I haven't yet been able to see the output at the time
the data becomes stale (terminal buffer not big enough). I can try
piping it to a file.
My guess is that there is a USB-level disconnect and this is a problem
between your UPS and your computer more than a nut problem.
I would try a different port and a different cable. I would look at
kernel dmesg. If you see disconnect there, I would leave it without nut
running and see if it disconnects.
In situations where you think you have to reboot, you might also try
unplugging UBS cable, waiting 10s, and replugging.
Here's the output when the driver stops responding:
50850.701985 [D1] Communications with the UPS lost: status read failed!
Given I'm using the same host and cable and have only switched the UPS
my feeling is that something has changed on the UPS side (maybe it goes
to sleep?). However I will try a new cable and port.
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
