#staff | Logs for 2025-08-24

« return
[00:04:00] <sylvester> 2025-08-24 02:04:00 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[00:07:08] <sylvester> 2025-08-24 02:07:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[00:08:15] <sylvester> 2025-08-24 02:08:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[00:08:28] <sylvester> 2025-08-24 02:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[01:01:44] -!- Loggie [Loggie!Loggie@Soylent/BotArmy] has joined #staff
[01:04:00] <sylvester> 2025-08-24 03:04:00 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[01:07:08] <sylvester> 2025-08-24 03:07:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[01:08:16] <sylvester> 2025-08-24 03:08:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[01:08:28] <sylvester> 2025-08-24 03:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[02:04:00] <sylvester> 2025-08-24 04:04:00 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[02:07:09] <sylvester> 2025-08-24 04:07:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[02:08:16] <sylvester> 2025-08-24 04:08:16 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[02:08:28] <sylvester> 2025-08-24 04:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[03:04:00] <sylvester> 2025-08-24 05:04:00 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[03:07:09] <sylvester> 2025-08-24 05:07:09 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[03:08:28] <sylvester> 2025-08-24 05:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[03:13:15] <sylvester> 2025-08-24 05:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[04:04:01] <sylvester> 2025-08-24 06:04:00 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[04:08:28] <sylvester> 2025-08-24 06:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[04:12:08] <sylvester> 2025-08-24 06:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[04:13:15] <sylvester> 2025-08-24 06:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[05:04:01] <sylvester> 2025-08-24 07:04:01 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[05:08:28] <sylvester> 2025-08-24 07:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[05:12:08] <sylvester> 2025-08-24 07:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[05:13:15] <sylvester> 2025-08-24 07:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[06:04:01] <sylvester> 2025-08-24 08:04:01 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[06:08:28] <sylvester> 2025-08-24 08:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[06:12:08] <sylvester> 2025-08-24 08:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[06:13:15] <sylvester> 2025-08-24 08:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[07:04:01] <sylvester> 2025-08-24 09:04:01 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[07:08:28] <sylvester> 2025-08-24 09:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[07:12:08] <sylvester> 2025-08-24 09:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[07:13:15] <sylvester> 2025-08-24 09:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:04:01] <sylvester> 2025-08-24 10:04:01 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:08:29] <sylvester> 2025-08-24 10:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[08:12:08] <sylvester> 2025-08-24 10:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[08:13:15] <sylvester> 2025-08-24 10:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[09:04:01] <sylvester> 2025-08-24 11:04:01 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[09:08:28] <sylvester> 2025-08-24 11:08:28 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[09:12:08] <sylvester> 2025-08-24 11:12:08 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[09:13:15] <sylvester> 2025-08-24 11:13:15 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:02:00] <sylvester> 2025-08-24 12:02:00 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 115623 bytes in 1.582 second response time
[10:03:06] <sylvester> 2025-08-24 12:03:06 03mail.soylentnews OK IMAPS IPv600 SIMAP OK - 0.504 second response time on 2602:fd63:12::3 port 993 [* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.]
[10:03:22] <sylvester> 2025-08-24 12:03:22 03mail.soylentnews OK SMTP IPv600 SMTP OK - 4.656 sec. response time
[10:03:52] <sylvester> 2025-08-24 12:03:52 03mail.soylentnews OK SMTPS IPv600 SSMTP OK - 0.501 second response time on 2602:fd63:12::3 port 465 [220 mx.soylentnews.org Dovecot ready.]
[17:29:21] <sylvester> 2025-08-24 19:29:20 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[17:30:26] <sylvester> 2025-08-24 19:30:26 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[17:30:42] <sylvester> 2025-08-24 19:30:42 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[17:31:12] <sylvester> 2025-08-24 19:31:12 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[18:29:30] <sylvester> 2025-08-24 20:29:30 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[18:30:36] <sylvester> 2025-08-24 20:30:36 04mail.soylentnews CRITICAL IMAPS IPv600 CRITICAL - Socket timeout after 10 seconds
[18:30:52] <sylvester> 2025-08-24 20:30:52 04mail.soylentnews CRITICAL SMTP IPv600 CRITICAL - Socket timeout after 10 seconds
[18:31:23] <sylvester> 2025-08-24 20:31:22 04mail.soylentnews CRITICAL SMTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[18:47:13] <fab23> I have disabled the alerts for the above services, will resume as soon as the services are reachable again.
[19:53:08] <chromas> Maybe it could auto-timeout alerts after a couple, then maybe roll them up into a summary post after awhile
[19:54:27] <chromas> I've seen kolie's bot do it sometimes, "[Skipped Report] Suppressed 14 reports in the last 30 minutes."
[19:57:10] <fab23> It is Nagios behind, I can only set the frequency when alerts are repeated, but I could also configure how many would be sent out, so they would just stop and then only report again when the service is up
[20:51:21] <sylvester> 2025-08-24 22:51:21 04www.soylentnews CRITICAL HTTPS Certificate soylentnews.org00 CRITICAL - Socket timeout after 10 seconds
[21:31:13] <sylvester> 2025-08-24 23:31:13 04mail.soylentnews CRITICAL SMTP STARTTLS Certificate00 CRITICAL - Socket timeout after 10 seconds