[Nut-upsuser] Data Stale issue
gareth94 at hotmail.co.uk
Mon May 6 18:34:37 BST 2019
Just to say, I stopped the driver and started it again and the errors went away! However, I turned off power to the UPS but I wasn’t receiving any e-mails :( also when I rebooted the RPi the driver/service didn’t start back up automatically...
I wonder if you have any thoughts on the above?
On 6 May 2019, at 3:27 pm, Gareth Davies <gareth94 at hotmail.co.uk<mailto:gareth94 at hotmail.co.uk>> wrote:
Thank you so much for getting back to me. I should have given you a bit of background in my last message but I'm actually doing this for my grandmother's benefit! She has Dementia and lives on her own so we want to be notified if she has a power cut... I'd hate to think she might be stumbling around in the dark (which has happened before)!
In terms of stopping the older driver process (usbhid-ups) you mentioned, how would I go about that? Could you advise me on the necessary commands? Sorry for being rather daft - I'm not quite used to Linux yet! 🙁
I'm using the latest version of NUT which I downloaded yesterday. I'm running the whole thing from the Raspberry Pi I have. I'm not entirely sure which version it is but I bought it back in 2014 I think. The OS is Debian 9 (Stretch) if that helps?
I'll change the driver back to usbhid-ups as you advised. Thank you for confirming that. The strange thing is though, the keyboard I attach to the Pi is showing to have usbhid-ups driver! Nothing to worry about I guess?
Just another thing I wanted to mention... once I've resolved the aforementioned issues, would it be possible for the system to run without any maintenance or checking up on it? What I mean is, once I've plugged it into my grandmother's house, I'd like to leave it running and forget about it basically - in the knowledge and trust it would notify us if there's ever a power cut!
From: Charles Lepple <clepple at gmail.com<mailto:clepple at gmail.com>>
Sent: 06 May 2019 13:55
To: Gareth Davies
Cc: nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>
Subject: Re: [Nut-upsuser] Data Stale issue
On May 6, 2019, at 8:10 AM, Gareth Davies wrote:
> 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<mailto:Nut-upsuser at alioth-lists.debian.net>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser