Nut upsuser - May 2007 - Bogus shutdown

Nut shut down a machine last night when there was no power outage.
When I came in this morning, the UPS was turned off, but it turned on
cleanly and passed its self-test.  The battery was at 62% when I
first checked it, and it's up to 63% now, about 20 minutes later.

The UPS is a Tripp-Lite AVR550U.  I'm running nut version 2.0.3.
I expect to be told to update to a newer version and to quit
using hidups.  Is there anything else?

Here's the relevant section of the log:

May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x8400d0 (0)
May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x840044 (0)
May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x840045 (1)
May 23 20:55:29 galprop hidups[3407]: Ignoring x86 page event 0xffff0091 (1)
May 23 20:55:31 galprop upsmon[3416]: UPS igor at galprop on battery
May 23 20:55:31 galprop wall[29877]: wall: user ups broadcasted 1 lines 
(29 chars)
May 23 20:55:34 galprop hidups[3407]: Unhandled event: 0x8400d0 (1)
May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop on line power
May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop on battery
May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop battery is low
May 23 20:55:36 galprop upsd[3411]: Client ups at 171.64.108.117 set FSD on 
UPS [igor]
May 23 20:55:36 galprop wall[29882]: wall: user ups broadcasted 1 lines 
(29 chars)
May 23 20:55:36 galprop upsmon[3416]: Executing automatic power-fail 
shutdown
May 23 20:55:36 galprop wall[29880]: wall: user ups broadcasted 1 lines 
(32 chars)
May 23 20:55:37 galprop hidups[3407]: Unhandled event: 0x840044 (1)
May 23 20:55:37 galprop hidups[3407]: Unhandled event: 0x840045 (0)
May 23 20:55:37 galprop hidups[3407]: Ignoring x86 page event 0xffff0091 (0)
May 23 20:55:37 galprop wall[29884]: wall: user ups broadcasted 1 lines 
(33 chars)
May 23 20:55:37 galprop wall[29886]: wall: user ups broadcasted 2 lines 
(43 chars)
May 23 20:55:37 galprop upsmon[3416]: Auto logout and shutdown proceeding
May 23 20:55:37 galprop wall[29891]: wall: user ups broadcasted 1 lines 
(37 chars)
May 23 20:55:42 galprop upsd[3411]: Host 171.64.108.117 disconnected 
(read failure)
May 23 20:55:42 galprop shutdown: shutting down for system halt
May 23 20:55:42 galprop init: Switching to runlevel: 0

On 5/24/07, Patrick Nolan <Patrick.Nolan at stanford.edu>
wrote:
> Nut shut down a machine last night when there was no power outage.
> When I came in this morning, the UPS was turned off, but it turned on
> cleanly and passed its self-test.  The battery was at 62% when I
> first checked it, and it's up to 63% now, about 20 minutes later.
Did it ever finish charging?
> The UPS is a Tripp-Lite AVR550U.  I'm running nut version 2.0.3.
> I expect to be told to update to a newer version and to quit
> using hidups.  Is there anything else?
You got it.

I don't want to sound like a broken record, because I assume you've
found the upgrade-from-hidups mantra in the mailing list archives a
few times now. I'm curious, though - is it just that your system
distribution includes 2.0.3, or is there something broken in the newer
versions that's preventing you from using them?
> Here's the relevant section of the log:
>
> May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x8400d0 (0)
this line:

http://boxster.ghz.cc/projects/nut/browser/tags/v2.0.5/drivers/tripplite-hid.c#L54

indicates that 0x8400d0 means that the AC failed, as far as the UPS is
concerned. (This could have been a brownout.)
> May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x840044 (0)
similarly, this means it is no longer charging.
> May 23 20:55:29 galprop hidups[3407]: Unhandled event: 0x840045 (1)
... now discharging
> May 23 20:55:29 galprop hidups[3407]: Ignoring x86 page event 0xffff0091
(1)
> May 23 20:55:31 galprop upsmon[3416]: UPS igor at galprop on battery
so this seems correct, given the three previous 0x84 codes.
> May 23 20:55:34 galprop hidups[3407]: Unhandled event: 0x8400d0 (1)
> May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop on line power
These lines also correlate with each other.
> May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop on battery
> May 23 20:55:36 galprop upsmon[3416]: UPS igor at galprop battery is low
Without seeing the debugging messages, it's hard to say if this was
bogus or not, but it's entirely possible that the battery is weak if
it was only at 62% when you came back.

-- 
- Charles Lepple