check_http high response time

[abrist]

Does a tcp check experience the same looong delay>?

Code: Select all

/usr/local/nagios/libexec/check_tcp -H http://www.google.com -p 443
/usr/local/nagios/libexec/check_tcp -H http://www.google.com -p 80

If so, I bet eloyd is absolutely on point.

[elia_anc]

Yes, tcp check has the quite same loooong result:

Code: Select all

check_tcp -H www.google.com -p 80 -t 30
TCP OK - 5.184 second response time on port 80|time=5.184422s;;;0.000000;30.000000

Code: Select all

check_tcp -H www.google.com -p 443 -t 30
TCP OK - 10.191 second response time on port 443|time=10.191447s;;;0.000000;30.000000

I can't understand what can slow down only this kind of connection...if someone has any idea, please help me.

Thanks for the support.

[eloyd]

Your traceroute may hold a clue. You go out through at least seven private IP address space hops (hops 1, 2, and 4-7) before hitting public IP. Any one of those could be slowing you down.

traceroute to www.caseinlegnobernardidasolo.it (46.252.193.11), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.656 ms 0.867 ms 1.105 ms
2 192.168.1.1 (192.168.1.1) 6.185 ms 6.516 ms 6.514 ms
3 * * *
4 172.17.217.165 (172.17.217.165) 47.101 ms 49.679 ms 49.862 ms
5 172.17.216.117 (172.17.216.117) 63.154 ms 172.17.216.105 (172.17.216.105) 57.938 ms 172.17.216.109 (172.17.216.109) 63.356 ms
6 172.17.12.45 (172.17.12.45) 66.701 ms 52.208 ms 53.250 ms
7 172.17.10.69 (172.17.10.69) 56.277 ms 172.17.6.105 (172.17.6.105) 58.178 ms 62.586 ms
8 bundle-ether12.milano50.mil.seabone.net (93.186.128.233) 62.882 ms 63.469 ms 69.674 ms
9 xe-3-0-3.milano51.mil.seabone.net (195.22.205.111) 64.096 ms 64.244 ms 64.380 ms
10 * * *
11 ae-0-11.bar2.Milan1.Level3.net (4.69.142.190) 50.736 ms 53.521 ms 51.995 ms
12 * * *
13 * * *
14 ae-93-93.ebr3.Frankfurt1.Level3.net (4.69.163.13) 72.507 ms ae-83-83.ebr3.Frankfurt1.Level3.net (4.69.163.9) 65.331 ms ae-93-93.ebr3.Frankfurt1.Level3.net (4.69.163.13) 66.243 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 ae-128-3514.edge6.Amsterdam1.Level3.net (4.69.162.230) 76.597 ms 79.270 ms ae-127-3513.edge6.Amsterdam1.Level3.net (4.69.162.226) 83.996 ms
20 THE-GO-DADD.edge6.Amsterdam1.Level3.net (213.19.195.26) 84.202 ms 90.569 ms 90.782 ms
21 ip-208-109-115-134.ip.secureserver.net (208.109.115.134) 91.385 ms 91.965 ms ip-208-109-115-142.ip.secureserver.net (208.109.115.142) 65.703 ms
22 ip-208-109-115-146.ip.secureserver.net (208.109.115.146) 65.988 ms ip-208-109-115-138.ip.secureserver.net (208.109.115.138) 66.433 ms ip-208-109-115-146.ip.secureserver.net (208.109.115.146) 66.410 ms
23 ip-188-121-33-49.ip.secureserver.net (188.121.33.49) 67.172 ms ip-208-109-115-170.ip.secureserver.net (208.109.115.170) 68.699 ms ip-188-121-33-49.ip.secureserver.net (188.121.33.49) 72.735 ms
24 ip-208-109-115-170.ip.secureserver.net (208.109.115.170) 72.308 ms ip-46-252-193-11.ip.secureserver.net (46.252.193.11) 67.584 ms ip-208-109-115-170.ip.secureserver.net (208.109.115.170) 65.760 ms

[sreinhardt]

Agreed, looks like between your immidiate gateway 192.168.1.1 and 172.17.217.165 hop 3 seems to either not respond or timeout, and it also just happens to be the hop where your response time goes from single digits to 50+ ms.