Nut upsuser - Jun 2016 - 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.
you are right. The exit code is exactly what I need for nagios monitoring.

When I invoke upsc multiple times, the data is sometimes stale, sometimes not.

Current log output (I specifically didn't fix the issue yet):

Jun 27 14:56:08 server upsd: UPS [apcsmart] data is no longer stale
Jun 27 14:56:08 server upsd[3123]: UPS [apcsmart] data is no longer stale
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:56:36 server upsmon: Poll UPS [apcsmart at localhost] failed - Data
stale
Jun 27 14:56:41 server upsmon: Poll UPS [apcsmart at localhost] failed - Data
stale
Jun 27 14:56:46 server upsmon: Poll UPS [apcsmart at localhost] failed - Data
stale
..
Jun 27 14:58:36 server upsmon: Poll UPS [apcsmart at localhost] failed - Data
stale
Jun 27 14:58:38 server upsd: UPS [apcsmart] data is no longer stale
Jun 27 14:58:38 server upsd[3123]: UPS [apcsmart] data is no longer stale
Jun 27 14:58:54 server upsd[3123]: Data for UPS [apcsmart] is stale - check
driver
Jun 27 14:58:54 server upsd: Data for UPS [apcsmart] is stale - check driver
Jun 27 14:58:56 server upsmon: Poll UPS [apcsmart at localhost] failed - Data
stale
> > driver.name: usbhid-ups
> > driver.parameter.pollfreq: 30
> > driver.parameter.pollinterval: 2
> 
> You can tune these parameters to avoid the stale condition, at the expense
> of slightly longer latency for updates. The smaller `pollinterval`
> (seconds between poll cycles) is used for items marked
> "HU_FLAG_QUICK_POLL" in the HID tables:
> https://github.com/networkupstools/nut/blob/master/drivers/apc-hid.c#L301
> and the `pollfreq` value is used for polling the rest.
> 
> More information here: http://networkupstools.org/docs/man/usbhid-ups.html
> (I think the interrupt stuff applies to APC models with USB ID 051d:0002)
> 
> If needed, we can look at the debug output to see what is going on, but
> for whatever reason, a few "data stale" messages over the course
of a day
> seems normal for many USB UPS interfaces.
it's running fine for months normally. You are right again, I've checked
the logs
back to 2016-05-06 and there are a few "Data stale" messages over the
course of the day.

I think I'll leave the polling frequency on the default value and
just add monitoring to get notified if the data is stale for a longer time
period.

Thanks a lot Charles, that was really helpful.

Thomas

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 disconnect/reconnect message pair in dmesg, you might want to try
swapping out the USB cable.

-- 
Charles Lepple
clepple at gmail

On Monday, 27. June 2016 22:32:50 Charles Lepple wrote:
> 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 disconnect/reconnect message pair in dmesg, you might want
> to try swapping out the USB cable.
there are a few rare USB reconnect messages in the log archive.

This specific UPS is also connected via Ethernet for external monitoring,
we highly suspect the firmware sometimes has trouble when
accessed via USB and Ethernet at the same time. If the issue persists,
I'll try to swap the USB cable, but I wouldn't hold my breath ;)

Thanks,
Thomas