check_openmanage 3.5.4 status bug

[Trond Hasle Amundsen]

"McKinlay, Ken" <Ken.McKinlay at curtisswright.com> writes:

> The status hash that is used to translate the voltageProbeStatus appears
> to be incorrect. Instead of %snmp_status, the hash used should be
> %snmp_probestatus. This is at line 3054 in check_openmanage v3.5.4. The
> corrected line reads:
>
> $status   = $snmp_probestatus{$out->{voltageProbeStatus}};
>
> I discovered this issue since one of my Dells has an almost dead battery
> but the check returned " OOPS! Something is wrong with this server, but
> I don't know what. The global system health status is CRITICAL, but
> every component check is OK. This may be a bug in the Nagios plugin,
> please file a bug report."

Hi Ken,

Thanks for the bug report and the patch. I guess that this was never
discovered before, since voltage errors occur rarely. Also good to know
that the little failsafe oops works as intended :)

Your patch will be included in the next release, and a patched beta
version is available here:

  http://folk.uio.no/trondham/tmp/check_openmanage-3.5.5-beta6

Cheers,
-- 
Trond H. Amundsen <t.h.amundsen at usit.uio.no>
Center for Information Technology Services, University of Oslo

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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