Am 14.04.2011 um 13:26 schrieb Trond Hasle Amundsen:
Helmut Wollmersdorfer <[email protected]> writes:
At one time we had a battery that didn't finish charging for a week,
called Dell and got a replacement battery. This was during a regular
charge cycle. In your case I would give it a few more days.
Thx for your experience - I will be patient.
Also I tried to '--blacklist bat_charge=0,0' (and other
combinations), but
blacklisting does not work.
Look in the debug output for the battery ID, which consists of the
controller number and battery number with colon as delimiter. In your
case it would be
--blacklist bat_charge=0:0
or simply use 'all':
--blacklist bat_charge=all
Oh, my fault not reading the docs carefully enough;-)
But, as we in fact did experience a case where the battery never
finished charging I would advice against this. We just ignore the
battery charge warnings unless they persist for days. It can be
annoying, but we decided that we can live with it :)
Agreed. IMHO it's better to have annoying warnings about (maybe)
degraded components then a complete outage, because e.g. one of the
redundant components was out of order for some time and the second
also died.
Cheers
Helmut Wollmersdorfer
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
