check_http problem with version 3.0rc2

[Hendrik Bäcker]

Wes Hegge schrieb:
> Hello everyone,
> 
> I  have this command working on version 2 of Nagios but have not been 
> able to get it to work on version 3.0rc2.  Plugins are version 1.4.11.
> 
> Here is the command:
> define command{
>         command_name    check_http_backhaul_trango
>         command_line    $USER1$/checkk_http -H $HOSTADDRESS$ -a :rabbit 
> -r "var rfAssociated = 1;"
>         }
> 
Copy and Paste error or did you called it realy checkkkkkkk_http? ;)

> 
> If I run the command from the command line as the nagios user I get:
> HTTP OK HTTP/1.0 200 OK - 1.196 second response time 
> |time=1.195612s;;;0.000000 size=12225B;;;0
> 
> Looks Good! Exactly what I expect.  Now when I look at the 'Service 
> Detail' I have this:
> 001-To-040  Check TBH Status  CRITICAL <then dates about last check and 
> downtime> (null)
> 

Even if there were any problems with Nagios you should see some plugin 
output after state and before <then dates about...>

> It looks like Nagios is not picking up the return value from the 
> check_http command.  I have check the log file it has nothing.
> 
> Any way to get a more detailed log output?
> 
Well.... nagios.log would be a beginning.

-
Hendrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2185 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080307/76873d3e/attachment.bin>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- 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