Check_http status 503 gives 200 OK

[Jaap van Arragon]

Hello,

I¹m trying to use the check_http plugin to verify if one of our website is
available. 

When I check our website it gives me a 200 OK status code back even when the
website isn¹t available en the URL gives me a 503 status code through the
browser.

After some searching I came across the post below:

http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485

This states that there is a bug in check_http. The only thing is that the
post is from 2003 so I expect that the necessary changes are already in the
new release. 

Things I¹ve tried:

- recompiled the latest version of the check_http plugin but the necessary
changes seems to be integrated there already.
- updated the plugins package to the latest version for our release

Check:
/usr/local/nagios/libexec/check_http -I <ip address> -u http://<url> -w1 -c2

Packages:

ii nagios-images 0.5
ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
ii nagios-plugins 1.4.14-1ubuntu1
ii nagios-plugins-basic 1.4.14-1ubuntu1
ii nagios-plugins-standard 1.4.14-1ubuntu1
ii nagios3 3.2.0-4ubuntu2.2
ii nagios3-cgi 3.2.0-4ubuntu2.2
ii nagios3-common 3.2.0-4ubuntu2.2
ii nagios3-core 3.2.0-4ubuntu2.2
ii nagiosgrapher 1.7.1-1

Does anyone know why it gives me a status 200 OK back? At the moment I can't
rely on my Nagios checks..

Thank you in advance

Regards
Jaap



------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
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