similar to: Data Stale issue

Hi Charles, 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

Hello, 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? Kind Regards Gareth On 6 May 2019, at 3:27 pm, Gareth Davies <gareth94 at

Hello all. I have installed Nut on a Raspberry PI and all looks to be configured correctly, but I get stale data and communications lost at random intervals. I tried running nut-driver in gcc to see if I could find any clues there, but it ran for about 24 hours with no sign of an issue. However, when I let Nut run normally, it seems to be anywhere from 2 to 8 hours and the data goes stale and

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

I have a ups that doesn't always (sometimes it does) load NUT right. I use Gentoo: * sys-power/nut Latest version available: 2.6.0-r1 Latest version installed: 2.6.0-r1 Size of files: 1,663 kB Homepage: http://www.networkupstools.org/ Description: Network-UPS Tools License: GPL-2 The kernel is 3.0.4. Here is the dmesg output:

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!

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Arjen, all, Just dropping a note on two points. First, Voltages are perfect in 2.4.1 for the Cyberpower ups's. Glad to see I'm not pushing 20+ any more: http://www.3111skyline.com/nut/ Second, even though the changes to where the monitor lines go in the configs and changes from ACCEPT, etc.. to LISTEN are fairly old now, the documentation for setting up monitoring for multiple UPSs

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

On Mon, 6 May 2019, Gareth Davies wrote: > 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? Those are issues with

The UPS seems to disconnect totally, i need to physically disconnect the cable to get the UPS connected again. A reboot is not enough. Also tried 2 different cables, the one i use now is shielded + 2 ferrite chokes to limit interference. But i want to use NUT since i dont have enough resources to run X.. -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS

When I disconnect my UPS from the wall, I have to wait 15-30 seconds before the USB drier 'polls' this information and tells me that the UPS is on battery power (via knutclient or syslog via nut): ups@p34 POWER ALERT on Fri Jan 26 12:49:29 EST 2007 With a serial connection, I would get the alerts IMMEDIATELY (0.5-1 seconds) after disconnecting the UPS. My new machine does not have a

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

i own a CyberPower OR2200LCDRM2U and was wondering if any nut drivers support this ups. none i have tried have worked although usbhid-ups did tell me that the productid=0601 was not supported yet. i see in the compatability list on the nut website that the PR2200 is supported with the powerpanel driver but the OR2200 is not listed. i am interested in what i am doing wrong or if this is a support

I recently purchased a CyberPower CP1200AVR UPS and am trying to get NUT 2.0.3 or NUT 2.1.0 to work with the newhidups driver, but am having little success. Before I purchased I did some googling and saw people talking about problems so I'm guessing it may not be supported yet? I did find some posts about people getting it to (sort of) work with some hacks, but couldn't tell if they

On Sep 29, 2014, at 12:50 PM, Shade Alabsa <shade34321 at gmail.com> wrote: > The lsusb command did not trigger a disconnect. The output of that > command is below. If you run lsusb several times, does it still work? The exact output of lsusb isn't as important as whether anything gets logged by the kernel. Running lsusb shouldn't cause any extra kernel messages such as

Hello, I have a CyberPower CP1500PFCLCD and I'm trying to get nut to see it under OpenIndiana. All search online suggested that it basically can't happen, but I decided to ask again, maybe things have changed since then. The UPS can be seen by the system: # /usr/sbin/cfgadm -lv usb9/1.1 Ap_Id Receptacle Occupant Condition Information When Type

All, I just had a power failure that caused me a little drama. This spurred me into trying to get NUT up on my cyberpower 1500 again. For about 6 months I tried to get it to work with the new power panel drive with no luck. Today I removed all the old files for NUT and installed the newest version I could find (2.4.3) and it works perfectly now with my UPS. Hopefully now I