On Tue, Sep 11, 2007 at 11:03:47AM +0200, Arjen de Korte wrote: > >>> 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 :( > >> I guess it was a power outage and the battery failed the moment it > >> really had to provide power. Regarding the age of the battery, this is > >> quite a likely failure mode. > > I have another UPS which did not record any power failure according to > > upsmon so it may be during an automatic test of the UPS that the fault > > occured. > > That of course, is also a possibility. In which case, there is probably > nothing we can *ever* do about this. If everything looks normal before the > tests, but the UPS fails during the test, we're toast. There can be a > number of failures for this, not limited to the battery alone (a relay > failing for instance, which is a nasty failure mode for line interactive > UPS'es or bypass switches). >
I tried newmge-shut which has a lot more information available. I ran a quick battery test with report no error but made the UPS start beeping and the a deep battery test which really reported an error and set the RB status and caused upsmon to report a warning message on console. This seems to me a hardware bug as the quick test did not report anything wrong. I ordered two sets of batteries as my older MGE Ellipse model is also in bad shape. This is a good reminder that a test from time to time is good pratice :) Philippe _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
