#staff | Logs for 2024-03-04

« return
[01:00:31] <sylvester> 2024-03-04 02:00:31 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 212.07 ms
[01:02:57] <sylvester> 2024-03-04 02:02:57 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 226.68 ms
[01:05:03] <sylvester> 2024-03-04 02:05:02 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 283.71 ms
[01:08:02] <sylvester> 2024-03-04 02:08:02 04mail.soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 315.71 ms
[01:18:06] <sylvester> 2024-03-04 02:18:06 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 136.04 ms
[01:20:06] <sylvester> 2024-03-04 02:20:06 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 127.75 ms
[01:20:35] <sylvester> 2024-03-04 02:20:35 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 139.48 ms
[03:07:15] <sylvester> 2024-03-04 04:07:15 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 299.71 ms
[03:07:43] <sylvester> 2024-03-04 04:07:43 08mail.soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 227.30 ms
[03:09:23] <sylvester> 2024-03-04 04:09:23 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 247.12 ms
[03:12:19] <sylvester> 2024-03-04 04:12:19 04soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 0%, RTA = 314.14 ms
[03:12:48] <sylvester> 2024-03-04 04:12:48 04mail.soylentnews CRITICAL PING IPv600 PING CRITICAL - Packet loss = 0%, RTA = 347.92 ms
[03:14:27] <sylvester> 2024-03-04 04:14:27 04mail.soylentnews CRITICAL PING IPv400 PING CRITICAL - Packet loss = 0%, RTA = 331.04 ms
[03:16:27] -!- sylvester has quit [Remote host closed the connection]
[03:16:36] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[03:17:23] <sylvester> 2024-03-04 04:17:23 08soylentnews WARNING PING IPv600 PING WARNING - Packet loss = 0%, RTA = 237.41 ms
[03:17:52] <sylvester> 2024-03-04 04:17:52 03mail.soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 142.23 ms
[03:19:31] <sylvester> 2024-03-04 04:19:31 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 125.08 ms
[03:22:28] <sylvester> 2024-03-04 04:22:27 03soylentnews OK PING IPv600 PING OK - Packet loss = 0%, RTA = 125.73 ms
[07:37:24] -!- aristarchus [aristarchus!~aristarch@149.88.pw.voo] has joined #staff
[07:45:15] -!- aristarchus has quit [Quit: Client closed]
[10:27:58] -!- aristarchus [aristarchus!~aristarch@149.40.yr.zyk] has joined #staff
[10:29:01] <sylvester> 2024-03-04 11:29:01 04soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.513 second response time
[10:29:01] <sylvester> 2024-03-04 11:29:01 04soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.526 second response time
[11:16:46] -!- aristarchus has quit [Quit: Client closed]
[11:29:01] <sylvester> 2024-03-04 12:29:01 04soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.524 second response time
[11:29:02] <sylvester> 2024-03-04 12:29:02 04soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.530 second response time
[12:29:02] <sylvester> 2024-03-04 13:29:02 04soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.517 second response time
[12:34:02] <sylvester> 2024-03-04 13:34:02 04soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.541 second response time
[13:29:02] <sylvester> 2024-03-04 14:29:02 04soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.526 second response time
[13:39:02] <sylvester> 2024-03-04 14:39:02 04soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.527 second response time
[13:40:25] -!- drussell has quit [Ping timeout: 252 seconds]
[13:41:23] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff
[14:34:02] <sylvester> 2024-03-04 15:34:02 04soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 794 bytes in 0.520 second response time
[16:43:17] <fab23> I have acknowledged the failed service in my monitoring a while ago, so the hourly repetive notifications are silenced. It will report again when the state does change.
[16:49:37] <janrinok> thanks
[17:39:02] <sylvester> 2024-03-04 18:39:02 03soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 95376 bytes in 1.071 second response time
[17:39:04] <sylvester> 2024-03-04 18:39:04 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95333 bytes in 1.219 second response time
[17:51:37] <janrinok> fab23, you can restart Sylvester
[17:56:22] <sylvester> 2024-03-04 18:56:22 04soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[17:56:24] <sylvester> 2024-03-04 18:56:24 04soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[17:58:49] <sylvester> 2024-03-04 18:58:49 04mail.soylentnews CRITICAL SMTP Submission IPv400 CRITICAL - Socket timeout after 10 seconds
[18:01:23] <sylvester> 2024-03-04 19:01:23 03soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 95347 bytes in 1.046 second response time
[18:01:25] <sylvester> 2024-03-04 19:01:25 03soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 95344 bytes in 1.086 second response time
[18:02:43] <janrinok> No, its down again
[18:03:50] <sylvester> 2024-03-04 19:03:50 03mail.soylentnews OK SMTP Submission IPv400 SMTP OK - 1.170 sec. response time
[21:57:04] -!- drussell has quit [Ping timeout: 252 seconds]
[21:57:57] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff