Page 1 of 1

check_http warning

Posted: Wed Jan 28, 2015 6:13 am
by rlinux57
Getting critical notification:

HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 864 bytes in 0.005 second response time

How to resolve it. ?
I've manually check it. it seems to be ok.
HTTP OK: HTTP/1.1 200 OK - 348 bytes in 0.002 second response time |time=0.001759s;5.000000;15.000000;0.000000 size=348B;;;0

Re: check_http warning

Posted: Wed Jan 28, 2015 9:19 am
by rlinux57
I have rotate the logs,restart httpd,restart nagios server and service, restart xinetd, stop iptables. All the possible solutions come into my mind had implemented but the error still same.

Kindly help me....

Re: check_http warning

Posted: Wed Jan 28, 2015 11:56 am
by slansing
Can you share both your nagios command definition for this service, and the manual command you were running that came through fine? Thanks.

Re: check_http warning

Posted: Wed Jan 28, 2015 10:32 pm
by rlinux57
Here's the command i put manually:

command# /usr/lib64/nagios/plugins/check_http -H HOSTNAME
[output]
HTTP OK: HTTP/1.1 200 OK - 348 bytes in 0.002 second response time |time=0.001660s;;;0.000000 size=348B;;;0


Here's the command definition:
# 'check_http' command definition
define command{
command_name check_http
command_line $USER1$/check_http -I $HOSTADDRESS$ $ARG1$ -t 20
}

I'm using this command definition without timeout "-t 20" but no effect take place.

Re: check_http warning

Posted: Thu Jan 29, 2015 1:05 am
by Box293
Your test and command use two different arguments.

Your manual test uses -H
-H, --hostname=ADDRESS
Host name argument for servers using host headers (virtual host)
Append a port to include it in the header (eg: example.com:5000)

Your command uses -I
-I, --IP-address=ADDRESS
IP address or name (use numeric address if possible to bypass DNS lookup).

Also, you've given us the command, but not the service definition so we don't know what is in your $ARG1$ field

Re: check_http warning

Posted: Thu Jan 29, 2015 1:38 am
by rlinux57
Wow that's the great, it seems to be a minor changes but the issue is resolved. :)
But we were using it with "-I" since the server was first configured.
Thanks for your cooperation.