Warnings/errors with check_openmanage plugin

Gianluca Varenni gianluca.varenni at gmail.com
Thu Jan 14 19:30:49 CET 2010


I spoke too soon. The new build works ok on my T610 server, but it generates 
an internal error on a 750 server

root at tinman:/home/nagios/plugins# ./check_openmanage -H homer -t 180 -d
   System:      PowerEdge 750
   ServiceTag:  XXXXXXX                  OMSA version:    5.0.0
   BIOS/date:   XXXXXXXXXXXXXX           Plugin version:  3.5.5-beta1
-----------------------------------------------------------------------------
   Storage Components
=============================================================================
  STATE  |    ID    |  MESSAGE TEXT
---------+----------+--------------------------------------------------------
      OK |        0 | Controller 0 [CERC SATA 1.5/6ch] is Ready
      OK |    0:0:0 | Array Disk 0:0 [250GB] on ctrl -1 is Online
      OK |    0:0:1 | Array Disk 0:1 [250GB] on ctrl -1 is Online
      OK |      0:0 | Logical drive 0 'Windows Disk 0' [RAID-1, 232.80 GB] 
on ctrl 0 is Ready
      OK |      0:0 | Connector 0 [SATA] on controller 0 is Ready
-----------------------------------------------------------------------------
   Chassis Components
=============================================================================
  STATE  |  ID  |  MESSAGE TEXT
---------+------+------------------------------------------------------------
      OK |    1 | Memory module 1 [DIMM1_A, 512 MB] is Ok
      OK |    2 | Memory module 2 [DIMM2_A, 512 MB] is Ok
      OK |    3 | Memory module 3 [DIMM1_B, 512 MB] is Ok
      OK |    4 | Memory module 4 [DIMM2_B, 512 MB] is Ok
      OK |    1 | Chassis fan 1 [System Blower]: 3479
      OK |    2 | Chassis fan 2 [System Memory Fan]: 8881
      OK |    3 | Chassis fan 3 [System PCI Fan]: 6250
      OK |    0 | Temperature Probe 0 [System Temp] reads 24 C (min=10/5, 
max=45/50)
      OK |    1 | Temperature Probe 1 [CPU Temp] reads 35 C (min=10/5, 
max=80/85)
      OK |    0 | Processor 0 [Intel Pentium 4 3.00GHz] is Enabled
      OK |    0 | Voltage sensor 0 [CPU Voltage] is 1.310 V
      OK |    1 | Voltage sensor 1 [Battery Voltage] is 3.136 V
      OK |    2 | Voltage sensor 2 [2.6V MB] is 2.597 V
      OK |    3 | Voltage sensor 3 [VTT Voltage] is 1.298 V
      OK |    4 | Voltage sensor 4 [3.3V MB] is 3.356 V
      OK |    5 | Voltage sensor 5 [3.3V AUX] is 3.373 V
      OK |    6 | Voltage sensor 6 [5V MB] is 4.992 V
      OK |    7 | Voltage sensor 7 [12V MB] is 12.250 V
      OK |    8 | Voltage sensor 8 [5V AUX] is 5.031 V
      OK |    9 | Voltage sensor 9 [2.5V VGA] is 2.503 V
      OK |   10 | Voltage sensor 10 [1.5V MB] is 1.485 V
      OK |   11 | Voltage sensor 11 [1.2V LAN1] is 1.225 V
      OK |   12 | Voltage sensor 12 [1.2V LAN2] is 1.205 V
      OK |    0 | Chassis intrusion 0 detection: Ok (Not Breached)
-----------------------------------------------------------------------------
   Other messages
=============================================================================
  STATE  |  MESSAGE TEXT
---------+-------------------------------------------------------------------
      OK | ESM log health is Ok (less than 80% full)

INTERNAL ERROR: Use of uninitialized value in join or string at 
./check_openmanage line 1345.
INTERNAL ERROR: Use of uninitialized value in join or string at 
./check_openmanage line 1345.

Let me know if you need any snmpwalk output.

Have a nice day
GV


--------------------------------------------------
From: "Trond Hasle Amundsen" <t.h.amundsen at usit.uio.no>
Sent: Thursday, January 14, 2010 3:12 AM
To: "Gianluca Varenni" <gianluca.varenni at gmail.com>
Cc: <nagios-users at lists.sourceforge.net>
Subject: Re: [Nagios-users] Warnings/errors with check_openmanage plugin

> "Gianluca Varenni" <gianluca.varenni at gmail.com> writes:
>
>> Here they are
>>
>> --------------
>> List of Virtual Disks on Controller PERC 6/i Integrated (Embedded)
>>
>> Controller PERC 6/i Integrated (Embedded)
>> ID                       : 0
>> Status                   : Ok
>> Name                     : Virtual Disk 0
>> State                    : Ready
>> HotSpare Policy violated : Not Assigned
>> Virtual Disk Bad Blocks  : Not Applicable
>> Secured                  : Not Applicable
>> Progress                 : Not Applicable
>> Layout                   : RAID-1
>> Size                     : 148.50 GB (159450660864 bytes)
>> Device Name              : Windows Disk 0
>> Bus Protocol             : SATA
>> Media                    : HDD
>> Read Policy              : No Read Ahead
>> Write Policy             : Write Back
>> Cache Policy             : Not Applicable
>> Stripe Element Size      : 64 KB
>> Disk Cache Policy        : Enabled
>>
>> ID                       : 1
>> Status                   : Ok
>> Name                     : DATA
>> State                    : Ready
>> HotSpare Policy violated : Not Assigned
>> Virtual Disk Bad Blocks  : Not Applicable
>> Secured                  : Not Applicable
>> Progress                 : Not Applicable
>> Layout                   : RAID-5
>> Size                     : 2,792.50 GB (2998424043520 bytes)
>> Device Name              : Windows Disk 1
>> Bus Protocol             : SATA
>> Media                    : HDD
>> Read Policy              : No Read Ahead
>> Write Policy             : Write Back
>> Cache Policy             : Not Applicable
>> Stripe Element Size      : 64 KB
>> Disk Cache Policy        : Enabled
>
> Ok, this looks perfectly normal.
>
>> root at tinman:~# snmpwalk -v2c -c public odyssey
>> 1.3.6.1.4.1.674.10893.1.20.140
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.1.1 = INTEGER: 1
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.1.4 = INTEGER: 4
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.2.1 = STRING: "Virtual 
>> Disk
>> 0"
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.2.4 = STRING: "DATA"
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.3.1 = STRING: "Windows 
>> Disk
>> 0"
>> SNMPv2-SMI::enterprises.674.10893.1.20.140.1.1.3.4 = STRING: "Windows 
>> Disk
>> 1"
> [...]
>
> The results from snmpwalk also looks OK, except for the fact that the
> last number jumps from 1 to 4. Where is 2 and 3? The plugin assumes that
> these indexes in the OIDs are sequential, which is clearly wrong. Though
> this situation is rare (never seen it before) the plugin should deal and
> the fact that it doesn't is a bug.
>
> I have a modified version of the plugin available here:
>
>  http://folk.uio.no/trondham/tmp/
>
> Can you give it a try to see if this one performs better?
>
> I'm curious about the cause of this problem. Have you perhaps created a
> couple of virtual disks that were later deleted? It would be interesting
> to see if a restart of OMSA, reboot or powercycle resets the indexes,
> but please help debug the plugin before attempting this :)
>
> 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





More information about the Users mailing list