#staff | Logs for 2024-04-08

« return
[00:57:05] <sylvester> 2024-04-08 02:57:46 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 266.97 ms
[01:02:09] <sylvester> 2024-04-08 03:02:50 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 130.17 ms
[01:24:17] <sylvester> 2024-04-08 03:24:58 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 274.21 ms
[01:26:18] <sylvester> 2024-04-08 03:26:59 04mail.soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 585.49 ms
[01:29:22] <sylvester> 2024-04-08 03:30:03 04mail.soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 0%, RTA = 526.94 ms
[01:39:26] <sylvester> 2024-04-08 03:40:07 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 210.29 ms
[01:41:22] <sylvester> 2024-04-08 03:42:03 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 168.35 ms
[01:44:30] <sylvester> 2024-04-08 03:45:12 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 174.10 ms
[01:51:27] <sylvester> 2024-04-08 03:52:08 04mail.soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 355.92 ms
[01:51:39] <sylvester> 2024-04-08 03:52:20 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 288.30 ms
[01:56:31] <sylvester> 2024-04-08 03:57:12 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 125.35 ms
[01:56:43] <sylvester> 2024-04-08 03:57:24 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.88 ms
[03:00:17] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff
[03:18:39] <sylvester> 2024-04-08 05:19:21 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 151.07 ms
[03:23:44] <sylvester> 2024-04-08 05:24:25 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 139.64 ms
[10:42:09] <sylvester> 2024-04-08 12:42:51 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 128.86 ms
[10:51:29] <sylvester> 2024-04-08 12:52:10 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:52:13] <sylvester> 2024-04-08 12:52:55 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 125.64 ms
[10:56:30] <sylvester> 2024-04-08 12:57:11 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 89795 bytes in 0.938 second response time
[10:59:33] <sylvester> 2024-04-08 13:00:15 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[11:04:37] <sylvester> 2024-04-08 13:05:19 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.36 ms
[11:11:57] <sylvester> 2024-04-08 13:12:39 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[11:17:01] <sylvester> 2024-04-08 13:17:43 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 124.90 ms
[11:29:12] <fab23> still the same as last week https://smokeping.home4u.ch so I will put this checks into maintanance again probably for a week. :(
[11:30:55] <janrinok> Do you think it is your check that is causing it? Can you run less frequently so we can look for correlation?
[11:31:30] <sylvester> 2024-04-08 13:32:11 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[11:31:31] <fab23> if you look at the smokeping graph, the site is not reacable every 5 min for 5 min
[11:33:34] <fab23> janrinok: and it fails from all my locations with IPv6, so it is really a problem on the SN web server side (or their Hoster / ISP). Sure it could be that some intrusion dedection system thinks my probes are evil and blocks them for 5 min. and then allows them again.
[11:34:29] <fab23> but then the why only to the website but not the mail server?
[11:37:53] <janrinok> I cannot answer that question, unfortunately. All you can do is switch it off and see if the problem disappears.
[11:38:49] <fab23> I don't think it does, as others with IPv6 also have confirmed the site occasionally is not reachable
[11:41:54] <janrinok> I suspect that Linode/Akamai are rejigging their hardware to accept IPv6 as much of Europe is already on IPv6 anyway, and the US is converting too but more slowly. Perhaps as someone suggested (you?) they are farming stuff out to others to reduce their own costs?
[12:13:35] <fab23> It does not make sense, that they route traffic to the web server differently then to the mail server, both are in the same IPv6 /64 sub net
[12:37:29] <janrinok> Perhaps the problem is on our servers then - I do not know
[16:40:00] <chromas> they already do ipv6 and don't charge for it (whereas they charge per ipv4) but also that's a lot of rejigging
[20:19:27] <sylvester> 2024-04-08 22:20:09 04soylentnews CRITICAL HTTPS Certificate soylentnews.org00 CRITICAL - Socket timeout after 10 seconds