[Nagiosplug-help] check_http 500 error

[Javier D'Ovidio]

Thank you Thomas, I actually tried that already (I think I tried every
single option with check_http)

What I can't figure out is why would nagios report an http 500 and running
exactly the same command from a shell it works perfectly fine:


This is the HTTP Check Service CGI for myhost.mydomain.net:
Status Information:HTTP CRITICAL: HTTP/1.1 500 Internal Server Error -
720 bytes in 0.201 second response time
Performance Data:time=0.201368s;3.000000;5.000000;0.000000 size=720B;;;0


This is from a shell:
./check_http -H myhost.mydomain.net
HTTP OK: HTTP/1.1 200 OK - 279 bytes in 0.002 second response time
|time=0.001871s;;;0.000000 size=279B;;;0

I tried with Curl and that works (I get a 200). Does anyone know about any
kind of debug I can do? I'm not sure where to start as everything looks fine
from a command line.



Regards.
Javier.



On Mon, Jan 24, 2011 at 11:32 PM, Thomas Guyot-Sionnest <dermoth at aei.ca>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-01-21 10:46 AM, Javier D'Ovidio wrote:
>> Hello All:
>> This is my first post to this mailing list so be nice with me :P I'm
>> facing a few issues with the check_http plugin. I'm checking an apache
>> on a host using check_http. Looking at the Nagios CGI I can see the
>> service in a CRITICAL state with the following information:
>>
>> Status Information:HTTP CRITICAL: HTTP/1.1 500 Internal Server Error -
>> 720 bytes in 0.201 second response time
>> Performance Data:time=0.201368s;3.000000;5.000000;0.000000 size=720B;;;0
>>
>>
>> Now, when I run the check_http on the command line, I get a different
answer:
>>
>> ./check_http -H myhost.mydomain.net
>> HTTP OK: HTTP/1.1 200 OK - 279 bytes in 0.002 second response time
>> |time=0.001871s;;;0.000000 size=279B;;;0
>>
>> This is my command definition:
>>
>> define command{
>>         command_name    check_site_http
>>         command_line    $USER1$/check_http -H $HOSTADDRESS$ -w 5 -c 7 -t
8
>>         }
>>
>>
>> As you can see, its very simple. Did anyone seen something like this
>> in the past? I have no idea why this might be happening
>
> $HOSTADDRESS$ is usually the IP-address of the server in Nagios. The
> general ways of using check_http are:
>
> 1. -H <vhost> -I <ip_addr>
>
> where vhost is the hostname generally used to access the server and -I
> is the server's IP, This is one way one can test an individual server in
> a pool of load-balancer servers.
>
> 2. -H <hostname>
>
> Where hostname is the server to test - it will be resolver to an ip
> address and check_http will connect to that IP.
>
>
> If #1 is unclear you should read about http name-based virtual hosting.
>
>
> You can also read more about check_http's usage with check_http --help.
>
> Thanks
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk0+NhoACgkQ6dZ+Kt5BchYURgCfZ6und1m3Lmfms7N4LQamovH4
> cuAAoNXhsRKtuo1OpLrG1I/SVJbxxL58
> =Amtq
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/help/attachments/20110128/233585fe/attachment.html>