check_openmanage

[Eero Volotinen]

2011/4/26 Ashcor Technologies <ashcor at optonline.net>:
>> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
>
>> Ashcor Technologies <ashcor at optonline.net> writes:
>>
>>> Thanks for the reply.  I just realized from your question that I'm
>>> using a pre-compiled .exe version of your check_openmanage from here:
>>>
>>> https://www.monitoringexchange.org/inventory/Check-Plugins/Hardware/check_openmanage-exe
>>>
>>> which was probably created from an older version...
>>
>> Yeah I think it's pretty old. A PE32 executable for Windows is
>> available
>> in the zip and tar.gz archives, and as a single file download:
>>
>>   http://folk.uio.no/trondham/software/check_openmanage.html#download
>>
>> Upgrading to the latest version will probably solve your problem. Let
>> me
>> know if it doesn't.
>>
>> Cheers,
>> --
>> Trond H. Amundsen <t.h.amundsen at usit.uio.no>
>
>
> Ok, now new and exciting changes... no matter what I do I get: WARNING
> PLUGIN TIMEOUT: check_openmanage timed out after 30 seconds.
>
> I have -t 60 set on the check_openmanage command and also on the NRPE
> check command line and in the NSC.ini.  nothing seems to change the
> timout beyond 30 seconds.

I am also experiencing timeout(s) with nsclient++ running vbs-scripts.

Is this related to nsclient++ poor performance on external checks? how
to fix it?

--
Eero

------------------------------------------------------------------------------
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