#staff | Logs for 2023-06-12

« return
[08:09:56] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[08:09:56] <sylvester> 2023-06-12 10:02:04 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97860 bytes in 4.812 second response time
[08:09:56] <sylvester> 2023-06-12 09:58:16 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.86 ms
[08:09:56] <sylvester> 2023-06-12 09:53:12 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 130.07 ms
[08:09:56] <sylvester> 2023-06-12 09:48:02 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 50%, RTA = 129.75 ms
[08:09:56] <sylvester> 2023-06-12 09:41:59 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:09:56] <sylvester> 2023-06-12 09:32:53 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.79 ms
[08:09:56] <sylvester> 2023-06-12 09:27:43 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 28%, RTA = 129.89 ms
[08:09:56] <sylvester> 2023-06-12 09:07:37 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.82 ms
[08:09:56] <sylvester> 2023-06-12 09:06:59 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97854 bytes in 6.781 second response time
[08:09:56] <sylvester> 2023-06-12 09:00:17 03soylentnews OK PING IPv600 PING OK - Packet loss = 16%, RTA = 129.79 ms
[08:09:56] <sylvester> 2023-06-12 08:56:52 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:09:56] <sylvester> 2023-06-12 08:49:32 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97834 bytes in 8.744 second response time
[08:09:56] <sylvester> 2023-06-12 08:29:24 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:09:56] <sylvester> 2023-06-12 08:20:12 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.93 ms
[08:09:56] <sylvester> 2023-06-12 08:12:04 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 101402 bytes in 6.918 second response time
[08:09:56] <sylvester> 2023-06-12 08:06:57 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:09:57] <sylvester> 2023-06-09 04:47:06 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 123.53 ms
[08:09:57] <sylvester> 2023-06-09 04:42:51 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 130.17 ms
[08:09:58] <sylvester> 2023-06-09 04:42:21 03soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 125.81 ms
[08:09:58] <sylvester> 2023-06-09 04:42:02 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 163.10 ms
[08:09:59] <sylvester> 2023-06-09 04:41:45 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 166.12 ms
[08:09:59] <sylvester> 2023-06-09 04:37:47 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 0%, RTA = 460.56 ms
[08:10:00] <sylvester> 2023-06-09 04:37:17 04soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 379.66 ms
[08:10:00] <sylvester> 2023-06-09 04:36:58 04mail.soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 686.13 ms
[08:10:01] <sylvester> 2023-06-09 04:36:41 04mail.soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 0%, RTA = 705.75 ms
[08:10:01] <sylvester> 2023-06-06 23:06:44 03mail.soylentnews UP00 PING OK - 2 plugins checked, 2 ok
[08:10:02] <sylvester> 2023-06-06 23:05:26 04mail.soylentnews DOWN00 PING CRITICAL - 2 plugins checked, 2 critical (check_host_alive_ipv6, check_host_alive_ipv4) [WARNING - TRUE - COUNT(CRITICAL) 0
[08:10:12] <chromas> 0% loss
[08:10:35] <sylvester> 2023-06-12 10:10:35 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 50%, RTA = 129.98 ms
[08:11:18] <fab23> hm, the order of the messages may be chaotic, they got stuck as sylvester was not in IRC any more.
[08:11:41] <chromas> I was wondering if there's an option to discard unsent messages from it being offline
[08:11:51] <janrinok> does that prevent its useful
[08:11:56] <chromas> but I suppose if there actually was something critical, it'd be nice to have it logged
[08:12:06] <fab23> :)
[08:12:14] <janrinok> its usefullness?
[08:12:16] <chromas> I saw sylvester come in and forgot it was the bot
[08:15:45] <sylvester> 2023-06-12 10:15:45 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 90%, RTA = 129.83 ms
[08:15:45] -!- bryan_ [bryan_!~bryan@136.50.qxv.zr] has joined #staff
[08:16:40] -!- bryan has quit [Ping timeout: 252 seconds]
[08:19:24] <sylvester> 2023-06-12 10:19:24 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:20:50] <sylvester> 2023-06-12 10:20:50 03soylentnews OK PING IPv600 PING OK - Packet loss = 16%, RTA = 129.89 ms
[08:22:50] -!- sylvester has quit [Remote host closed the connection]
[08:22:56] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[08:23:09] <chromas> I think we need to start monitoring whatever box sylvester's running from; seems to have bad internets :)
[08:24:16] <fab23> chromas: it looks like, sylvester is located in Nuremberg (Nürnberg), Bavaria, Germany at Hetzner :)
[08:24:26] <sylvester> 2023-06-12 10:24:25 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97900 bytes in 1.154 second response time
[08:25:27] <fab23> but it more looks like that IPv6 to www SN has difficulties from multiple locations: https://smokeping.home4u.ch
[08:26:51] <chromas> so it's not just the Nurenberg trials that are failing
[08:27:24] <fab23> related to what sylvester reports, it is only from Nurenberg
[08:28:10] <sylvester> 2023-06-12 10:28:10 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.92 ms
[08:28:36] <chromas> heh, "Requests of this client are not permitted."
[08:29:26] <fab23> chromas: ?
[08:30:14] <chromas> doing a whois on the vhost
[08:36:46] <sylvester> 2023-06-12 10:36:46 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:37:57] <chromas> does it scan all the internets or just whatever you put into ?target= ?
[08:40:47] <chromas> ah, putting something else into the target parameter throws an error
[08:43:14] <sylvester> 2023-06-12 10:43:14 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.87 ms
[08:50:34] <sylvester> 2023-06-12 10:50:34 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 90%, RTA = 129.83 ms
[08:56:55] <sylvester> 2023-06-12 10:56:55 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97848 bytes in 8.704 second response time
[09:04:15] <sylvester> 2023-06-12 11:04:15 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[09:05:39] <sylvester> 2023-06-12 11:05:39 03soylentnews OK PING IPv600 PING OK - Packet loss = 16%, RTA = 129.77 ms
[09:13:28] <fab23> chromas: it does only monitor what I have configured
[09:14:24] <sylvester> 2023-06-12 11:14:24 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97879 bytes in 8.798 second response time
[09:14:25] <fab23> chromas: if you just go to https://smokeping.home4u.ch you see what else is there
[09:17:56] <sylvester> 2023-06-12 11:17:56 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 90%, RTA = 127.97 ms
[09:38:05] <sylvester> 2023-06-12 11:38:05 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 50%, RTA = 129.87 ms
[09:43:15] <sylvester> 2023-06-12 11:43:15 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.84 ms
[09:51:45] <sylvester> 2023-06-12 11:51:44 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:06:46] <sylvester> 2023-06-12 12:06:46 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 97960 bytes in 1.261 second response time
[10:33:19] <sylvester> 2023-06-12 12:33:19 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 127.98 ms
[10:40:39] <sylvester> 2023-06-12 12:40:39 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 70%, RTA = 127.97 ms
[10:53:17] <sylvester> 2023-06-12 12:53:17 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[11:00:44] <sylvester> 2023-06-12 13:00:43 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 128.15 ms
[11:08:04] <sylvester> 2023-06-12 13:08:03 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 70%, RTA = 128.10 ms
[11:53:12] <sylvester> 2023-06-12 13:53:12 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 50%, RTA = 129.87 ms
[11:53:27] <sylvester> 2023-06-12 13:53:27 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[11:58:22] <sylvester> 2023-06-12 13:58:22 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.84 ms
[11:58:22] <sylvester> 2023-06-12 13:58:22 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95585 bytes in 4.727 second response time
[12:05:23] <fab23> it looks like something is filtering out IPv6 traffic to www.SN
[12:19:55] <sylvester> 2023-06-12 14:19:54 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[12:24:56] <sylvester> 2023-06-12 14:24:56 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95457 bytes in 1.186 second response time
[12:54:57] <sylvester> 2023-06-12 14:54:57 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[12:58:32] <sylvester> 2023-06-12 14:58:32 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.87 ms
[13:00:06] <sylvester> 2023-06-12 15:00:06 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95527 bytes in 8.949 second response time
[13:02:06] -!- sylvester has quit [Remote host closed the connection]
[13:02:12] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[13:07:26] <sylvester> 2023-06-12 15:07:26 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[13:12:33] <sylvester> 2023-06-12 15:12:33 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95514 bytes in 6.993 second response time
[13:18:27] <sylvester> 2023-06-12 15:18:27 03soylentnews OK PING IPv600 PING OK - Packet loss = 16%, RTA = 129.96 ms
[13:25:46] <sylvester> 2023-06-12 15:25:46 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.71 ms
[13:43:25] <sylvester> 2023-06-12 15:43:24 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[14:00:51] <sylvester> 2023-06-12 16:00:51 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.89 ms
[14:03:30] <sylvester> 2023-06-12 16:03:30 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95830 bytes in 6.860 second response time
[14:08:11] <sylvester> 2023-06-12 16:08:11 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.94 ms
[14:15:02] <sylvester> 2023-06-12 16:15:02 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[14:25:03] <sylvester> 2023-06-12 16:25:03 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95816 bytes in 1.368 second response time
[14:43:17] <sylvester> 2023-06-12 16:43:17 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 28%, RTA = 129.85 ms
[14:48:27] <sylvester> 2023-06-12 16:48:27 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 80%, RTA = 129.95 ms
[14:55:48] <sylvester> 2023-06-12 16:55:48 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[15:10:49] <sylvester> 2023-06-12 17:10:49 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95887 bytes in 1.333 second response time
[15:13:31] <sylvester> 2023-06-12 17:13:31 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 129.86 ms
[20:03:43] <sylvester> 2023-06-12 22:03:43 08soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 16%, RTA = 172.29 ms
[20:08:47] <sylvester> 2023-06-12 22:08:47 03soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 123.93 ms