[Nut-upsuser] Data Stale issue

Charles Lepple clepple at gmail.com
Mon May 6 13:55:41 BST 2019


On May 6, 2019, at 8:10 AM, Gareth Davies wrote:
> 
> Hello,
> 
> I apologise if I've sent this question to the wrong place/e-mail! I'm new to the site! I was wondering if anyone could help me... I downloaded Network UPS Tools yesterday so that I could receive e-mail notifications of when my UPS switched to battery power. I got it up and running and was working brilliantly! Then, after a while I tested the system by switching off power to my UPS.... I wasn't receiving any e-mail notifications! I was puzzled by this given it had worked perfectly fine just a few minutes (or an hour) before! I then ran the nut-server status command  and saw the following error:
> 
> Data for UPS [ups] is stale - check driver
> Duplicate driver instance detected! Terminating other driver!

The "data is stale" message does happen from time to time.

The "duplicate driver" message shouldn't happen, though it can be the result of mixing things up while testing. When starting and stopping NUT, be sure that the old driver process (usbhid-ups) has stopped before restarting things.

Which version of NUT are you using, and assuming Linux, which distribution?

> I checked the web and given I have a CyberPower UPS it seemed I had the correct driver stated (usbhid-ups). However after running the command usb-devices in the terminal it indicated that the driver associated with the UPS was 'usbfs'? I changed this in the conf file but no luck 🙁 

The term "driver" is a bit overloaded - NUT started using that term prior to when USB became a common connection type for an UPS. "usb-devices" is reading the kernel's view of the USB subsystem, and "usbfs" is the kernel's way of handing over a USB device to a process that uses libusb (like the current USB UPS drivers in NUT).

Long story short, "driver = usbhid-ups" is the right thing to use in ups.conf for a CyberPower USB UPS.

There might be some other options to try in ups.conf, but the version/distro information will help narrow that down.

> Just to add to the above, I've tried all other solutions I found on the web such as increasing the MAXAGE, DEADTIME and POLLINTERVAL values....

[please use reply-all to include the list, and consider subscribing below in case someone else replies directly to the list - it's a low-volume list, and you can unsubscribe easily later.]

> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser




More information about the Nut-upsuser mailing list