[Nut-upsuser] false alerts/shutdown

Mon Jun 18 14:45:25 UTC 2007

Hi,

My colleague asked me to mail this info.
It seems the problem only occures when using the usb interface.

With the usb interface:
***********************
[root at testserver /var/log]# /usr/local/ups/bin/upsc 
usb-mge-evolution at localhost
battery.charge: 100
battery.charge.low: 20
battery.charge.restart: 0
battery.runtime: 1200
battery.type: PbAc
battery.voltage: 13.0
driver.name: newhidups
driver.parameter.port: auto
driver.parameter.productid: ffff
driver.parameter.vendorid: 0463
driver.version: 2.0.5
driver.version.data: MGE HID 1.0
driver.version.internal: 0.30
input.frequency: 50.0
input.transfer.boost.low: 184.0
input.transfer.high: 294.0
input.transfer.low: 160.0
input.transfer.trim.high: 265.0
input.voltage: 226.0
outlet.0.desc: Main Outlet
outlet.0.id: 0
outlet.0.switchable: no
outlet.1.autoswitch.charge.low: 0
outlet.1.delay.shutdown: 65535
outlet.1.delay.start: 3
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 1
outlet.1.status: on
outlet.1.switchable: yes
outlet.2.autoswitch.charge.low: 0
outlet.2.delay.shutdown: 65535
outlet.2.delay.start: 6
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 2
outlet.2.status: on
outlet.2.switchable: yes
output.current: 0.40
output.frequency: 50.0
output.voltage: 226.0
output.voltage.nominal: 24.0
ups.beeper.status: enabled
ups.delay.shutdown: -1
ups.delay.start: -1
ups.load: 21
ups.mfr: MGE UPS SYSTEMS
ups.model: Evolution 650
ups.power.nominal: 650
ups.serial: AV0G4602F
ups.status: OL CHRG
ups.test.interval: 604800
ups.test.result: Done and passed

In the log file:
****************

Broadcast message from nutups (Mon Jun 18 12:25:33 2007):

UPS usb-mge-evolution at localhost on battery
Jun 18 12:25:33 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on battery
Jun 18 12:25:33 testserver wall[361]: wall: user nutups broadcasted 1 
lines (44 chars)

Broadcast message from nutups (Mon Jun 18 12:25:43 2007):

UPS usb-mge-evolution at localhost on line power
Jun 18 12:25:43 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on line power
Jun 18 12:25:43 testserver wall[366]: wall: user nutups broadcasted 1 
lines (47 chars)

Broadcast message from nutups (Mon Jun 18 12:26:23 2007):

UPS usb-mge-evolution at localhost on battery
Jun 18 12:26:23 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on battery
Jun 18 12:26:23 testserver wall[370]: wall: user nutups broadcasted 1 
lines (44 chars)

Broadcast message from nutups (Mon Jun 18 12:26:33 2007):

UPS usb-mge-evolution at localhost on line power
Jun 18 12:26:33 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on line power
Broadcast message from nutups (Mon Jun 18 12:42:18 2007):

UPS usb-mge-evolution at localhost on battery
Jun 18 12:42:18 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on battery
Jun 18 12:42:18 testserver wall[385]: wall: user nutups broadcasted 1 
lines (44 chars)

Broadcast message from nutups (Mon Jun 18 12:42:28 2007):

UPS usb-mge-evolution at localhost on line power
Jun 18 12:42:28 testserver upsmon[2872]: UPS usb-mge-evolution at localhost 
on line power
Jun 18 12:42:28 testserver wall[389]: wall: user nutups broadcasted 1 
lines (47 chars)
Broadcast message from nutups (Mon Jun 18 12:42:48 2007):

UPS usb-mge-evolution at localhost battery is low

Broadcast message from nutups (Mon Jun 18 12:42:48 2007):

Executing automatic power-fail shutdown

Broadcast message from nutups (Mon Jun 18 12:42:48 2007):

UPS usb-mge-evolution at localhost on battery

Broadcast message from nutups (Mon Jun 18 12:42:48 2007):

Auto logout and shutdown proceeding

