#staff | Logs for 2024-04-22

« return
[08:50:37] -!- drussell has quit [Ping timeout: 252 seconds]
[08:51:28] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff
[13:50:55] -!- drussell has quit [Ping timeout: 252 seconds]
[13:51:32] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff
[14:02:09] <sylvester> 2024-04-22 16:02:09 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[14:12:17] <sylvester> 2024-04-22 16:12:17 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 44%, RTA = 124.79 ms
[14:17:27] <sylvester> 2024-04-22 16:17:27 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[14:21:37] <sylvester> 2024-04-22 16:21:37 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[14:22:31] <sylvester> 2024-04-22 16:22:31 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 124.92 ms
[14:26:38] <sylvester> 2024-04-22 16:26:38 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 109550 bytes in 1.048 second response time
[14:29:51] <sylvester> 2024-04-22 16:29:51 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[14:34:56] <sylvester> 2024-04-22 16:34:56 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 124.87 ms
[14:42:16] <sylvester> 2024-04-22 16:42:16 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 70%, RTA = 124.36 ms
[14:52:20] <sylvester> 2024-04-22 16:52:20 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 126.69 ms
[14:59:40] <sylvester> 2024-04-22 16:59:40 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[15:01:38] <sylvester> 2024-04-22 17:01:38 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[15:03:39] -!- sylvester has quit [Remote host closed the connection]
[15:03:45] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[15:04:44] <sylvester> 2024-04-22 17:04:44 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 126.55 ms
[15:06:40] <sylvester> 2024-04-22 17:06:39 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 109465 bytes in 1.059 second response time
[15:12:04] <sylvester> 2024-04-22 17:12:04 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[15:12:18] <fab23> oh, the IPv6 check did awake again :) How should we proceed, disable for another week, or remove forever? :)
[15:13:51] <janrinok> Are we still seeing any work being carried out by Akamai, or do you think we have a problem with our configuration?
[15:14:48] <fab23> It could be something on the SN side, but some sysadmin needs to check that, e.g. if something automatically is sometimes blocking IPv6 traffic.
[15:15:46] <janrinok> I would suggest that you just disable it for another week or two. See PM
[15:15:53] <fab23> In my opininon it was never something on Akamai / Linode side, as IPv6 to the IP of the mail.soy does work without any issue, and it is in the same subnetwork.
[15:17:08] <sylvester> 2024-04-22 17:17:08 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 126.18 ms
[15:41:34] <sylvester> 2024-04-22 17:41:34 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[15:46:35] <sylvester> 2024-04-22 17:46:35 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 109435 bytes in 1.076 second response time
[15:52:09] <sylvester> 2024-04-22 17:52:09 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 100%
[15:54:51] <fab23> ok, downtime scheduled for ping / https IPv6 until 2024-04-29 17:53:50 (CEST)
[17:28:13] <drussell> It is rather strange that it is like clockwork responding / not responding
[17:37:18] <fab23> drussell: yes, and that for me really gives the impression, that something on the system itself is blocking / unblocking IPv6.
[17:40:13] <janrinok> how often does it change - perhaps we can tie it into another task on the server that runs periodically
[17:40:43] <fab23> if you look at https://smokeping.home4u.ch every 5 minutes.
[17:41:24] <janrinok> is it toggling on and then off or just going down for a short period every 5 minutes?
[17:46:09] <fab23> I will check manually with ping, as I could not figure out how often smokeping does check, but it looks like on and off for 5 min each.
[17:49:31] <janrinok> thanks fab23 - I don't think audioguy is in a position to look at this at the moment. So it could be a task that runs every 5 mins and toggles the problem, or a task that runs every 10 minutes and knocks it off for 5 minutes each time.
[17:50:34] <fab23> I have currently a 'ping6 -i 30 soylentnews.org' running, will send one packet every 30 seconds.
[17:51:22] <janrinok> OK we will see what happens...
[17:52:41] <janrinok> which one should I be watching? jetstream, logjammer, ?
[17:59:07] <fab23> janrinok: it seems that both of them are in sync, and e.g. batman has also the 5 min pattern, but with less loss, and from buccaneer it seems to be a constant loss. But if I think it through, then smokeping may only test every 5 min. and some of the check always get some packets trough, other only every 5 min.
[18:07:01] <janrinok> thanks - I'm not sure what I can do with that information, but I will look through the software if I can find some time.
[18:12:09] <fab23> janrinok: if it is anything, then it is something on the firewall, as ICMP and HTTPS are blocked.
[18:13:17] <fab23> HTTP probably as well, I don't probe for that.
[18:15:38] <fab23> janrinok: from my manual ping check: https://scratchy.ponz.ch I guess you have the better math brain then I have. :)
[18:16:19] <fab23> janrinok: the icmp_seq= are counted up, when missing, then there was no answer.
[19:54:12] <sylvester> 2024-04-22 21:54:12 04mail.soylentnews CRITICAL IRC Certificate00 CRITICAL - Certificate *.soylentnews.org expires in 12 day(s) (Sun 05 May 2024 03:53:45 AM GMT +0000).