check-openmanage errors after upgrade of openmanage

[Ashcor Technologies]

> On Wed, Apr 27, 2011 at 8:28 AM, Trond Hasle Amundsen wrote:

> Trond Hasle Amundsen <t.h.amundsen at usit.uio.no> writes:
>
>> Are you using check_openmanage with NRPE or similar in local mode, or
>> checking via SNMP?
>
> I have an idea of what the problem might be. Can you try either of the
> development versions of check_openmanage available here:
>
>   http://folk.uio.no/trondham/software/check_openmanage.html#download
>
> Regards,
> -- 
> Trond H. Amundsen <t.h.amundsen at usit.uio.no>


Trond,

I ran check_openmanage.exe --only storage locally and it worked fine.

I then changed the NSC.ini to have:

command[check_openmanage]=check_openmanage.exe --only storage

and restarted the NSCLient++ (x64) service in test mode.

the results:

d NSClient++.cpp(1106) Injecting: check_openmanage:
d NSClient++.cpp(1142) Injected Result: WARNING 'Problem running 
'omreport chass is fans': Error! No fan probes found on this 
system.<br/>Problem running 'omreport chassis temps': Error! No 
temperature probes found on this system.<br/>Proble m running 'omreport 
chassis volts': Error! No voltage probes found on this system.'

I've looked on your site for the dev versions and am happy to try them 
but don't see a zip with the .exe.  Is there an .exe available for the 
dev?  also, which dev version would you prefer I try, 3.6 or 3.7?

thanks again for all your help with this, you've been awesome!

Jeff

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
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