With the serial interface:
**************************
[root at testserver ~]# /usr/local/ups/bin/upsc serial-mge-evolution at localhost
battery.charge: 100
battery.charge.low: 20
battery.runtime: 1200
driver.name: mge-shut
driver.parameter.port: /dev/ttyS0
driver.version: 2.0.5
driver.version.internal: 0.66
input.frequency: 50
input.voltage: 226
outlet.0.desc: Main Outlet
outlet.0.id: 0
outlet.0.switchable: 0
outlet.1.autoswitch.charge.low: 0
outlet.1.delay.shutdown: -1
outlet.1.delay.start: -1
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 1
outlet.1.switch: 1
outlet.1.switchable: 1
outlet.2.autoswitch.charge.low: 0
outlet.2.delay.shutdown: -1
outlet.2.delay.start: -1
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 2
outlet.2.switch: 1
outlet.2.switchable: 1
output.frequency: 50
output.voltage: 226
output.voltage.nominal: 24
ups.delay.shutdown: -1
ups.delay.start: -1
ups.load: 20
ups.mfr: MGE UPS SYSTEMS
ups.model: Evolution 650
ups.power.nominal: 650
ups.serial: AV0G4602F
ups.status: OL CHRG
ups.test.result: Done and passed

in the log file:
****************
no shutdown or "on battery" messages

> -------- Oorspronkelijk bericht --------
> Onderwerp: Re: [Nut-upsuser] false alerts/shutdown
> Van: "Arjen de Korte" <nut+users at de-korte.org>
> Datum: Vr, 15 juni, 2007 12:19 pm
> Aan: "Stijn Gruwier" <sg at schaubroeck.be>
>
>
>   
>>> What makes you think these are false alarms?
>>>       
>> I have 2 reasons for believing these are false alarms:
>>
>> 1) The UPS doesn't beep and none of the status leds change when this
>> occurs. I configured nut to page me for 'on battery' events, and while
>> working in the server room I witnessed how NUT complained but the UPS
>> didn't give a sign. In contrast, when it goes on battery because I
>> pull the plug, it beeps, leds flash, ...
>>     
>
> How long it takes before a UPS starts to beep and whether or not it will
> beep at all for glitches, is something that is rarely specified. Don't
> count on it.
>
>   
>> 2) Three other servers (not backed up by ups) who share the same power
>> distribution unit as the UPS are not affected. If these alarms are
>> real, it means voltage drops to 160V. I thought that would shut a
>> server down.  Maybe you are right and a server can handle this for a
>> few seconds?
>>     
>
> Not necessarily. When a UPS detects a mains glitch, it will usually go
> to battery for a couple of seconds and then return. So even if the power
> fails for just a couple of milliseconds, it will be on battery for a few
> seconds. Most (if not all) servers will tolerate a complete loss of
> input power for at least a full cycle (20 ms) and even longer than that
> for brown outs. So the fact that other systems don't notice this, is no
> indication either.
>
> [...]
>
>   
>> I'm almost sure the mains are OK since the building is less than 2
>> years old.
>>     
>
> That by itself tells nothing. Remember the recent deaths of patients in
> an italian hospital where the builder swapped nitrous oxide and oxygen
> lines? That department was brand new too, but sadly eight people died
> before they found out.
>
>   
>> Also I connected the UPS to another socket across the room to no
>> avail. I agree there might be electrical glitches, but wouldn't the
>> UPS beep then?
>>     
>
> Not necessarily. Many will only start to beep when the mains is really
> out, to prevent nagging people for each and every transient.
>
> To rule out problems with the USB port, could you try connecting this
> UPS via a serial port and the 'mge-shut' driver? You might also run it
> in debug mode, but this will probably result in huge amounts of data
> since the protocol this UPS uses is very verbose.
>
> Best regards, Arjen
>
>
>
>
>  **** DISCLAIMER ****
>  http://www.schaubroeck.be/maildisclaimer.htm
>
>   

 **** DISCLAIMER ****
 http://www.schaubroeck.be/maildisclaimer.htm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20070618/b19551da/attachment.htm 