Is this possible: Debugging Nagios -- logging commands and their exit codes.

[Jan Bessels]

>>> Deborah Martin <Deborah.Martin at Kognitio.com> 25-4-2006 13:49:58
>>>
>As an example, if you run the following command-line from wherever you
have
>the plugins installed :- 

>./check_ping -H localhost -w 3000.0,80% -c 5000.0,100% -p 1

>you would get the following output which Nagios can understand :- 

>PING OK - Packet loss = 0%, RTA = 0.16 ms

>You'd need to amend the -H, -w, -c and -p options to your requirements
of
> course. 

Thanks for the info. As you also suggested I always start with the
commandline. If that works (and only then)  I put the commands in the
.cfg files. Sometimes things go wrong and then it would be great to see
what Nagios is actually executing. Hence logging what exacalty is
executed and their exit status seems a good idea to start the debugging
proces and figure out whats gooing on. 






-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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