A little over an hour ago, I had a connection-refused, so since I had just grabbed the monitor that Discipulus mentioned earlier, I started running it:
> pm_ip_monitor.pl -c 20 -s 60 Thu Aug 22 09:03:49 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 3.704645 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 2.420785 seconds (timeout 15 s +econds) -------------------------------------------------------------------- Thu Aug 22 09:04:55 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 2.406652 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 2.42126 seconds (timeout 15 se +conds) -------------------------------------------------------------------- Thu Aug 22 09:06:00 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 2.405922 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 2.422154 seconds (timeout 15 s +econds) -------------------------------------------------------------------- Thu Aug 22 09:07:05 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 2.421456 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 3.828308 seconds (timeout 15 s +econds) -------------------------------------------------------------------- Thu Aug 22 09:08:11 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 2.428386 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 2.407986 seconds (timeout 15 s +econds) -------------------------------------------------------------------- Thu Aug 22 09:09:16 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 500 Can't conn +ect to 66.39.54.27:443 (No connection could be made because the targe +t machine actively refused it.) took 2.412528 seconds (timeout 15 sec +onds) perlmonks.org @ https://216.92.34.251/index.pl? 500 Can't conn +ect to 216.92.34.251:443 (No connection could be made because the tar +get machine actively refused it.) took 2.454082 seconds (timeout 15 s +econds) -------------------------------------------------------------------- Thu Aug 22 09:10:21 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl? 200 OK 27.8066 + Kb (28474 bytes) in 0.852321 seconds 32.6246 Kb/s perlmonks.org @ https://216.92.34.251/index.pl? 200 OK 27.8066 + Kb (28474 bytes) in 0.382289 seconds 72.7372 Kb/s --
(Times at UTC-0700, so my it means the outage I saw was from 16:03 (or earlier) to 16:09 UTC.)
When I was getting a response again, I checked pm server stats, and it didn't list any problems. I waited until after 17:00 UTC, in case it was behind in updating the page, but even at 17:25, it said the 16:00 UTC hour had no issues. Since the monitor script was actively getting 500 errors, not just timing out, it seems to me that they might be checking two different things. Well, maybe it is a routing difference; but previously, when I've had the connection-refused, I get it whether through my wifi or through my phone network, and often through an external is-it-down site. Unfortunately, this time, I didn't think to confirm with external route whether it was more generally down.
And it is interesting that most of the full hours have had 585-615 access counts, whereas the 16:00 hour only had 528 -- which is about 5/6 of the normal, which would correspond to about 10 minutes in the hour without any accesses, which matches with my ~10min of connection-refused. cavac, are you sure it's properly logging when an error occurs? Or maybe it's only specific errors that yours logs, and the error I was seeing isn't one of them?
In reply to Re^8: super slow
by pryrt
in thread super slow
by Danny
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |