RE: Monitoring IPv6 website
"Frank Bulk" <[email protected]> Fri, 29 Aug 2014 08:32:32 -0500
| Newsgroups | gmane.network.nagios.plugins |
|---|---|
| Message-ID | <001001cfc38d$b0022790$100676b0$__40059.7180975184$1409319187$gmane$org@iname.com> |
But there is! Try with a typical webbrowser or wget! root@nagios:/tmp# wget -6 www.timewarnercable.com --2014-08-29 08:31:57-- http://www.timewarnercable.com/ Resolving www.timewarnercable.com... 2001:1998:840:b001::7 Connecting to www.timewarnercable.com|2001:1998:840:b001::7|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://www.timewarnercable.com/en/residential.html [following] --2014-08-29 08:31:57-- http://www.timewarnercable.com/en/residential.html Reusing existing connection to www.timewarnercable.com:80. HTTP request sent, awaiting response... 200 OK Length: 101218 (99K) [text/html] Saving to: âindex.htmlâ 100%[======================================================================= ======================================>] 101,218 389K/s in 0.3s 2014-08-29 08:31:58 (389 KB/s) - âindex.htmlâ root@nagios:/tmp# So is something broken with check_http? Regards, Frank -----Original Message----- From: Hugo van der Kooij [mailto:[email protected]] Sent: Wednesday, August 27, 2014 8:38 AM To: Monitoring Plugins Users Subject: RE: Monitoring IPv6 website Frank, Blame them! Ignore them. But there is simply no HTTP server listening on that IPv6 host. -----Oorspronkelijk bericht----- I monitor over 60 IPv6-enabled websites and the only one that's giving me grief is TWC: root@nagios:/usr/lib/nagios/plugins# ./check_http -6 -H www.timewarnercable.com CRITICAL - Socket timeout after 10 seconds root@nagios:/usr/lib/nagios/plugins# root@nagios:/usr/lib/nagios/plugins# ./check_http -6 -H www.timewarnercable.com -v GET / HTTP/1.1 User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15) Connection: close Host: www.timewarnercable.com CRITICAL - Socket timeout after 10 seconds root@nagios:/usr/lib/nagios/plugins# Anyone else see this? Why is check_http struggling here, while all other sites work fine? Frank