Monitoring IPv6 website

Frank Bulk ( frnkblk at
Wed Aug 27 17:25:34 CEST 2014

Thanks, Jens.  But if I drop the "-H" it works fine.  What is the difference
between the two checks?

root at nagios:/usr/lib/nagios/plugins# ./check_http -6
GET / HTTP/1.0
User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
Connection: close is 669 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Date: Wed, 27 Aug 2014 15:24:41 GMT
Server: Apache
Cache-Control: max-age=1800
Expires: Wed, 27 Aug 2014 15:54:41 GMT
Content-Length: 325
Connection: close
Content-Type: text/html; charset=iso-8859-1
Set-Cookie: TWC-COOKIE-webcms-twc-sg=MNEHKIEE; Path=/
**** CONTENT ****
<title>301 Moved Permanently</title>
<h1>Moved Permanently</h1>
<p>The document has moved <a
<address>Apache Server at Port 80</address>

HTTP OK: HTTP/1.1 301 Moved Permanently - 669 bytes in 0.100 second response
time |time=0.100085s;;;0.000000 size=669B;;;0
root at nagios:/usr/lib/nagios/plugins#


-----Original Message-----
From: Help [ at] On
Behalf Of Jens Link
Sent: Wednesday, August 27, 2014 9:50 AM
To: help at
Subject: Re: Monitoring IPv6 website

"Frank Bulk (" <frnkblk at> writes:

> Anyone else see this?  Why is check_http struggling here, while all other
> sites work fine?

I just tried with telnet and ran tcpdump in another screen "window" looks
like the server does not want to talk to the rest of the world. there is
a TCP handshake but nothing more. 

| Foelderichstr. 40   | 13595 Berlin, Germany           | +49-151-18721264 |
| | jabber: jenslink at | ---------------  |


More information about the Help mailing list