Why is check_openmanage so slow on PowerEdge R510?

[Helmut Wollmersdorfer]

Hi,


new to this architecture I installed the monitoring plugin check- 
openmanage and was surprised about the performance:

root at xen10:~# time perl /usr/lib/nagios/plugins/check_openmanage  -d |  
head -n 3
sh: /bin/rpm: not found
    System:      		PowerEdge R510 II        	OMSA version:    6.5.0
    ServiceTag:  	1Z7215J                  		Plugin version:  3.6.5
    BIOS/date:   	1.6.3 02/01/2011        	 	Checking mode:   local

real		0m3.426s
user	0m2.456s
sys		0m0.544s

OS: Debian
root at xen10:~# uname -a
Linux xen10 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011  
x86_64 GNU/Linux

Most calls of check_openmanage (from the shell) take 3 - 4 seconds,  
some with '--only' are faster, but not as fast as omreport:

root at xen10:~# time perl /usr/lib/nagios/plugins/check_openmanage  -- 
only fans
FANS OK - 5 fan probes checked

real	0m0.716s


root at xen10:~# time /opt/dell/srvadmin/bin/omreport chassis fans
Fan Probes Information

Fan Redundancy
Redundancy Status : Full
[...]

real	0m0.037s

In comparison called with the option --help (does nearly nothing) the  
execution time is as expected for loading the perl interpreter and  
compiling the source:

root at xen10:~# time perl /usr/lib/nagios/plugins/check_openmanage  -h
[...]
real	0m0.064s

What can be the reason?

TIA

Helmut Wollmersdorfer


------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
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