similar to: query "Data stale" from the cmdline

Hi Charles, On Monday, 27. June 2016 08:59:02 Charles Lepple wrote: > > is there a way to query from the cmdline if the UPS data is stale? > > The "data stale" state applies to the entire set of variables for an UPS, > so if the exit code of `upsc` is zero, the data set is not stale. > > "upsc" outputs a lot of information, but not if the data is stale.

On Jun 27, 2016, at 4:46 AM, Thomas Jarosch wrote: > > Hello, > > is there a way to query from the cmdline if the UPS data is stale? The "data stale" state applies to the entire set of variables for an UPS, so if the exit code of `upsc` is zero, the data set is not stale. > > "upsc" outputs a lot of information, but not if the data is stale. > Example

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

Hello, I had a brief power fluctuation earlier, which caused the UPS to power up a few seconds. Then suddenly NUT was busy shutting down my server, after full power had already been restored. Here's the logs: Jun 6 13:28:30 hell upsmon[607]: UPS apc620 at localhost on battery Jun 6 13:28:35 hell apcsmart[602]: Communications with UPS lost - check cabling Jun 6 13:28:35 hell upsd[604]:

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Hello, I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? I am using the apcsmart UPS driver. Thanks, M.L.

Hi, I am studying (in a few months I might go on a TV quiz show :-) Rodger's excelent guide and wanted to confirm that all measurements in NUT are in seconds. For example, the Cyber Power System CP1500 AVR UPS returns that the **driver.parameter.pollfreq = 30**. This means that I can (maybe should) adjust the settings within NUT.CONF to match this value. Setting this value to 2 seconds gains

On Jun 27, 2016, at 9:11 AM, Thomas Jarosch wrote: > > Jun 27 14:56:24 server upsd[3123]: Data for UPS [apcsmart] is stale - check driver > Jun 27 14:56:24 server upsd: Data for UPS [apcsmart] is stale - check driver ... > Jun 27 14:58:38 server upsd: UPS [apcsmart] data is no longer stale Two minutes is a bit longer than what I was expecting for stale data. If you have a USB

Thanks for the help, with the apcsmart-old driver it works again! Didn't notice my UPS is now so "old" ;-) Here is the output of upsc with apcsmart-old driver: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 11/22/06 battery.packs: 001 battery.packs.bad: 000 battery.runtime: 540 battery.runtime.low: 120 battery.voltage: 53.73

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

Hello, I use the following in my ups.conf: # USB: [apc] driver = usbhid-ups port = auto desc = "APC 1500VA" pollfreq = 5 On my new motherboard (an Intel DP55KG), every once and awhile I get this: Broadcast Message from nut at box.com (somewhere) at 17:48 ... Communications with UPS apc at localhost lost Broadcast Message from nut at box.com

On Jun 13, 2013, at 7:14 AM, ML mail wrote: > I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? > > I am using the apcsmart UPS driver. The apcsmart driver was overhauled, and in 2.6.x, the previous

It looks like I'm currently on 4.4.0-38 uname -a: Linux kvm 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux On Mon, Oct 10, 2016 at 10:04 PM, Charles Lepple <clepple at gmail.com> wrote: > > On Oct 6, 2016, at 7:26 PM, Lane Russell <lanerussell028 at gmail.com> wrote: > > Ubuntu Server 16.04.1 LTS > NUT 2.7.2-4ubuntu1

On Jan 2, 2015, at 1:07 PM, Mike Raath <raathm at gmail.com> wrote: > I built a single VM to monitor the UPS (Ubuntu Server 14.04 i386) and installed NUT on the box from the apt packages. I set it up as per the previous box with the blazer_usb driver and all goes well, for a while. Initially, the UPS reports correctly via upsc, but after a while I get the "Data stale" error,

Hello, I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine except the following: After I disconnect the UPS the upsd write "Data for UPS [apc] is stale - check driver" in /var/log/messages. In the same second it tells "UPS [apc] data is no longer stale". This repeats all the time the ups is disconnected: Jan 25 14:45:03 degpn026w226 kernel: usb

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this:

A couple of years ago, Arnaud helped me get my Apollo Line Interactive UPS working, using the blazer_usb driver. Now I've run into another problem, having rebuilt my HP Proliant Microserver into an ESXi 5.5 managed hypervisor with various VMs. One of the VMs is a FreeNAS server which manages the storage for the other VMs so graceful shutdowns are important. I built a single VM to monitor the

Have done more Googling and searching around the system. Found that /lib/udev/rules.d/52-nut-usbups.rules has been changed to 62 by others and also in Sid (2.7.4) so gave that a shot. Will post back with results. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Monday, October 10, 2016 10:51 PM To: nut-upsuser at lists. alioth. debian. org

On Oct 11, 2016, at 10:07 PM, Daniel Shields wrote: > > No joy. Reverted. A wrong number for the udev rules file would prevent the driver from starting at all due to permissions errors. It is possible that 52 and 62 are currently in the acceptable range. > > From: Daniel Shields <grungelizard9 at hotmail.com> > Sent: Tuesday, October 11, 2016 9:19 PM > To: nut-upsuser

Charles Lepple wrote, On 12/4/2013 4:11 PM: > On Dec 4, 2013, at 3:52 PM, Kris Jordan wrote: > >> Roger Price wrote, On 12/4/2013 12:35 PM: >>> I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch