"No response" result code inconsistency in nagios-plugins

[Andreas Ericsson]

Ian Chard wrote:
> Hi,
> 
> There seems to be a general inconsistency in how "no response"
> conditions are handled in some of the plugins.  For example:
> 
> 	check_snmp		UNKNOWN
> 	check_nt		CRITICAL
> 	check_ifoperstatus	WARNING
> 
> I would have thought that a plugin should return UNKNOWN if nothing
> is received unless it's the response itself that's being tested (i.e.
> check_ping should obviously return CRITICAL if no packets are received).
> 

In general it's nice to be told (in large letters, preferrably) that the 
transportation mechanism failed. Most people choose to not receive 
UNKNOWN notifications.

I lobbied some time ago for the inclusion of a -T variable which would 
specify the exit-status in case of network timeouts. The plugin package 
at http://oss.op5.se/nagios deploys this for the check_nt plugin as a 
sort of proof of workability. The syntax is case insensitive and accepts 
any level of ambiguity.

> Do Nagios folk agree, and if so, is it worth logging this as a bug?
> 

Bug, no. Consistency request, sure.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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