<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head></head><body><div style="font-size: 12pt; font-family: Calibri,sans-serif;"><div>I've done it in bash before a while ago, using wget. Though it was more a "download this page every minute and take some data from it" script, there was a bit of error reporting in there too. If I can find it I might be able to bring something to the table. :-)</div><div><br></div><div>Sent from my HTC</div><br><div id="htc_header">----- Reply message -----<br>From: "Duncan Fyfe" <duncanfyfe@domenlas.com><br>To: "The Nottingham Perl Mongers" <nottingham-pm@pm.org><br>Subject: [Nottingham-pm] Monitoring website uptimes<br>Date: Tue, Jul 29, 2014 19:45</div></div><br><pre style="word-wrap: break-word; white-space: pre-wrap;">On 29/07/14 18:35, James Green wrote:
> Hey folks,
>
> Rather than my usual meeting-arranging blather on this list ... I have
> an actual Perl-related question! OK, it's not very Perl related.
>
> Following a bunch of recent conversations about the future of
> search.cpan.org, and the fact it was seemingly down all the time, I've
> started gathering stats on when both it, and metacpan.org, are
> unreachable.
>
> Unfortunately I'm getting a lot of what I suspect are false positives.
> I'm using LWP::UserAgent to get() a specific search page from each
> site, timing out after 30s, and if it hasn't loaded, considering it
> "down" until the next check. This process runs every 2 minutes, from
> cron. Quite often a site will fail to load just once, then be back up
> the next time -- which is as likely to be a transient routing problem
> at my end as an issue at theirs.
>
> Does anyone have experience monitoring the availability of websites,
> or exciting ideas for better approaches to this data?
>
Quick check, details below, but for starters it looks like there might
be a reverse DNS problem with metacpan.org. I'll have a more detailed
look later.
Have fun,
Duncan
=== DETAILS ===
nslookup search.cpan.org
Server: 194.168.4.100
Address: 194.168.4.100#53
Non-authoritative answer:
search.cpan.org canonical name = cpansearch.perl.org.
Name: cpansearch.perl.org
Address: 207.171.7.59
Name: cpansearch.perl.org
Address: 207.171.7.49
wget <a href="http://search.cpan.org/search?query=Moose&mode=all">http://search.cpan.org/search?query=Moose&mode=all</a>
OK
wget <a href="http://207.171.7.59/search?query=Moose&mode=all">http://207.171.7.59/search?query=Moose&mode=all</a>
OK
wget <a href="http://207.171.7.49/search?query=Moose&mode=all">http://207.171.7.49/search?query=Moose&mode=all</a>
OK
nslookup metacpan.org
Server: 194.168.4.100
Address: 194.168.4.100#53
Non-authoritative answer:
Name: metacpan.org
Address: 23.235.37.143
Name: metacpan.org
Address: 23.235.33.143
wget <a href="https://metacpan.org/search?q=Moose">https://metacpan.org/search?q=Moose</a>
OK
wget --no-check-certificate <a href="https://23.235.37.143/search?q=Moose">https://23.235.37.143/search?q=Moose</a>
--2014-07-29 19:04:46-- <a href="https://23.235.37.143/search?q=Moose">https://23.235.37.143/search?q=Moose</a>
Connecting to 23.235.37.143:443... connected.
The certificate's owner does not match hostname ‘23.235.37.143’
HTTP request sent, awaiting response... 500 Domain Not Found
2014-07-29 19:04:46 ERROR 500: Domain Not Found.
wget --no-check-certificate <a href="https://23.235.33.143/search?q=Moose">https://23.235.33.143/search?q=Moose</a>
--2014-07-29 19:05:15-- <a href="https://23.235.33.143/search?q=Moose">https://23.235.33.143/search?q=Moose</a>
Connecting to 23.235.33.143:443... connected.
The certificate's owner does not match hostname ‘23.235.33.143’
HTTP request sent, awaiting response... 500 Domain Not Found
2014-07-29 19:05:15 ERROR 500: Domain Not Found.
nslookup 23.235.37.143
Server: 194.168.4.100
Address: 194.168.4.100#53
** server can't find 143.37.235.23.in-addr.arpa: NXDOMAIN
nslookup 23.235.33.143
Server: 194.168.4.100
Address: 194.168.4.100#53
** server can't find 143.33.235.23.in-addr.arpa: NXDOMAIN
ping -q -c 10 23.235.37.143
PING 23.235.37.143 (23.235.37.143) 56(84) bytes of data.
--- 23.235.37.143 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 25.587/27.657/37.575/3.352 ms
ping -q -c 10 23.235.33.143
PING 23.235.33.143 (23.235.33.143) 56(84) bytes of data.
--- 23.235.33.143 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 29.846/32.689/43.296/3.717 ms
_______________________________________________
Nottingham-pm mailing list
Nottingham-pm@pm.org
<a href="http://mail.pm.org/mailman/listinfo/nottingham-pm">http://mail.pm.org/mailman/listinfo/nottingham-pm</a></pre></body></html>