[Nut-upsuser] mge-shut and hardware error on MGE Pulsar Evolution 800

[Philippe Marzouk]

On Mon, Sep 10, 2007 at 09:12:36PM +0200, Arjen de Korte wrote:
> 
> > My MGE Pulsar Evolution 800 had some hardware troubles (it may be the
> > batteries according to the manual). The fault was not detected so the
> > power was cut to the load and nothing appears in the log files.
> 
> Please be as specific as possible to describing what kind of problem you
> had. Which driver (and interface) are you using and which NUT version are
> we talking about.

I am on Debian unstable and have official  Nut 2.2.0 package installed.

I use the mge-shut driver (serial as that is what the s in shut means).
This is historical on my part as I was the original author of the driver
when it was still called mge-ellipse.

When I got home after work, my computer was off and my UPS was beeping
with the fault led blinking.
I tried to reset the UPS by powering it off and disconnecting it from
the wall but when I switched it back on and powered up the display it
would start beeping again and the fault led started to blink again.

That seems likely to be a hardware problem. As the UPS is already 4
years old batteries are a likely candidate (and seems to be what the
beeping and led blinking means according to the manual).

> 
> > Arnaud: do you know if the UPS have some way to report this kind of
> > troubles to the PC so that NUT can handle it with a shutdown sequence ?
> 
> Note that the only *automatic* shutdown NUT supports, is for a low battery
> situation, since that might not need user intervention to clear. Chances
> are that there are ways to detect the problem you're having (depending on
> what driver you're using), but I doubt that this will result in NUT
> initiating a shutdown. It might throw an alarm, but this usually means
> that it still requires user intervention to deal with/correct the
> situation.
> 

Yes I understand only LB condition initiates the shutdown sequence. I
don't know if the protocol contains any provision to inform the computer
a hardware problem has occured, that was the meaning of my question
because if it is available some support for it would be great.
I would have liked to fine something in my log files. I know the
problem occured between 14:15 and 14:29 but not much :(

Philippe