Nagios 2.03b, plugins 1.4 - no status changes

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Marc Belanger
> Sent: Thursday, April 21, 2005 5:37 PM
> To: nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Nagios 2.03b, plugins 1.4 - no status
changes
> 
> Hey Marc (and others),
> 
> I won't be able to check til tommorow AM. I have a feeling that I'll
see a
> return code of 1 (warning) simply because part of the information is
> getting
> to the monitor console - in the "Status Information" field. The whole
> "WARNING - free disk yadayadayada part). I'll definately check it out
> though.
> 
> I did see the return codes as I was reading through the plugin
developer
> standards/requirements, and was curious how I might leverage that in
> troubleshooting. I'm going to read up on how-to get nagios to react to
> exit
> codes, but if anyone has the abridged version, please share.

It's not modifiable behavior. The nagios plugin architecture was
designed to look for and react to exit codes specifically. Everything
else is just add-on for human consumption.

My suspicion is that check_disk is either not exiting with the proper
code or check_by_ssh isn't reading it and passing it on properly for
some reason.

Your command definitions and the way you are calling them all look fine
and worked for me perfectly, at least from the command line so I believe
you're ok there.

--
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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