Return code of 142 is out of bounds

[Mat W]

there's the FAQ... http://www.nagios.org/faqs/viewfaq.php?faq_id=17

 

I think this can also happen when some checks returns -no- value, or return a string when expecting an integer, etc.  essentially encountering something the plugin isn't expecting which could be leading to "bad exit" from the script.


Can you recreate this from the command line?


-- 
Mat W. - http://www.techadre.com


 


Date: Thu, 18 Jun 2009 10:38:18 +0530
From: victory17 at gmail.com
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Return code of 142 is out of bounds

Hi All,

I am running Nagios 3.0.2 on FC5 server.

I have been encountering this strange error intermittently on a few checks.

(Return code of 142 is out of bounds)

I am using the nagios with snmp (net-snmp-5.2 & net-snmp-5.3) on a few servers.

This normally happens with snmp-load checks or snmp-disk checks.

I could not find anything related to this problem over the internet. Hoping to get a solution to this problem here.

Regards,


_________________________________________________________________
Windows Live™: Keep your life in sync. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090618/b23899ed/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
-------------- next part --------------
_______________________________________________
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