Hi,
I need some help with the check_http plugin and websites hosted by weebly.com, here's where I'm at:
- check_http v1.5 , os is SLES 11
- wget http://nagios.weebly.com/ works ok
- check_http -H nagios.weebly.com does not:
suse3:~ # check_http -vv -H nagios.weebly.com
GET / HTTP/1.1
User-Agent: check_http/v1.5 (nagios-plugins 1.5)
Connection: close
Host: nagios.weebly.com
CRITICAL - Socket timeout after 10 seconds
If i use -I instead of -H it works, but I get back the default weebly page, not the nagios.weebly.com website. I've tested some other weebly websites, and I can't check_http any of them.
I've played with all the -f options, but to no avail. I could really use some advice about this.
thanks
check_http and weebly sites
-
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: check_http and weebly sites
When you request that page, is it causing a redirect, are they behind load balancers, or anything else like that? Any more detail that you can give regarding how they differ from a base webserver, and what server is actually serving them would be very helpful.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
-
- Posts: 2
- Joined: Thu Jun 12, 2014 2:03 pm
Re: check_http and weebly sites
Thanks sreinhardt,
it seems to be based on apache, here's the wget -d output:
suse3:~ # wget -d nagios.weebly.com
DEBUG output created by Wget 1.11.4 on linux-gnu.
--2014-06-12 23:13:28-- http://nagios.weebly.com/
Resolving nagios.weebly.com... 199.34.228.53
Caching nagios.weebly.com => 199.34.228.53
Connecting to nagios.weebly.com|199.34.228.53|:80... connected.
Created socket 3.
Releasing 0x0000000000648100 (new refcount 1).
---request begin---
GET / HTTP/1.0
User-Agent: Wget/1.11.4
Accept: */*
Host: nagios.weebly.com
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.0 200 OK
Date: Thu, 12 Jun 2014 21:13:29 GMT
Server: Apache
Set-Cookie: is_mobile=0; path=/; domain=nagios.weebly.com
X-Host: app-64-43.intern.weebly.net
X-UA-Compatible: IE=edge,chrome=1
Connection: close
Content-Type: text/html; charset=UTF-8
---response end---
200 OK
cdm: 1 2
Stored cookie nagios.weebly.com -1 (ANY) / <session> <insecure> [expiry none] is_mobile 0
Length: unspecified [text/html]
Saving to: `index.html.4'
it seems to be based on apache, here's the wget -d output:
suse3:~ # wget -d nagios.weebly.com
DEBUG output created by Wget 1.11.4 on linux-gnu.
--2014-06-12 23:13:28-- http://nagios.weebly.com/
Resolving nagios.weebly.com... 199.34.228.53
Caching nagios.weebly.com => 199.34.228.53
Connecting to nagios.weebly.com|199.34.228.53|:80... connected.
Created socket 3.
Releasing 0x0000000000648100 (new refcount 1).
---request begin---
GET / HTTP/1.0
User-Agent: Wget/1.11.4
Accept: */*
Host: nagios.weebly.com
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.0 200 OK
Date: Thu, 12 Jun 2014 21:13:29 GMT
Server: Apache
Set-Cookie: is_mobile=0; path=/; domain=nagios.weebly.com
X-Host: app-64-43.intern.weebly.net
X-UA-Compatible: IE=edge,chrome=1
Connection: close
Content-Type: text/html; charset=UTF-8
---response end---
200 OK
cdm: 1 2
Stored cookie nagios.weebly.com -1 (ANY) / <session> <insecure> [expiry none] is_mobile 0
Length: unspecified [text/html]
Saving to: `index.html.4'
-
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: check_http and weebly sites
It certainly looks like you must have a loadbalancer there. There are some potential issues with loadbalencers as some like to improperly close the connection when forwarding to the actual server. Would you be able to tcpdump while running a check_http and forward that to us? I can certainly send some commands if that would help too.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.