Return Code of 4

[patrick.morris at hp.com]

Hi Weiner,!

On Thu, 15 Apr 2010, Weiner, Michael wrote:

> Running this at the command line (even as user nagios) succeeds and gives me
> 
> Scratch OK : available tapes 121|Scratch=121;100;20
> 
> However once I add this as a service check to nagios I receive the following:
> 
> Warning: Return code of 4 for check of service 'Scratch_Pool_Check' on host 'my-backup-server' was out of bounds.
> 
> I tried googling for the return code 4 and really came up empty, but read a lot about various other return codes. Does someone on the list do something similar? If so, how? And is anyone able to shed some light on the above Warning?

Your script is returning a result code of 4.  Why is impossible to say
without seeing the script, but on an OK state it should be returning 0,
not 4.

Note that it doesn't matter if the output of the plugin is "Scratch OK,
etc."  All Nagios pays any attention to when determining that state of a
service is that return code, and your script is not returning an "OK" 
code (that would be 0).  What "4" means in this case could very well be
specific to that script.

Without more details about the script it'd be hard to say why it's
returning the wrong result code, but I'd look for something like an
"exit" command and verify that it's returning the right values for
critical, warning, OK and unknown states.

http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN76

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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