2006/1/13, Kurt Roeckx <[EMAIL PROTECTED]>:
yup, better but still not fixed!
What are your current MAXAGE and DEADTIME values?
Please also send me an "upsc" output.
On Fri, Jan 13, 2006 at 10:25:09PM +0100, Arnaud Quette wrote:
> Hi Kurt,
>
> > Jan 10 16:39:04 intrepid upsd[1693]: Startup successful
> > [...]
> > Jan 10 16:43:54 intrepid upsd[1693]: Data for UPS [myups] is stale - check
> > driver
> > Jan 10 16:43:57 intrepid upsd[1693]: UPS [myups] data is no longer stale
[...]
>
> > We'll see what happens during the next few days/weeks.
This is how the log continues:
Jan 12 11:18:03 intrepid upsd[1693]: Data for UPS [myups] is stale - check driver
Jan 12 11:18:08 intrepid upsmon[1696]: Poll UPS [EMAIL PROTECTED] failed - Data stale
Jan 12 11:18:08 intrepid upsmon[1696]: Communications with UPS [EMAIL PROTECTED] lost
Jan 12 11:18:09 intrepid upsd[1693]: UPS [myups] data is no longer stale
Jan 12 11:18:13 intrepid upsmon[1696]: Communications with UPS [EMAIL PROTECTED] established
Jan 12 23:07:44 intrepid upsd[1693]: Data for UPS [myups] is stale - check driver
Jan 12 23:07:45 intrepid upsd[1693]: UPS [myups] data is no longer stale
Jan 13 09:14:16 intrepid upsd[1693]: Data for UPS [myups] is stale - check driver
Jan 13 09:14:16 intrepid upsd[1693]: UPS [myups] data is no longer stale
Jan 13 17:18:38 intrepid upsd[1693]: Data for UPS [myups] is stale - check drive
Jan 13 17:18:39 intrepid upsmon[1696]: Poll UPS [EMAIL PROTECTED] failed - Data stale
Jan 13 17:18:39 intrepid upsmon[1696]: Communications with UPS [EMAIL PROTECTED] lost
Jan 13 17:18:40 intrepid upsd[1693]: UPS [myups] data is no longer stale
Jan 13 17:18:44 intrepid upsmon[1696]: Communications with UPS [EMAIL PROTECTED] established
Jan 13 22:24:52 intrepid upsd[1693]: Data for UPS [myups] is stale - check driver
Jan 13 22:24:52 intrepid upsd[1693]: UPS [myups] data is no longer stale
It looks much better than before.
yup, better but still not fixed!
What are your current MAXAGE and DEADTIME values?
What I really don't like is the "Communications with UPS
lost" messages from upsmon. And each time I have those
the driver seems to have gotten stale too.
Note that it's not a big problem as it's simply that the driver doesn't have enough time to answer upsd in the timely fashion, as the driver polls all data during each update loop. This will be solved when mge-shut is merged into newhidups as I've already done the necessary in the later (interrupt/notification support and flow optimisation).
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/
