Two of www.ebay.com's six IPs timing out on HTTPv4 request
Our monitoring system reported errors with HTTPv4 requests around 11 pm Central. www.ebay.com has six IPs for me: C:\bin>dig A www.ebay.com +short www.g.ebay.com. 66.135.200.181 66.135.210.61 66.135.210.181 66.211.181.161 66.211.181.181 66.135.200.161 Testing showed that queries to the other four work well, but 66.135.200.181 and 66.211.181.181 time out for me. I used NAGIOS' check_http and httping to check, as I can specify the target IP and it queries the whole page, not just the head. Anyone else seeing this? nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178472 bytes in 0.852 second response time |time=0.852004s;;;0.000000 size=178472B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178930 bytes in 0.945 second response time |time=0.945317s;;;0.000000 size=178930B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178461 bytes in 0.856 second response time |time=0.855919s;;;0.000000 size=178461B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178526 bytes in 0.880 second response time |time=0.880290s;;;0.000000 size=178526B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178432 bytes in 0.854 second response time |time=0.853617s;;;0.000000 size=178432B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178499 bytes in 0.967 second response time |time=0.966769s;;;0.000000 size=178499B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178457 bytes in 0.878 second response time |time=0.877644s;;;0.000000 size=178457B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178484 bytes in 0.850 second response time |time=0.849843s;;;0.000000 size=178484B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178869 bytes in 0.750 second response time |time=0.749532s;;;0.000000 size=178869B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.758 second response time |time=0.757955s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 179005 bytes in 0.754 second response time |time=0.754183s;;;0.000000 size=179005B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.751 second response time |time=0.750797s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178405 bytes in 0.876 second response time |time=0.875883s;;;0.000000 size=178405B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178481 bytes in 0.766 second response time |time=0.765653s;;;0.000000 size=178481B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# nagios:/usr/lib/nagios/plugins# nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.61 -t 5 PING 66.135.210.61:80 (www.ebay.com): connected to 66.135.210.61:80, seq=0 time=249.63 ms connected to 66.135.210.61:80, seq=1 time=214.81 ms connected to 66.135.210.61:80, seq=2 time=232.85 ms connected to 66.135.210.61:80, seq=3 time=220.85 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 214.8/229.5/249.6 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.181 -t 5 PING 66.135.210.181:80 (www.ebay.com): connected to 66.135.210.181:80, seq=0 time=228.37 ms connected to 66.135.210.181:80, seq=1 time=224.12 ms connected to 66.135.210.181:80, seq=2 time=197.35 ms connected to 66.135.210.181:80, seq=3 time=242.46 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 197.4/223.1/242.5 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.200.181 -t 5 PING 66.135.200.181:80 (www.ebay.com): timeout receiving reply from host ^Ctimeout receiving reply from host --- www.ebay.com ping statistics --- 2 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.211.181.181 -t 2 PING 66.211.181.181:80 (www.ebay.com): timeout receiving reply from host timeout receiving reply from host timeout receiving reply from host ^C--- www.ebay.com ping statistics --- 3 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins#
$ for i in `dig a www.ebay.com +short | grep -v www` ; do printf "%-32s%-20s" "`date`" "$i" ; curl -i -s -S -H "Host: www.ebay.com" http://$i/ >/dev/null ; echo $? ; done Wed Jan 22 22:32:52 PST 2014 66.211.181.181 0 Wed Jan 22 22:32:52 PST 2014 66.135.200.161 0 Wed Jan 22 22:32:53 PST 2014 66.135.200.181 0 Wed Jan 22 22:32:54 PST 2014 66.135.210.181 0 Wed Jan 22 22:32:54 PST 2014 66.135.210.61 0 Wed Jan 22 22:32:55 PST 2014 66.211.181.161 0 In English: I have no trouble getting back HTTP content from any of those IPs, and promptly. Source IP is 76.102.14.35, located in Mountain View, CA. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Thu, Jan 23, 2014 at 12:21:04AM -0600, Frank Bulk wrote:
Our monitoring system reported errors with HTTPv4 requests around 11 pm Central.
www.ebay.com has six IPs for me:
C:\bin>dig A www.ebay.com +short www.g.ebay.com. 66.135.200.181 66.135.210.61 66.135.210.181 66.211.181.161 66.211.181.181 66.135.200.161
Testing showed that queries to the other four work well, but 66.135.200.181 and 66.211.181.181 time out for me.
I used NAGIOS' check_http and httping to check, as I can specify the target IP and it queries the whole page, not just the head. Anyone else seeing this?
nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178472 bytes in 0.852 second response time |time=0.852004s;;;0.000000 size=178472B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178930 bytes in 0.945 second response time |time=0.945317s;;;0.000000 size=178930B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178461 bytes in 0.856 second response time |time=0.855919s;;;0.000000 size=178461B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178526 bytes in 0.880 second response time |time=0.880290s;;;0.000000 size=178526B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178432 bytes in 0.854 second response time |time=0.853617s;;;0.000000 size=178432B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178499 bytes in 0.967 second response time |time=0.966769s;;;0.000000 size=178499B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178457 bytes in 0.878 second response time |time=0.877644s;;;0.000000 size=178457B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178484 bytes in 0.850 second response time |time=0.849843s;;;0.000000 size=178484B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178869 bytes in 0.750 second response time |time=0.749532s;;;0.000000 size=178869B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.758 second response time |time=0.757955s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 179005 bytes in 0.754 second response time |time=0.754183s;;;0.000000 size=179005B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.751 second response time |time=0.750797s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178405 bytes in 0.876 second response time |time=0.875883s;;;0.000000 size=178405B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178481 bytes in 0.766 second response time |time=0.765653s;;;0.000000 size=178481B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins#
nagios:/usr/lib/nagios/plugins# nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.61 -t 5 PING 66.135.210.61:80 (www.ebay.com): connected to 66.135.210.61:80, seq=0 time=249.63 ms connected to 66.135.210.61:80, seq=1 time=214.81 ms connected to 66.135.210.61:80, seq=2 time=232.85 ms connected to 66.135.210.61:80, seq=3 time=220.85 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 214.8/229.5/249.6 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.181 -t 5 PING 66.135.210.181:80 (www.ebay.com): connected to 66.135.210.181:80, seq=0 time=228.37 ms connected to 66.135.210.181:80, seq=1 time=224.12 ms connected to 66.135.210.181:80, seq=2 time=197.35 ms connected to 66.135.210.181:80, seq=3 time=242.46 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 197.4/223.1/242.5 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.200.181 -t 5 PING 66.135.200.181:80 (www.ebay.com): timeout receiving reply from host ^Ctimeout receiving reply from host --- www.ebay.com ping statistics --- 2 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.211.181.181 -t 2 PING 66.211.181.181:80 (www.ebay.com): timeout receiving reply from host timeout receiving reply from host timeout receiving reply from host ^C--- www.ebay.com ping statistics --- 3 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins#
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
----- Original Message -----
From: "Jeremy Chadwick" <jdc@koitsu.org>
$ for i in `dig a www.ebay.com +short | grep -v www` ; do printf "%-32s%-20s" "`date`" "$i" ; curl -i -s -S -H "Host: www.ebay.com" http://$i/ >/dev/null ; echo $? ; done
Given the volume, intensity, and duration of the "systemd is the worst designed anti-Unix-Philosophy POS ever and I want to do things to Lennart that would probably get me arrested" rant I just finished with, I can't decide whether to laugh or cry at that pipeline... Cheers, -- jr 'WHY has everyone drunk the Flavor-Aid?' a -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
Thanks for that nice script. I ran it myself (adding the timeout option because it wasn't ever dying). It's still out for me: nagios:/home/fbulk# for i in `dig a www.ebay.com +short | grep -v www` ; do printf "%-32s%-20s" "`date`" "$i" ; curl -i -s -m 15 -S -H "Host: www.ebay.com" http://$i/ >/dev/null ; echo $? ; done Thu Jan 23 06:09:13 CST 2014 66.135.210.61 0 Thu Jan 23 06:09:14 CST 2014 66.135.210.181 0 Thu Jan 23 06:09:15 CST 2014 66.211.181.161 0 Thu Jan 23 06:09:15 CST 2014 66.211.181.181 curl: (28) Operation timed out after 15001 milliseconds with 0 bytes received 28 Thu Jan 23 06:09:30 CST 2014 66.135.200.161 0 Thu Jan 23 06:09:31 CST 2014 66.135.200.181 curl: (28) Operation timed out after 15001 milliseconds with 0 bytes received 28 nagios:/home/fbulk# But the two that fail do have port 80 open for me -- tcping and tcptraceroute confirm that. They're just not sending back any HTTP info. I've tested from 96.31.0.5 and 199.120.69.4. Frank -----Original Message----- From: Jeremy Chadwick [mailto:jdc@koitsu.org] Sent: Thursday, January 23, 2014 12:34 AM To: Frank Bulk Cc: outages@outages.org Subject: Re: [outages] Two of www.ebay.com's six IPs timing out on HTTPv4 request $ for i in `dig a www.ebay.com +short | grep -v www` ; do printf "%-32s%-20s" "`date`" "$i" ; curl -i -s -S -H "Host: www.ebay.com" http://$i/ >/dev/null ; echo $? ; done Wed Jan 22 22:32:52 PST 2014 66.211.181.181 0 Wed Jan 22 22:32:52 PST 2014 66.135.200.161 0 Wed Jan 22 22:32:53 PST 2014 66.135.200.181 0 Wed Jan 22 22:32:54 PST 2014 66.135.210.181 0 Wed Jan 22 22:32:54 PST 2014 66.135.210.61 0 Wed Jan 22 22:32:55 PST 2014 66.211.181.161 0 In English: I have no trouble getting back HTTP content from any of those IPs, and promptly. Source IP is 76.102.14.35, located in Mountain View, CA. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Thu, Jan 23, 2014 at 12:21:04AM -0600, Frank Bulk wrote:
Our monitoring system reported errors with HTTPv4 requests around 11 pm Central.
www.ebay.com has six IPs for me:
C:\bin>dig A www.ebay.com +short www.g.ebay.com. 66.135.200.181 66.135.210.61 66.135.210.181 66.211.181.161 66.211.181.181 66.135.200.161
Testing showed that queries to the other four work well, but 66.135.200.181 and 66.211.181.181 time out for me.
I used NAGIOS' check_http and httping to check, as I can specify the target IP and it queries the whole page, not just the head. Anyone else seeing this?
nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178472 bytes in 0.852 second response time |time=0.852004s;;;0.000000 size=178472B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178930 bytes in 0.945 second response time |time=0.945317s;;;0.000000 size=178930B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178461 bytes in 0.856 second response time |time=0.855919s;;;0.000000 size=178461B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178526 bytes in 0.880 second response time |time=0.880290s;;;0.000000 size=178526B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178432 bytes in 0.854 second response time |time=0.853617s;;;0.000000 size=178432B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178499 bytes in 0.967 second response time |time=0.966769s;;;0.000000 size=178499B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178457 bytes in 0.878 second response time |time=0.877644s;;;0.000000 size=178457B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.61 HTTP OK: HTTP/1.1 200 OK - 178484 bytes in 0.850 second response time |time=0.849843s;;;0.000000 size=178484B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178869 bytes in 0.750 second response time |time=0.749532s;;;0.000000 size=178869B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.758 second response time |time=0.757955s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 179005 bytes in 0.754 second response time |time=0.754183s;;;0.000000 size=179005B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178471 bytes in 0.751 second response time |time=0.750797s;;;0.000000 size=178471B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178405 bytes in 0.876 second response time |time=0.875883s;;;0.000000 size=178405B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.210.181 HTTP OK: HTTP/1.1 200 OK - 178481 bytes in 0.766 second response time |time=0.765653s;;;0.000000 size=178481B;;;0 nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.135.200.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins# ./check_http -H www.ebay.com -I 66.211.181.181 CRITICAL - Socket timeout after 10 seconds nagios:/usr/lib/nagios/plugins#
nagios:/usr/lib/nagios/plugins# nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.61 -t 5 PING 66.135.210.61:80 (www.ebay.com): connected to 66.135.210.61:80, seq=0 time=249.63 ms connected to 66.135.210.61:80, seq=1 time=214.81 ms connected to 66.135.210.61:80, seq=2 time=232.85 ms connected to 66.135.210.61:80, seq=3 time=220.85 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 214.8/229.5/249.6 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.210.181 -t 5 PING 66.135.210.181:80 (www.ebay.com): connected to 66.135.210.181:80, seq=0 time=228.37 ms connected to 66.135.210.181:80, seq=1 time=224.12 ms connected to 66.135.210.181:80, seq=2 time=197.35 ms connected to 66.135.210.181:80, seq=3 time=242.46 ms ^C--- www.ebay.com ping statistics --- 4 connects, 4 ok, 0.00% failed round-trip min/avg/max = 197.4/223.1/242.5 ms nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.135.200.181 -t 5 PING 66.135.200.181:80 (www.ebay.com): timeout receiving reply from host ^Ctimeout receiving reply from host --- www.ebay.com ping statistics --- 2 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins# httping www.ebay.com -G -h 66.211.181.181 -t 2 PING 66.211.181.181:80 (www.ebay.com): timeout receiving reply from host timeout receiving reply from host timeout receiving reply from host ^C--- www.ebay.com ping statistics --- 3 connects, 0 ok, 100.00% failed nagios:/usr/lib/nagios/plugins#
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Frank Bulk -
Jay Ashworth -
Jeremy Chadwick