Re: [Nagios-users] Check_http status 503 gives 200 OK
Hello, Does anyone know why it gives me a 200 back? If you need more info, I will gladly provide it ;-) Thank you. Regards, Jaap On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: > 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 -u http:// -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@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
Re: [Nagios-users] Check_http status 503 gives 200 OK
You said u are using it like so: Check: /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2 Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url its causing problems. Maybe its replying on the IP, but not on the URL your providing. You prob only need one or the other if im not mistaken Cheers! On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon wrote: > Hello, > > Does anyone know why it gives me a 200 back? > > If you need more info, I will gladly provide it ;-) > > Thank you. > > Regards, > > Jaap > > > On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: > > > 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 -u http:// > -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@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 > -- Christianity: The belief that some cosmic Jewish Zombie can make you live forever if you symbolically eat his flesh and telepathically tell him that you accept him as your master, so he can remove an evil force from your soul that is present in humanity because a rib-woman was convinced by a talking snake to eat from a magical tree. Makes perfect sense! -- 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@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
Re: [Nagios-users] Check_http status 503 gives 200 OK
Thank you for your reply. I¹ve tried the check without the ip adress option but it makes no difference. Any other ideas? Thanks. On 11/19/12 2:29 PM, "Ryan Edwards" wrote: > You said u are using it like so: > > Check: > /usr/local/nagios/libexec/check_http -I -u http:// -w1 > -c2 > > Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url > its causing problems. Maybe its replying on the IP, but not on the URL your > providing. You prob only need one or the other if im not mistaken > > Cheers! > > > On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon > wrote: >> Hello, >> >> Does anyone know why it gives me a 200 back? >> >> If you need more info, I will gladly provide it ;-) >> >> Thank you. >> >> Regards, >> >> Jaap >> >> >> On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: >> >>> > 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 -u http:// -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@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 > > -- 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@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
Re: [Nagios-users] Check_http status 503 gives 200 OK
Your example /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2 is a proxy request! -I = ip address to connect to -H = HTTP/1.1 Host Header -u = relative url to fetch without protocol infos like http:// some examples check nagios.org OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time |time=1.703114s;;;0.00 size=54919B;;;0 OMD[gearman]:~/lib/nagios/plugins$ host nagios.org nagios.org has address 96.126.126.159 ok, nagios .org runns on 96.126.126.159 lets check a non existing page. we got 404! OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H nagios.org -u /404 HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response time |time=0.536015s;;;0.00 size=17141B;;;0 lets ask nagios.org for icinga.org ;) and we will get a 302 OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H icinga.org -u / HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time |time=1.837209s;;;0.00 size=242B;;;0 Joerg Am 19.11.2012 um 17:14 schrieb Jaap van Arragon : > Thank you for your reply. > > I’ve tried the check without the ip adress option but it makes no difference. > > Any other ideas? > > Thanks. > > > On 11/19/12 2:29 PM, "Ryan Edwards" wrote: > >> You said u are using it like so: >> >>Check: >>/usr/local/nagios/libexec/check_http -I -u http:// -w1 >> -c2 >> >> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url >> its causing problems. Maybe its replying on the IP, but not on the URL your >> providing. You prob only need one or the other if im not mistaken >> >> Cheers! >> >> >> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon >> wrote: >>> Hello, >>> >>> Does anyone know why it gives me a 200 back? >>> >>> If you need more info, I will gladly provide it ;-) >>> >>> Thank you. >>> >>> Regards, >>> >>> Jaap >>> >>> >>> On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: >>> >>> > 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 -u http:// -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@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 >> >> > -- > 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@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/n
Re: [Nagios-users] Check_http status 503 gives 200 OK
Hey Joerg, The 4xx and 3xx error are handeld correctly but not the 5xx error ;-) any ideas? Regards, Jaap _ From: Joerg Linge [mailto:pitchf...@ederdrom.de] To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net] Sent: Mon, 19 Nov 2012 18:07:52 +0100 Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK Your example /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2 is a proxy request! -I = ip address to connect to -H = HTTP/1.1 Host Header -u = relative url to fetch without protocol infos like http:// some examples check nagios.org OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time |time=1.703114s;;;0.00 size=54919B;;;0 OMD[gearman]:~/lib/nagios/plugins$ host nagios.org nagios.org has address 96.126.126.159 ok, nagios .org runns on 96.126.126.159 lets check a non existing page. we got 404! OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H nagios.org -u /404 HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response time |time=0.536015s;;;0.00 size=17141B;;;0 lets ask nagios.org for icinga.org ;) and we will get a 302 OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H icinga.org -u / HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time |time=1.837209s;;;0.00 size=242B;;;0 Joerg Am 19.11.2012 um 17:14 schrieb Jaap van Arragon : > Thank you for your reply. > > I’ve tried the check without the ip adress option but it makes no difference. > > Any other ideas? > > Thanks. > > > On 11/19/12 2:29 PM, "Ryan Edwards" wrote: > >> You said u are using it like so: >> >>Check: >>/usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2 >> >> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url its causing problems. Maybe its replying on the IP, but not on the URL your providing. You prob only need one or the other if im not mistaken >> >> Cheers! >> >> >> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon wrote: >>> Hello, >>> >>> Does anyone know why it gives me a 200 back? >>> >>> If you need more info, I will gladly provide it ;-) >>> >>> Thank you. >>> >>> Regards, >>> >>> Jaap >>> >>> >>> On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: >>> >>> > 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 -u http:// -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 >>> >
Re: [Nagios-users] Check_http status 503 gives 200 OK
Please provide a complete example! check_http works correct since years Joerg Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" : > Hey Joerg, > > The 4xx and 3xx error are handeld correctly but not the 5xx error ;-) > > any ideas? > > Regards, > Jaap > From: Joerg Linge [mailto:pitchf...@ederdrom.de] > To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net] > Sent: Mon, 19 Nov 2012 18:07:52 +0100 > Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK > > > Your example > > /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2 > > is a proxy request! > > -I = ip address to connect to > -H = HTTP/1.1 Host Header > -u = relative url to fetch without protocol infos like http:// > > some examples > > check nagios.org > > OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org > HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time > |time=1.703114s;;;0.00 size=54919B;;;0 > > > OMD[gearman]:~/lib/nagios/plugins$ host nagios.org > nagios.org has address 96.126.126.159 > > ok, nagios .org runns on 96.126.126.159 > lets check a non existing page. we got 404! > > OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H > nagios.org -u /404 > HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response > time |time=0.536015s;;;0.00 size=17141B;;;0 > > lets ask nagios.org for icinga.org ;) and we will get a 302 > > OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H > icinga.org -u / > HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time > |time=1.837209s;;;0.00 size=242B;;;0 > > Joerg > > Am 19.11.2012 um 17:14 schrieb Jaap van Arragon : > > > Thank you for your reply. > > > > I’ve tried the check without the ip adress option but it makes no > > difference. > > > > Any other ideas? > > > > Thanks. > > > > > > On 11/19/12 2:29 PM, "Ryan Edwards" wrote: > > > >> You said u are using it like so: > >> > >> Check: > >> /usr/local/nagios/libexec/check_http -I -u http:// -w1 > >> -c2 > >> > >> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url > >> its causing problems. Maybe its replying on the IP, but not on the URL > >> your providing. You prob only need one or the other if im not mistaken > >> > >> Cheers! > >> > >> > >> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon > >> wrote: > >>> Hello, > >>> > >>> Does anyone know why it gives me a 200 back? > >>> > >>> If you need more info, I will gladly provide it ;-) > >>> > >>> Thank you. > >>> > >>> Regards, > >>> > >>> Jaap > >>> > >>> > >>> On 11/16/12 11:54 AM, "Jaap van Arragon" wrote: > >>> > >>> > 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 -u http:// > >>> > -w1 -c2 > >>> > > >>> > Packages: > >>> > > >>> > ii nagios-images 0.5 > >>> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04
Re: [Nagios-users] Check_http status 503 gives 200 OK
Herewith
define service{
use generic-service_24x7
host_name www1
service_description check http
check_command check_http! -u
http://www.testsomething.com -w 5 -c 8
}
This gives me a
HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
Back.
But in the browser the check gives me a
503 statuscode back.
The Nagios check_http script isn't detecting this 503 error message.
Regards,
Jaap
On 11/20/12 8:20 AM, "Joerg Linge" wrote:
> Please provide a complete example!
> check_http works correct since years
>
> Joerg
>
> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" :
>
>> Hey Joerg,
>>
>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>>
>> any ideas?
>>
>> Regards,
>> Jaap
>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>>
>>
>> Your example
>>
>> /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2
>>
>> is a proxy request!
>>
>> -I = ip address to connect to
>> -H = HTTP/1.1 Host Header
>> -u = relative url to fetch without protocol infos like http://
>>
>> some examples
>>
>> check nagios.org
>>
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>> |time=1.703114s;;;0.00 size=54919B;;;0
>>
>>
>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>> nagios.org has address 96.126.126.159
>>
>> ok, nagios .org runns on 96.126.126.159
>> lets check a non existing page. we got 404!
>>
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> nagios.org -u /404
>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response
>> time |time=0.536015s;;;0.00 size=17141B;;;0
>>
>> lets ask nagios.org for icinga.org ;) and we will get a 302
>>
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> icinga.org -u /
>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>> |time=1.837209s;;;0.00 size=242B;;;0
>>
>> Joerg
>>
>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
>>
>>> Thank you for your reply.
>>>
>>> I¹ve tried the check without the ip adress option but it makes no
>>> difference.
>>>
>>> Any other ideas?
>>>
>>> Thanks.
>>>
>>>
>>> On 11/19/12 2:29 PM, "Ryan Edwards" wrote:
>>>
>>>> You said u are using it like so:
>>>>
>>>> Check:
>>>> /usr/local/nagios/libexec/check_http -I -u http:// -w1
>>>> -c2
>>>>
>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url
>>>> its causing problems. Maybe its replying on the IP, but not on the URL your
>>>> providing. You prob only need one or the other if im not mistaken
>>>>
>>>> Cheers!
>>>>
>>>>
>>>> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon
>>>> wrote:
>>>>> Hello,
>>>>>
>>>>> Does anyone know why it gives me a 200 back?
>>>>>
>>>>> If you need more info, I will gladly provide it ;-)
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Jaap
>>>>>
>>>>>
>>>>> On 11/16/12 11:54 AM, "Jaap van Arragon" wrote:
>>>>>
>>>>>> 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
>>>>>>
>>>>
Re: [Nagios-users] Check_http status 503 gives 200 OK
again
check_http -H -u http://www.testsomething.com
is a proxy request. NOT an valid HTTP request
Joerg
Am 20.11.2012 um 08:35 schrieb Jaap van Arragon :
> Herewith
>
> define service{
>use generic-service_24x7
>host_name www1
>service_description check http
>check_command check_http! -u
> http://www.testsomething.com -w 5 -c 8
> }
>
> This gives me a
>
> HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
>
> Back.
>
>
> But in the browser the check gives me a
>
> 503 statuscode back.
>
> The Nagios check_http script isn't detecting this 503 error message.
>
> Regards,
>
> Jaap
>
>
> On 11/20/12 8:20 AM, "Joerg Linge" wrote:
>
>> Please provide a complete example!
>> check_http works correct since years
>>
>> Joerg
>>
>> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" :
>>
>>> Hey Joerg,
>>>
>>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>>>
>>> any ideas?
>>>
>>> Regards,
>>> Jaap
>>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>>>
>>>
>>> Your example
>>>
>>> /usr/local/nagios/libexec/check_http -I -u http:// -w1 -c2
>>>
>>> is a proxy request!
>>>
>>> -I = ip address to connect to
>>> -H = HTTP/1.1 Host Header
>>> -u = relative url to fetch without protocol infos like http://
>>>
>>> some examples
>>>
>>> check nagios.org
>>>
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>>> |time=1.703114s;;;0.00 size=54919B;;;0
>>>
>>>
>>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>>> nagios.org has address 96.126.126.159
>>>
>>> ok, nagios .org runns on 96.126.126.159
>>> lets check a non existing page. we got 404!
>>>
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>>> nagios.org -u /404
>>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response
>>> time |time=0.536015s;;;0.00 size=17141B;;;0
>>>
>>> lets ask nagios.org for icinga.org ;) and we will get a 302
>>>
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>>> icinga.org -u /
>>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>>> |time=1.837209s;;;0.00 size=242B;;;0
>>>
>>> Joerg
>>>
>>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
>>>
>>>> Thank you for your reply.
>>>>
>>>> I¹ve tried the check without the ip adress option but it makes no
>>>> difference.
>>>>
>>>> Any other ideas?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On 11/19/12 2:29 PM, "Ryan Edwards" wrote:
>>>>
>>>>> You said u are using it like so:
>>>>>
>>>>> Check:
>>>>> /usr/local/nagios/libexec/check_http -I -u http:// -w1
>>>>> -c2
>>>>>
>>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url
>>>>> its causing problems. Maybe its replying on the IP, but not on the URL
>>>>> your
>>>>> providing. You prob only need one or the other if im not mistaken
>>>>>
>>>>> Cheers!
>>>>>
>>>>>
>>>>> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon
>>>>> wrote:
>>>>>> Hello,
>>>>>>
>>>>>> Does anyone know why it gives me a 200 back?
>>>>>>
>>>>>> If you need more info, I will gladly provide it ;-)
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Jaap
>>>>>>
>>>>>>
>>>>>> On 11/16/12 11:54 AM, "Jaap van Arragon"
>>>>>> wrote:
>>>&
Re: [Nagios-users] Check_http status 503 gives 200 OK
He's not using host headers in his definition.
On Tue, Nov 20, 2012 at 12:05 AM, Joerg Linge wrote:
> again
>
> check_http -H -u http://www.testsomething.com
>
> is a proxy request. NOT an valid HTTP request
>
> Joerg
>
> Am 20.11.2012 um 08:35 schrieb Jaap van Arragon >:
>
> > Herewith
> >
> > define service{
> >use generic-service_24x7
> >host_name www1
> >service_description check http
> >check_command check_http! -u
> > http://www.testsomething.com -w 5 -c 8
> > }
> >
> > This gives me a
> >
> > HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
> >
> > Back.
> >
> >
> > But in the browser the check gives me a
> >
> > 503 statuscode back.
> >
> > The Nagios check_http script isn't detecting this 503 error message.
> >
> > Regards,
> >
> > Jaap
> >
> >
> > On 11/20/12 8:20 AM, "Joerg Linge" wrote:
> >
> >> Please provide a complete example!
> >> check_http works correct since years
> >>
> >> Joerg
> >>
> >> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" <
> j.vanarra...@lukkien.com>:
> >>
> >>> Hey Joerg,
> >>>
> >>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
> >>>
> >>> any ideas?
> >>>
> >>> Regards,
> >>> Jaap
> >>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
> >>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
> >>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
> >>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
> >>>
> >>>
> >>> Your example
> >>>
> >>> /usr/local/nagios/libexec/check_http -I -u http://
> -w1 -c2
> >>>
> >>> is a proxy request!
> >>>
> >>> -I = ip address to connect to
> >>> -H = HTTP/1.1 Host Header
> >>> -u = relative url to fetch without protocol infos like http://
> >>>
> >>> some examples
> >>>
> >>> check nagios.org
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
> >>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
> >>> |time=1.703114s;;;0.00 size=54919B;;;0
> >>>
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
> >>> nagios.org has address 96.126.126.159
> >>>
> >>> ok, nagios .org runns on 96.126.126.159
> >>> lets check a non existing page. we got 404!
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
> >>> nagios.org -u /404
> >>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second
> response
> >>> time |time=0.536015s;;;0.00 size=17141B;;;0
> >>>
> >>> lets ask nagios.org for icinga.org ;) and we will get a 302
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
> >>> icinga.org -u /
> >>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
> >>> |time=1.837209s;;;0.00 size=242B;;;0
> >>>
> >>> Joerg
> >>>
> >>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon <
> j.vanarra...@lukkien.com>:
> >>>
> >>>> Thank you for your reply.
> >>>>
> >>>> I¹ve tried the check without the ip adress option but it makes no
> >>>> difference.
> >>>>
> >>>> Any other ideas?
> >>>>
> >>>> Thanks.
> >>>>
> >>>>
> >>>> On 11/19/12 2:29 PM, "Ryan Edwards" wrote:
> >>>>
> >>>>> You said u are using it like so:
> >>>>>
> >>>>> Check:
> >>>>> /usr/local/nagios/libexec/check_http -I -u http://
> -w1
> >>>>> -c2
> >>>>>
> >>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and
> the url
> >>>>> its causing problems. Maybe its replying on the IP, but not on the
> URL your
> >>>>> providing. You prob only need one or the other if im not mistaken
> >>>&g
Re: [Nagios-users] Check_http status 503 gives 200 OK
Jaap, if you'd use check_http correctly, as the others mentioned, it would
work.
It just happens that https://latitude.google.com shows a 503 error right
this moment and for curiosity's sake I tested it:
# ./check_http -H latitude.google.com -S
HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 1119 bytes in 0.071
second response time |time=0.070649s;;;0.00 size=1119B;;;0
As you see, it works as it should if used correctly.
On Tue, Nov 20, 2012 at 10:26 AM, Travis Runyard wrote:
> He's not using host headers in his definition.
>
>
> On Tue, Nov 20, 2012 at 12:05 AM, Joerg Linge wrote:
>
>> again
>>
>> check_http -H -u http://www.testsomething.com
>>
>> is a proxy request. NOT an valid HTTP request
>>
>> Joerg
>>
>> Am 20.11.2012 um 08:35 schrieb Jaap van Arragon > >:
>>
>> > Herewith
>> >
>> > define service{
>> >use generic-service_24x7
>> >host_name www1
>> >service_description check http
>> >check_command check_http! -u
>> > http://www.testsomething.com -w 5 -c 8
>> > }
>> >
>> > This gives me a
>> >
>> > HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
>> >
>> > Back.
>> >
>> >
>> > But in the browser the check gives me a
>> >
>> > 503 statuscode back.
>> >
>> > The Nagios check_http script isn't detecting this 503 error message.
>> >
>> > Regards,
>> >
>> > Jaap
>> >
>> >
>> > On 11/20/12 8:20 AM, "Joerg Linge" wrote:
>> >
>> >> Please provide a complete example!
>> >> check_http works correct since years
>> >>
>> >> Joerg
>> >>
>> >> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" <
>> j.vanarra...@lukkien.com>:
>> >>
>> >>> Hey Joerg,
>> >>>
>> >>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>> >>>
>> >>> any ideas?
>> >>>
>> >>> Regards,
>> >>> Jaap
>> >>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>> >>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>> >>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>> >>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>> >>>
>> >>>
>> >>> Your example
>> >>>
>> >>> /usr/local/nagios/libexec/check_http -I -u http://
>> -w1 -c2
>> >>>
>> >>> is a proxy request!
>> >>>
>> >>> -I = ip address to connect to
>> >>> -H = HTTP/1.1 Host Header
>> >>> -u = relative url to fetch without protocol infos like http://
>> >>>
>> >>> some examples
>> >>>
>> >>> check nagios.org
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>> >>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>> >>> |time=1.703114s;;;0.00 size=54919B;;;0
>> >>>
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>> >>> nagios.org has address 96.126.126.159
>> >>>
>> >>> ok, nagios .org runns on 96.126.126.159
>> >>> lets check a non existing page. we got 404!
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> >>> nagios.org -u /404
>> >>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second
>> response
>> >>> time |time=0.536015s;;;0.00 size=17141B;;;0
>> >>>
>> >>> lets ask nagios.org for icinga.org ;) and we will get a 302
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> >>> icinga.org -u /
>> >>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>> >>> |time=1.837209s;;;0.00 size=242B;;;0
>> >>>
>> >>> Joerg
>> >>>
>> >>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon <
>> j.vanarra...@lukkien.com>:
>> >>>
>> >>>> Thank you for your reply.
>> >>>>
>> >&
