[00:03:19] PROBLEM - db112 Current Load on db112 is CRITICAL: CRITICAL - load average: 8.94, 5.87, 2.92 [00:17:19] PROBLEM - db112 Current Load on db112 is WARNING: WARNING - load average: 2.83, 6.83, 7.13 [00:19:19] RECOVERY - db112 Current Load on db112 is OK: OK - load average: 2.52, 5.47, 6.59 [00:44:37] PROBLEM - matomo121 Current Load on matomo121 is WARNING: LOAD WARNING - total load average: 3.67, 3.57, 3.11 [00:46:37] RECOVERY - matomo121 Current Load on matomo121 is OK: LOAD OK - total load average: 2.66, 3.13, 2.99 [01:16:27] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.90, 6.46, 6.01 [01:18:25] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.97, 6.23, 5.97 [01:21:53] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.67, 7.09, 6.61 [01:23:52] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.98, 6.77, 6.56 [01:27:52] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.05, 7.18, 6.80 [01:31:52] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 4.45, 6.01, 6.45 [01:33:41] PROBLEM - graylog131 Current Load on graylog131 is WARNING: LOAD WARNING - total load average: 3.69, 3.38, 2.43 [01:35:41] RECOVERY - graylog131 Current Load on graylog131 is OK: LOAD OK - total load average: 2.77, 3.22, 2.49 [01:37:35] PROBLEM - mw143 Current Load on mw143 is WARNING: LOAD WARNING - total load average: 10.91, 10.57, 7.28 [01:39:31] RECOVERY - mw143 Current Load on mw143 is OK: LOAD OK - total load average: 5.06, 8.59, 6.95 [01:40:37] PROBLEM - matomo121 Current Load on matomo121 is WARNING: LOAD WARNING - total load average: 3.75, 3.05, 2.65 [01:42:37] RECOVERY - matomo121 Current Load on matomo121 is OK: LOAD OK - total load average: 2.02, 2.68, 2.56 [01:42:38] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/5de37497a884...7a7c8a5d9c7c [01:42:40] [02miraheze/ssl] 07MirahezeSSLBot 037a7c8a5 - Bot: Update SSL cert for www.dovearchives.wiki [01:47:29] RECOVERY - www.dovearchives.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'www.dovearchives.wiki' will expire on Fri 22 Mar 2024 00:42:30 GMT +0000. [01:48:47] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/7a7c8a5d9c7c...fa559b257551 [01:48:48] [02miraheze/ssl] 07MirahezeSSLBot 03fa559b2 - Bot: Update SSL cert for wiki.puucraft.net [02:16:51] PROBLEM - puppetdb121 Puppet on puppetdb121 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[puppetdb] [02:18:48] RECOVERY - wiki.puucraft.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.puucraft.net' will expire on Fri 22 Mar 2024 00:48:39 GMT +0000. [02:27:35] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 10.05, 7.35, 6.54 [02:29:30] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.92, 7.05, 6.53 [02:31:26] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.60, 6.47, 6.37 [02:39:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.39, 6.58, 6.14 [02:41:00] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.99, 6.32, 6.09 [02:42:02] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.72, 7.59, 6.82 [02:43:57] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.89, 7.45, 6.88 [02:45:53] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.50, 9.04, 7.61 [02:51:54] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.98, 7.66, 7.42 [02:55:39] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.41, 6.92, 6.65 [03:01:28] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.74, 6.51, 6.61 [03:03:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.48, 6.47, 6.80 [03:04:46] RECOVERY - ns1 NTP time on ns1 is OK: NTP OK: Offset 0.00520798564 secs [03:08:21] RECOVERY - puppetdb121 Puppet on puppetdb121 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:27:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.76, 6.91, 6.71 [03:29:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.63, 6.51, 6.59 [06:03:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 10.14, 9.30, 7.22 [06:04:48] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 4.59, 6.98, 6.31 [06:05:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 5.98, 8.00, 7.00 [06:06:45] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 9.78, 7.68, 6.61 [06:10:38] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.65, 7.97, 7.00 [06:14:31] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.59, 6.60, 6.64 [06:17:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 3.79, 5.67, 6.50 [06:30:46] PROBLEM - ns1 NTP time on ns1 is WARNING: NTP WARNING: Offset 0.1012328267 secs [06:35:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.50, 6.89, 6.58 [06:37:51] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.16, 6.67, 6.55 [07:21:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.07, 6.77, 6.42 [07:23:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.30, 6.30, 6.28 [07:40:17] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.06, 6.00, 5.90 [07:48:35] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.30, 6.05, 5.78 [07:52:28] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.50, 5.79, 5.73 [07:55:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.38, 7.64, 6.84 [07:57:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.64, 6.98, 6.68 [07:59:51] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.03, 6.62, 6.58 [08:11:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.72, 7.11, 6.73 [08:13:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.89, 6.67, 6.62 [08:23:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.90, 6.83, 6.74 [08:25:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.49, 7.42, 6.95 [08:27:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.87, 7.19, 6.91 [08:29:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.98, 6.60, 6.72 [08:54:51] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.05, 6.16, 5.66 [08:56:48] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.17, 5.73, 5.56 [08:59:15] PROBLEM - wiki.globasa.net - reverse DNS on sslhost is WARNING: LifetimeTimeout: The resolution lifetime expired after 5.405 seconds: Server 2606:4700:4700::1111 UDP port 53 answered The DNS operation timed out.; Server 2606:4700:4700::1111 UDP port 53 answered The DNS operation timed out.; Server 2606:4700:4700::1111 UDP port 53 answered The DNS operation timed out. [09:25:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.45, 6.83, 6.46 [09:27:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.65, 7.55, 6.74 [09:28:10] RECOVERY - wiki.globasa.net - reverse DNS on sslhost is OK: SSL OK - wiki.globasa.net reverse DNS resolves to cp24.miraheze.org - CNAME OK [09:29:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.85, 6.91, 6.59 [09:33:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.99, 6.73, 6.62 [09:55:55] PROBLEM - db112 Current Load on db112 is CRITICAL: CRITICAL - load average: 9.73, 6.45, 5.03 [09:57:52] RECOVERY - db112 Current Load on db112 is OK: OK - load average: 4.24, 5.41, 4.81 [10:14:46] PROBLEM - ns1 NTP time on ns1 is CRITICAL: NTP CRITICAL: Offset 0.5034436285 secs [10:17:59] PROBLEM - puppetdb121 Puppet on puppetdb121 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[puppetdb] [10:46:40] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.37, 7.00, 6.58 [10:48:35] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.03, 6.54, 6.45 [10:59:12] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.34, 6.88, 6.61 [11:03:02] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.79, 6.59, 6.58 [11:07:59] RECOVERY - puppetdb121 Puppet on puppetdb121 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [11:43:35] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.42, 6.86, 6.37 [11:45:30] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.42, 6.64, 6.34 [11:49:21] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.24, 7.61, 6.85 [11:51:17] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.59, 7.41, 6.87 [11:55:09] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.54, 6.70, 6.69 [12:24:58] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.69, 7.68, 6.86 [12:26:53] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.28, 6.93, 6.67 [12:28:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.17, 6.34, 6.49 [12:42:18] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 8.00, 7.07, 6.73 [12:46:10] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.42, 6.68, 6.65 [12:53:52] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.55, 7.11, 6.85 [12:57:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.32, 6.66, 6.72 [13:02:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 9.14, 7.25, 6.23 [13:04:03] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 6.21, 6.74, 6.16 [13:17:12] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.81, 6.97, 6.74 [13:23:00] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.20, 7.84, 7.15 [13:24:55] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.96, 7.24, 7.00 [13:26:51] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.64, 7.86, 7.26 [13:30:41] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.07, 7.80, 7.41 [13:44:46] RECOVERY - ns1 NTP time on ns1 is OK: NTP OK: Offset 0.004482358694 secs [13:49:56] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.33, 7.18, 7.05 [13:51:51] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 5.65, 6.85, 6.96 [13:53:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 4.60, 6.20, 6.72 [14:02:37] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.13, 6.58, 6.65 [14:04:32] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.24, 6.49, 6.62 [14:17:59] PROBLEM - puppetdb121 Puppet on puppetdb121 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[puppetdb] [14:19:00] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.90, 7.07, 6.76 [14:22:46] PROBLEM - ns1 NTP time on ns1 is WARNING: NTP WARNING: Offset 0.1109584868 secs [14:22:51] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.47, 7.72, 7.08 [14:24:46] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.17, 7.76, 7.18 [14:29:04] RECOVERY - cloud11 IPMI Sensors on cloud11 is OK: IPMI Status: OK [14:33:04] PROBLEM - cloud11 IPMI Sensors on cloud11 is CRITICAL: IPMI Status: Critical [Cntlr 2 Bay 8 = Critical] [14:34:25] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.17, 7.89, 7.43 [14:36:20] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.12, 7.20, 7.23 [14:38:16] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.15, 7.51, 7.33 [14:42:06] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.23, 7.22, 7.27 [14:49:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.66, 7.81, 7.39 [14:51:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.13, 7.25, 7.24 [15:03:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 4.26, 5.81, 6.61 [15:07:59] RECOVERY - puppetdb121 Puppet on puppetdb121 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:12:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.24, 6.50, 6.11 [15:12:37] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.25, 7.36, 6.92 [15:14:33] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.34, 7.44, 7.01 [15:16:03] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.82, 6.32, 6.14 [15:20:19] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.74, 7.91, 7.31 [15:22:14] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 5.12, 6.87, 7.00 [15:26:05] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.15, 6.86, 6.92 [15:28:00] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.77, 7.06, 7.01 [15:35:35] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.83, 7.44, 6.67 [15:35:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 11.15, 8.25, 7.48 [15:39:28] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 4.04, 5.88, 6.23 [15:41:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.44, 7.92, 7.60 [15:55:05] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.34, 7.40, 6.73 [15:57:01] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.72, 6.65, 6.52 [15:57:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.09, 7.49, 7.28 [16:01:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.55, 7.31, 7.27 [16:05:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.51, 6.22, 6.79 [16:13:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.49, 6.78, 6.85 [16:17:51] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.36, 7.77, 7.21 [16:21:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.56, 7.92, 7.42 [16:29:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.26, 6.22, 6.72 [16:34:34] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.gab.pt.eu.org All nameservers failed to answer the query. [16:36:58] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.79, 6.94, 6.46 [16:38:54] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.16, 6.35, 6.30 [16:42:46] PROBLEM - ns1 NTP time on ns1 is CRITICAL: NTP CRITICAL: Offset 0.5032983422 secs [16:44:32] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.74, 7.23, 6.96 [16:44:47] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.89, 7.20, 6.64 [16:48:40] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 6.64, 6.80, 6.60 [16:56:31] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.06, 6.83, 6.72 [16:58:27] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 5.55, 6.33, 6.54 [16:59:55] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 10.29, 8.87, 7.79 [17:04:35] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is WARNING: SSL WARNING - rDNS OK but records conflict. {'NS': ['ns.ankh.fr.eu.org.', 'ns1.eu.org.', 'ns1.eriomem.net.'], 'CNAME': 'bouncingwiki.miraheze.org.'} [17:05:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.05, 7.76, 7.65 [17:07:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.17, 7.67, 7.61 [17:09:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.09, 7.04, 7.38 [17:19:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.10, 7.41, 7.31 [17:21:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.82, 7.61, 7.39 [17:33:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.29, 6.75, 6.90 [17:35:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.40, 6.91, 6.94 [17:41:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.81, 6.51, 6.78 [17:45:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.35, 7.10, 6.96 [17:46:06] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.98, 6.75, 6.20 [17:48:03] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 6.34, 6.52, 6.17 [18:04:34] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.gab.pt.eu.org All nameservers failed to answer the query. [18:07:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.84, 6.44, 6.80 [18:15:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.52, 7.07, 6.98 [18:17:59] PROBLEM - puppetdb121 Puppet on puppetdb121 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[puppetdb] [18:19:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.08, 7.46, 7.13 [18:21:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.31, 7.47, 7.18 [18:25:04] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.06, 5.98, 5.80 [18:27:00] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 6.43, 5.93, 5.79 [18:27:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.15, 6.82, 6.89 [18:29:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.45, 6.50, 6.76 [18:34:34] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is WARNING: SSL WARNING - rDNS OK but records conflict. {'NS': ['ns.ankh.fr.eu.org.', 'ns1.eu.org.', 'ns1.eriomem.net.'], 'CNAME': 'bouncingwiki.miraheze.org.'} [18:39:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.95, 6.51, 6.55 [18:41:49] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.61, 6.23, 6.45 [18:51:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.13, 7.87, 7.07 [18:53:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.39, 7.56, 7.07 [18:57:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.10, 7.39, 7.07 [18:59:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.48, 7.27, 7.06 [19:05:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.34, 7.16, 7.00 [19:07:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.12, 6.57, 6.79 [19:07:59] RECOVERY - puppetdb121 Puppet on puppetdb121 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:13:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 5.96, 6.71, 6.81 [19:15:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.13, 6.34, 6.67 [19:33:09] PROBLEM - db112 APT on db112 is CRITICAL: APT CRITICAL: 4 packages available for upgrade (3 critical updates). [19:33:49] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 10.33, 8.02, 7.14 [19:35:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.35, 7.51, 7.06 [19:51:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.26, 7.75, 7.36 [19:53:50] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.50, 7.66, 7.38 [20:01:50] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.39, 6.07, 6.75 [20:15:35] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.94, 7.07, 6.87 [20:17:31] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 6.07, 6.72, 6.76 [20:21:22] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.45, 7.30, 6.99 [20:27:08] RECOVERY - swiftobject122 Current Load on swiftobject122 is OK: OK - load average: 5.75, 6.64, 6.80 [20:31:02] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.39, 6.91, 6.87 [20:34:53] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.94, 8.00, 7.29 [20:36:48] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 5.47, 7.20, 7.09 [20:42:34] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 8.52, 8.28, 7.66 [20:44:14] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.21, 7.30, 6.70 [20:44:30] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 6.95, 7.85, 7.59 [20:46:10] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 9.03, 8.32, 7.16 [20:46:25] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 9.59, 8.61, 7.90 [20:48:07] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 6.34, 7.56, 7.02 [20:48:20] PROBLEM - swiftobject122 Current Load on swiftobject122 is WARNING: WARNING - load average: 7.00, 7.76, 7.66 [20:52:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 8.32, 7.19, 6.93 [20:54:03] RECOVERY - swiftobject101 Current Load on swiftobject101 is OK: OK - load average: 4.93, 6.22, 6.60 [20:55:27] PROBLEM - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is CRITICAL: CRITICAL - NGINX Error Rate is 87% [20:55:27] PROBLEM - cp35 Nginx Backend for mw133 on cp35 is CRITICAL: connect to address localhost and port 8110: Connection refused [20:55:30] PROBLEM - cp35 Nginx Backend for mw132 on cp35 is CRITICAL: connect to address localhost and port 8107: Connection refused [20:55:37] PROBLEM - cp35 Nginx Backend for mw134 on cp35 is CRITICAL: connect to address localhost and port 8111: Connection refused [20:55:41] PROBLEM - cp35 Nginx Backend for matomo121 on cp35 is CRITICAL: connect to address localhost and port 8203: Connection refused [20:55:47] PROBLEM - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [20:55:58] PROBLEM - cp35 Varnish Backends on cp35 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [20:56:01] PROBLEM - swiftobject122 Current Load on swiftobject122 is CRITICAL: CRITICAL - load average: 13.89, 7.98, 7.52 [20:56:04] PROBLEM - cp35 HTTPS on cp35 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp35.miraheze.org port 443 after 78 ms: Couldn't connect to server [20:56:05] PROBLEM - cp24 HTTPS on cp24 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp24.miraheze.org port 443 after 2 ms: Couldn't connect to server [20:56:05] PROBLEM - cp35 Nginx Backend for mw141 on cp35 is CRITICAL: connect to address localhost and port 8108: Connection refused [20:56:06] PROBLEM - cp35 Nginx Backend for mw142 on cp35 is CRITICAL: connect to address localhost and port 8109: Connection refused [20:56:08] PROBLEM - cp35 Nginx Backend for test131 on cp35 is CRITICAL: connect to address localhost and port 8180: Connection refused [20:56:13] PROBLEM - cp25 Varnish Backends on cp25 is WARNING: No backends detected. If this is an error, see readme.txt [20:56:13] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 6 datacenters are down: 51.195.201.140/cpweb, 51.89.139.24/cpweb, 2001:41d0:801:2000::5d68/cpweb, 2001:41d0:801:2000::3a18/cpweb, 51.222.12.133/cpweb, 2607:5300:205:200::1c93/cpweb [20:56:20] PROBLEM - cp25 Current Load on cp25 is CRITICAL: LOAD CRITICAL - total load average: 21.41, 8.48, 3.51 [20:56:23] PROBLEM - cp35 Nginx Backend for mon141 on cp35 is CRITICAL: connect to address localhost and port 8201: Connection refused [20:56:28] PROBLEM - cp24 Nginx Backend for mail121 on cp24 is CRITICAL: connect to address localhost and port 8200: Connection refused [20:56:34] PROBLEM - cp35 Nginx Backend for phab121 on cp35 is CRITICAL: connect to address localhost and port 8202: Connection refused [20:56:38] PROBLEM - cp24 Nginx Backend for mon141 on cp24 is CRITICAL: connect to address localhost and port 8201: Connection refused [20:56:38] PROBLEM - cp35 Nginx Backend for mw143 on cp35 is CRITICAL: connect to address localhost and port 8112: Connection refused [20:56:39] PROBLEM - cp24 Nginx Backend for mw142 on cp24 is CRITICAL: connect to address localhost and port 8109: Connection refused [20:56:41] PROBLEM - cp35 Nginx Backend for mwtask141 on cp35 is CRITICAL: connect to address localhost and port 8150: Connection refused [20:56:41] PROBLEM - cp24 Nginx Backend for matomo121 on cp24 is CRITICAL: connect to address localhost and port 8203: Connection refused [20:56:42] PROBLEM - cp35 Nginx Backend for reports121 on cp35 is CRITICAL: connect to address localhost and port 8205: Connection refused [20:56:43] PROBLEM - cp24 Nginx Backend for mw143 on cp24 is CRITICAL: connect to address localhost and port 8112: Connection refused [20:56:48] PROBLEM - cp24 Nginx Backend for mw134 on cp24 is CRITICAL: connect to address localhost and port 8111: Connection refused [20:56:55] PROBLEM - cp34 Current Load on cp34 is CRITICAL: LOAD CRITICAL - total load average: 2.97, 8.43, 4.55 [20:56:59] PROBLEM - cp35 Nginx Backend for puppet141 on cp35 is CRITICAL: connect to address localhost and port 8204: Connection refused [20:57:02] PROBLEM - cp24 Nginx Backend for test131 on cp24 is CRITICAL: connect to address localhost and port 8180: Connection refused [20:57:07] PROBLEM - cp35 HTTP 4xx/5xx ERROR Rate on cp35 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [20:57:07] PROBLEM - cp24 Nginx Backend for reports121 on cp24 is CRITICAL: connect to address localhost and port 8205: Connection refused [20:57:08] PROBLEM - cp24 Nginx Backend for phab121 on cp24 is CRITICAL: connect to address localhost and port 8202: Connection refused [20:57:08] PROBLEM - cp35 Nginx Backend for mail121 on cp35 is CRITICAL: connect to address localhost and port 8200: Connection refused [20:57:18] PROBLEM - cp35 Nginx Backend for mw131 on cp35 is CRITICAL: connect to address localhost and port 8106: Connection refused [20:57:18] PROBLEM - cp24 Nginx Backend for puppet141 on cp24 is CRITICAL: connect to address localhost and port 8204: Connection refused [20:57:23] PROBLEM - cp24 Nginx Backend for mw132 on cp24 is CRITICAL: connect to address localhost and port 8107: Connection refused [20:57:25] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 4 datacenters are down: 51.195.201.140/cpweb, 2001:41d0:801:2000::5d68/cpweb, 51.222.12.133/cpweb, 2607:5300:205:200::1c93/cpweb [20:57:26] RECOVERY - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is OK: OK - NGINX Error Rate is 3% [20:57:27] PROBLEM - cp24 Varnish Backends on cp24 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [20:57:28] PROBLEM - cp24 Nginx Backend for mwtask141 on cp24 is CRITICAL: connect to address localhost and port 8150: Connection refused [20:57:41] PROBLEM - cp24 Nginx Backend for mw133 on cp24 is CRITICAL: connect to address localhost and port 8110: Connection refused [20:57:41] PROBLEM - cp24 Nginx Backend for mw141 on cp24 is CRITICAL: connect to address localhost and port 8108: Connection refused [20:57:52] PROBLEM - cp24 Nginx Backend for mw131 on cp24 is CRITICAL: connect to address localhost and port 8106: Connection refused [20:58:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 19.29, 12.12, 8.76 [20:58:12] RECOVERY - cp25 Varnish Backends on cp25 is OK: All 15 backends are healthy [20:58:19] RECOVERY - cp25 Current Load on cp25 is OK: LOAD OK - total load average: 4.30, 6.16, 3.25 [20:58:25] PROBLEM - swiftobject121 Current Load on swiftobject121 is CRITICAL: CRITICAL - load average: 11.24, 7.89, 6.16 [20:58:55] RECOVERY - cp34 Current Load on cp34 is OK: LOAD OK - total load average: 0.79, 5.80, 4.06 [20:59:14] PROBLEM - swiftobject113 Current Load on swiftobject113 is CRITICAL: CRITICAL - load average: 8.37, 6.30, 5.38 [21:00:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 10.15, 7.90, 5.94 [21:00:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is WARNING: WARNING - load average: 7.85, 6.60, 5.01 [21:01:19] PROBLEM - wiki.bikinibottomdiscord.org - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.bikinibottomdiscord.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:02] PROBLEM - hastursnotebook.org - LetsEncrypt on sslhost is CRITICAL: connect to address hastursnotebook.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:02] PROBLEM - wiki.site97.fr - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.site97.fr and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:07] PROBLEM - archive.a2b2.org - LetsEncrypt on sslhost is CRITICAL: connect to address archive.a2b2.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:13] PROBLEM - wiki.potabi.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.potabi.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:13] PROBLEM - gil.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address gil.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:14] PROBLEM - publictestwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address publictestwiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:15] PROBLEM - wiki.consid.vn - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.consid.vn and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:15] PROBLEM - revi.wiki - PositiveSSLDV on sslhost is CRITICAL: connect to address revi.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:15] PROBLEM - apocrypha.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address apocrypha.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:17] PROBLEM - wikappedia.cc - LetsEncrypt on sslhost is CRITICAL: connect to address wikappedia.cc and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:18] PROBLEM - cp25 Varnish Backends on cp25 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [21:02:20] PROBLEM - wiki.thesimswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.thesimswiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:26] PROBLEM - wiki.triplescripts.org - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.triplescripts.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:26] PROBLEM - wiki.wilderyogi.eu - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.wilderyogi.eu and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:02:27] PROBLEM - cp25 Nginx Backend for mw131 on cp25 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:02:40] PROBLEM - cp25 Nginx Backend for mw142 on cp25 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:02:41] PROBLEM - cp25 Nginx Backend for mw141 on cp25 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:02:46] PROBLEM - cp25 Nginx Backend for mw143 on cp25 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:03:03] PROBLEM - cp25 Nginx Backend for mon141 on cp25 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:03:07] PROBLEM - cp25 Nginx Backend for mw132 on cp25 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:03:08] PROBLEM - cp25 Nginx Backend for mwtask141 on cp25 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:03:09] PROBLEM - cp25 Nginx Backend for reports121 on cp25 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:03:14] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 7.84, 7.50, 6.12 [21:03:19] PROBLEM - cp25 Nginx Backend for mw134 on cp25 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:03:25] PROBLEM - cp25 Nginx Backend for mail121 on cp25 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:03:26] PROBLEM - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is CRITICAL: CRITICAL - NGINX Error Rate is 87% [21:03:31] PROBLEM - cp25 Nginx Backend for puppet141 on cp25 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:03:37] PROBLEM - cp25 HTTPS on cp25 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp25.miraheze.org port 443 after 2 ms: Couldn't connect to server [21:03:44] PROBLEM - cp25 Nginx Backend for matomo121 on cp25 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:03:47] PROBLEM - cp25 Nginx Backend for phab121 on cp25 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:03:57] PROBLEM - cp25 Nginx Backend for test131 on cp25 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:04:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is WARNING: WARNING - load average: 6.32, 7.50, 6.27 [21:04:18] PROBLEM - cp25 Nginx Backend for mw133 on cp25 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:04:41] RECOVERY - swiftobject112 Current Load on swiftobject112 is OK: OK - load average: 4.88, 6.08, 5.21 [21:07:14] PROBLEM - swiftobject113 Current Load on swiftobject113 is CRITICAL: CRITICAL - load average: 8.17, 7.52, 6.41 [21:08:28] RECOVERY - cp24 Nginx Backend for mail121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:08:38] RECOVERY - cp24 Nginx Backend for mon141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:08:39] RECOVERY - cp24 Nginx Backend for mw142 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:08:42] RECOVERY - cp24 Nginx Backend for matomo121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:08:43] RECOVERY - cp24 Nginx Backend for mw143 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:08:48] RECOVERY - cp24 Nginx Backend for mw134 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:09:02] RECOVERY - cp24 Nginx Backend for test131 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:09:07] RECOVERY - cp24 Nginx Backend for reports121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:09:08] RECOVERY - cp24 Nginx Backend for phab121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:09:18] RECOVERY - cp24 Nginx Backend for puppet141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:09:24] RECOVERY - cp24 Nginx Backend for mw132 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:09:27] RECOVERY - cp24 Varnish Backends on cp24 is OK: All 15 backends are healthy [21:09:28] RECOVERY - cp24 Nginx Backend for mwtask141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:09:37] RECOVERY - cp35 Nginx Backend for mw134 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:09:41] RECOVERY - cp24 Nginx Backend for mw133 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:09:41] RECOVERY - cp24 Nginx Backend for mw141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8108 [21:09:41] RECOVERY - cp35 Nginx Backend for matomo121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:09:47] RECOVERY - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is OK: OK - NGINX Error Rate is 0% [21:09:52] RECOVERY - cp24 Nginx Backend for mw131 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:10:02] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 8.52, 7.54, 6.64 [21:10:05] RECOVERY - cp35 Nginx Backend for mw141 on cp35 is OK: TCP OK - 0.006 second response time on localhost port 8108 [21:10:06] RECOVERY - cp35 Nginx Backend for mw142 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:10:09] RECOVERY - cp35 Nginx Backend for test131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:10:23] RECOVERY - cp35 Nginx Backend for mon141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:10:34] RECOVERY - cp35 Nginx Backend for phab121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:10:38] RECOVERY - cp35 Nginx Backend for mw143 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:10:41] RECOVERY - cp35 Nginx Backend for mwtask141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:10:42] RECOVERY - cp35 Nginx Backend for reports121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:10:59] RECOVERY - cp35 Nginx Backend for puppet141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:11:08] RECOVERY - cp35 Nginx Backend for mail121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:11:13] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 4.96, 7.31, 6.65 [21:11:18] RECOVERY - cp35 Nginx Backend for mw131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:11:27] RECOVERY - cp35 Nginx Backend for mw133 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:11:30] RECOVERY - cp35 Nginx Backend for mw132 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:11:56] PROBLEM - celeste.ink - LetsEncrypt on sslhost is CRITICAL: connect to address celeste.ink and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:11:56] PROBLEM - wiki.coolstation.space - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.coolstation.space and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:11:57] PROBLEM - rarewarewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rarewarewiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:00] PROBLEM - familiacorsi.com - LetsEncrypt on sslhost is CRITICAL: connect to address familiacorsi.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:01] RECOVERY - swiftobject111 Current Load on swiftobject111 is OK: OK - load average: 4.33, 6.21, 6.26 [21:12:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is WARNING: WARNING - load average: 4.26, 7.18, 7.32 [21:12:06] PROBLEM - iceria.org - LetsEncrypt on sslhost is CRITICAL: connect to address iceria.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:07] PROBLEM - wiki.thehall.xyz - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.thehall.xyz and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:08] PROBLEM - elsterclopedie.marithaime.nl - LetsEncrypt on sslhost is CRITICAL: connect to address elsterclopedie.marithaime.nl and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:17] PROBLEM - wiki.worldbuilding.network - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.worldbuilding.network and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:19] PROBLEM - wiki.ivy.cm - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.ivy.cm and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:22] PROBLEM - www.trollpasta.com - LetsEncrypt on sslhost is CRITICAL: connect to address www.trollpasta.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:23] PROBLEM - wiki.dwarvesrp.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.dwarvesrp.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:26] PROBLEM - wiki.lewisgill.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.lewisgill.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:27] PROBLEM - ncuwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address ncuwiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:28] PROBLEM - cp24 Nginx Backend for mail121 on cp24 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:12:33] PROBLEM - wiki.themarkside.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.themarkside.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:33] PROBLEM - closinglogosgroup.miraheze.org - Sectigo on sslhost is CRITICAL: connect to address closinglogosgroup.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:34] PROBLEM - cp34 Nginx Backend for phab121 on cp34 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:12:35] PROBLEM - wiki.cryptoroyale.one - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.cryptoroyale.one and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:36] PROBLEM - pwsc.polandballwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address pwsc.polandballwiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:38] PROBLEM - cp24 Nginx Backend for mon141 on cp24 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:12:39] PROBLEM - cp24 Nginx Backend for mw142 on cp24 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:12:39] PROBLEM - cp34 Nginx Backend for mw132 on cp34 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:12:41] PROBLEM - cp34 HTTP 4xx/5xx ERROR Rate on cp34 is CRITICAL: CRITICAL - NGINX Error Rate is 92% [21:12:42] PROBLEM - cp24 Nginx Backend for matomo121 on cp24 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:12:42] PROBLEM - petrawiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address petrawiki.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:42] PROBLEM - cp34 Nginx Backend for mw134 on cp34 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:12:42] PROBLEM - cp24 Nginx Backend for mw143 on cp24 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:12:46] PROBLEM - cp34 Nginx Backend for matomo121 on cp34 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:12:47] PROBLEM - history.estill.org - LetsEncrypt on sslhost is CRITICAL: connect to address history.estill.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:48] PROBLEM - cp24 Nginx Backend for mw134 on cp24 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:12:50] PROBLEM - wc.miraheze.org on sslhost is CRITICAL: connect to address miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:51] PROBLEM - cp34 Nginx Backend for mw141 on cp34 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:12:54] PROBLEM - wiki.infomedia.co.uk - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.infomedia.co.uk and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:56] PROBLEM - wiki.yuanpi.eu.org - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.yuanpi.eu.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:12:57] PROBLEM - metroidpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address metroidpedia.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:02] PROBLEM - cp24 Nginx Backend for test131 on cp24 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:13:05] PROBLEM - wiki.mastodon.kr - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.mastodon.kr and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:06] PROBLEM - rare.miraheze.org - Sectigo on sslhost is CRITICAL: connect to address rare.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:07] PROBLEM - cp24 Nginx Backend for reports121 on cp24 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:13:08] PROBLEM - cp24 Nginx Backend for phab121 on cp24 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:13:09] PROBLEM - puritwiki.p-e.kr - LetsEncrypt on sslhost is CRITICAL: connect to address puritwiki.p-e.kr and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:10] PROBLEM - cp34 Nginx Backend for puppet141 on cp34 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:13:12] PROBLEM - m.miraheze.org - LetsEncrypt on sslhost is CRITICAL: connect to address m.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:13] RECOVERY - swiftobject113 Current Load on swiftobject113 is OK: OK - load average: 3.39, 5.91, 6.21 [21:13:14] PROBLEM - sarovia.graalmilitary.com - LetsEncrypt on sslhost is CRITICAL: connect to address sarovia.graalmilitary.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:14] PROBLEM - wizardia.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address wizardia.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:15] PROBLEM - tl.awiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address tl.awiki.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:16] PROBLEM - infectowiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address infectowiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:16] PROBLEM - kirisame-kissaten.cf - LetsEncrypt on sslhost is CRITICAL: connect to address kirisame-kissaten.cf and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:17] PROBLEM - cp34 Nginx Backend for mon141 on cp34 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:13:18] PROBLEM - cp24 Nginx Backend for puppet141 on cp24 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:13:23] PROBLEM - dkpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address dkpedia.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:23] PROBLEM - cp24 Nginx Backend for mw132 on cp24 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:13:25] PROBLEM - cp34 Nginx Backend for reports121 on cp34 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:13:27] PROBLEM - cp24 Varnish Backends on cp24 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [21:13:28] PROBLEM - cp24 Nginx Backend for mwtask141 on cp24 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:13:28] PROBLEM - cp34 Nginx Backend for mail121 on cp34 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:13:30] PROBLEM - cp34 HTTPS on cp34 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp34.miraheze.org port 443 after 84 ms: Couldn't connect to server [21:13:31] PROBLEM - wiki.closai.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.closai.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:35] PROBLEM - cp34 Nginx Backend for mw143 on cp34 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:13:38] PROBLEM - cp35 Nginx Backend for mw134 on cp35 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:13:41] PROBLEM - cp24 Nginx Backend for mw133 on cp24 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:13:41] PROBLEM - cp24 Nginx Backend for mw141 on cp24 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:13:41] PROBLEM - cp35 Nginx Backend for matomo121 on cp35 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:13:47] PROBLEM - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is CRITICAL: CRITICAL - NGINX Error Rate is 98% [21:13:49] PROBLEM - de.berlinwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address de.berlinwiki.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:51] PROBLEM - cp34 Nginx Backend for test131 on cp34 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:13:52] PROBLEM - cp24 Nginx Backend for mw131 on cp24 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:13:53] PROBLEM - wiki.grab-tools.live - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.grab-tools.live and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:13:58] PROBLEM - cp34 Nginx Backend for mw131 on cp34 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:13:59] PROBLEM - n64brew.dev - LetsEncrypt on sslhost is CRITICAL: connect to address n64brew.dev and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:00] PROBLEM - cp34 Varnish Backends on cp34 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [21:14:01] PROBLEM - cp34 Nginx Backend for mw133 on cp34 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:14:05] PROBLEM - cp35 Nginx Backend for mw141 on cp35 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:14:06] PROBLEM - cp35 Nginx Backend for mw142 on cp35 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:14:06] PROBLEM - partopedia.ru - LetsEncrypt on sslhost is CRITICAL: connect to address partopedia.ru and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:08] PROBLEM - cp35 Nginx Backend for test131 on cp35 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:14:10] PROBLEM - portalsofphereon.com - LetsEncrypt on sslhost is CRITICAL: connect to address portalsofphereon.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:13] PROBLEM - wiki.wikimedia.cat - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.wikimedia.cat and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:14] PROBLEM - cp34 Nginx Backend for mwtask141 on cp34 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:14:15] PROBLEM - acgn.sfdev.eu.org - LetsEncrypt on sslhost is CRITICAL: connect to address acgn.sfdev.eu.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:15] PROBLEM - webkinzguide.com - LetsEncrypt on sslhost is CRITICAL: connect to address webkinzguide.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:17] PROBLEM - files.pornwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address files.pornwiki.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:17] PROBLEM - cp34 Nginx Backend for mw142 on cp34 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:14:20] PROBLEM - wiki.strangereons.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.strangereons.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:20] PROBLEM - wiki.kingmingshrimp.com - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.kingmingshrimp.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:21] PROBLEM - www.themagical.world - LetsEncrypt on sslhost is CRITICAL: connect to address www.themagical.world and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:21] PROBLEM - hoseki.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hoseki.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:21] PROBLEM - developer-and-testers.wiki.feign-wiki.tk - LetsEncrypt on sslhost is CRITICAL: connect to address developer-and-testers.wiki.feign-wiki.tk and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:22] PROBLEM - wiki.cutefame.net - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.cutefame.net and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:23] PROBLEM - worldtriggerwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address worldtriggerwiki.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:23] PROBLEM - 321nailswiki.miraheze.org - Sectigo on sslhost is CRITICAL: connect to address 321nailswiki.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:23] PROBLEM - cp35 Nginx Backend for mon141 on cp35 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:14:24] PROBLEM - opendatascot.org - LetsEncrypt on sslhost is CRITICAL: connect to address opendatascot.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:26] PROBLEM - wiki.jsal.org - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.jsal.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:26] PROBLEM - yoshipedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address yoshipedia.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:26] PROBLEM - mhdh.pj568.eu.org - LetsEncrypt on sslhost is CRITICAL: connect to address mhdh.pj568.eu.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:26] PROBLEM - wmworld.sktz.live - LetsEncrypt on sslhost is CRITICAL: connect to address wmworld.sktz.live and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:27] PROBLEM - stablestate.org - LetsEncrypt on sslhost is CRITICAL: connect to address stablestate.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:30] PROBLEM - wiki.moores.tech - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.moores.tech and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:30] PROBLEM - wiki.drycleaninglobby.net - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.drycleaninglobby.net and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:34] PROBLEM - cp35 Nginx Backend for phab121 on cp35 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:14:35] PROBLEM - pwiki.arkcls.com - LetsEncrypt on sslhost is CRITICAL: connect to address pwiki.arkcls.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:38] PROBLEM - cp35 Nginx Backend for mw143 on cp35 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:14:41] PROBLEM - cp35 Nginx Backend for mwtask141 on cp35 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:14:41] PROBLEM - cp35 Nginx Backend for reports121 on cp35 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:14:43] PROBLEM - encyclopediarobotica.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediarobotica.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:43] PROBLEM - istpcomputing.com - LetsEncrypt on sslhost is CRITICAL: connect to address istpcomputing.com and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:47] PROBLEM - smashbros.miraheze.org - Sectigo on sslhost is CRITICAL: connect to address smashbros.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:47] PROBLEM - www.deadprem.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address www.deadprem.wiki and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:58] PROBLEM - heavyironmodding.org - LetsEncrypt on sslhost is CRITICAL: connect to address heavyironmodding.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:14:59] PROBLEM - cp35 Nginx Backend for puppet141 on cp35 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:14:59] PROBLEM - fid.koymi.net - LetsEncrypt on sslhost is CRITICAL: connect to address fid.koymi.net and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:15:00] PROBLEM - data.wikiyri.org - LetsEncrypt on sslhost is CRITICAL: connect to address data.wikiyri.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:15:04] PROBLEM - www.tintinpedia.fr - LetsEncrypt on sslhost is CRITICAL: connect to address www.tintinpedia.fr and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:15:05] PROBLEM - crustypedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address crustypedia.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:15:06] PROBLEM - ajhalili2006.miraheze.org - Sectigo on sslhost is CRITICAL: connect to address ajhalili2006.miraheze.org and port 443: Network is unreachableHTTP CRITICAL - Unable to open TCP socket [21:15:07] RECOVERY - cp25 Nginx Backend for mw132 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:15:08] RECOVERY - cp25 Nginx Backend for mwtask141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:15:08] PROBLEM - cp35 Nginx Backend for mail121 on cp35 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:15:09] RECOVERY - cp25 Nginx Backend for reports121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:15:18] PROBLEM - cp35 Nginx Backend for mw131 on cp35 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:15:18] RECOVERY - cp24 Nginx Backend for puppet141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:15:19] RECOVERY - cp25 Nginx Backend for mw134 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:15:24] RECOVERY - cp24 Nginx Backend for mw132 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:15:25] RECOVERY - cp25 Nginx Backend for mail121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:15:25] RECOVERY - cp34 Nginx Backend for reports121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:15:27] PROBLEM - cp35 Nginx Backend for mw133 on cp35 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:15:28] RECOVERY - cp24 Nginx Backend for mwtask141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:15:28] RECOVERY - cp34 Nginx Backend for mail121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:15:29] PROBLEM - cp35 Nginx Backend for mw132 on cp35 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:15:31] RECOVERY - cp25 Nginx Backend for puppet141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:15:35] RECOVERY - cp34 Nginx Backend for mw143 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:15:38] RECOVERY - cp35 Nginx Backend for mw134 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:15:41] RECOVERY - cp24 Nginx Backend for mw133 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:15:41] RECOVERY - cp24 Nginx Backend for mw141 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8108 [21:15:41] RECOVERY - cp35 Nginx Backend for matomo121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:15:44] RECOVERY - cp25 Nginx Backend for matomo121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:15:47] RECOVERY - cp25 Nginx Backend for phab121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:15:47] PROBLEM - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is WARNING: WARNING - NGINX Error Rate is 47% [21:15:49] RECOVERY - cp34 Nginx Backend for test131 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:15:52] RECOVERY - cp24 Nginx Backend for mw131 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:15:54] RECOVERY - cp34 Nginx Backend for mw131 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:15:56] RECOVERY - cp34 Nginx Backend for mw133 on cp34 is OK: TCP OK - 0.004 second response time on localhost port 8110 [21:15:56] PROBLEM - wiki.miraheze.org - Sectigo on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:15:57] RECOVERY - cp25 Nginx Backend for test131 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:15:59] PROBLEM - electowiki.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:02] RECOVERY - swiftobject121 Current Load on swiftobject121 is OK: OK - load average: 3.44, 5.23, 6.48 [21:16:04] PROBLEM - wiki.harlonserver.net - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:05] RECOVERY - cp35 Nginx Backend for mw141 on cp35 is OK: TCP OK - 0.001 second response time on localhost port 8108 [21:16:06] RECOVERY - cp35 Nginx Backend for mw142 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:16:08] PROBLEM - wiki.anempireofdreams.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:08] PROBLEM - wiki.evscope.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:09] RECOVERY - cp35 Nginx Backend for test131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:16:11] RECOVERY - cp34 Nginx Backend for mwtask141 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:16:12] RECOVERY - cp25 Varnish Backends on cp25 is OK: All 15 backends are healthy [21:16:14] PROBLEM - lcn.zfc.id.lv - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:14] PROBLEM - wiki.pixandbit.gay - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:15] RECOVERY - cp34 Nginx Backend for mw142 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:16:15] PROBLEM - echoes-wiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:16:18] RECOVERY - cp25 Nginx Backend for mw133 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:16:23] RECOVERY - cp35 Nginx Backend for mon141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:16:27] RECOVERY - cp25 Nginx Backend for mw131 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:16:29] RECOVERY - cp24 Nginx Backend for mail121 on cp24 is OK: TCP OK - 0.002 second response time on localhost port 8200 [21:16:29] RECOVERY - cp34 Nginx Backend for phab121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:16:34] RECOVERY - cp35 Nginx Backend for phab121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:16:38] RECOVERY - cp24 Nginx Backend for mon141 on cp24 is OK: TCP OK - 0.001 second response time on localhost port 8201 [21:16:38] RECOVERY - cp34 Nginx Backend for matomo121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:16:38] RECOVERY - cp35 Nginx Backend for mw143 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:16:39] RECOVERY - cp34 Nginx Backend for mw132 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:16:39] RECOVERY - cp24 Nginx Backend for mw142 on cp24 is OK: TCP OK - 0.002 second response time on localhost port 8109 [21:16:40] RECOVERY - cp25 Nginx Backend for mw142 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:16:41] RECOVERY - cp35 Nginx Backend for mwtask141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:16:42] RECOVERY - cp24 Nginx Backend for matomo121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:16:42] RECOVERY - cp25 Nginx Backend for mw141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8108 [21:16:42] RECOVERY - cp35 Nginx Backend for reports121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:16:43] RECOVERY - cp34 Nginx Backend for mw134 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:16:43] RECOVERY - cp24 Nginx Backend for mw143 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:16:46] RECOVERY - cp25 Nginx Backend for mw143 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:16:48] RECOVERY - cp34 Nginx Backend for mw141 on cp34 is OK: TCP OK - 0.001 second response time on localhost port 8108 [21:16:48] RECOVERY - cp24 Nginx Backend for mw134 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:16:59] RECOVERY - cp35 Nginx Backend for puppet141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:17:02] RECOVERY - cp24 Nginx Backend for test131 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:17:03] RECOVERY - cp25 Nginx Backend for mon141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:17:07] RECOVERY - m.miraheze.org - LetsEncrypt on sslhost is OK: OK - Certificate 'm.miraheze.org' will expire on Tue 23 Jan 2024 13:13:37 GMT +0000. [21:17:07] RECOVERY - cp24 Nginx Backend for reports121 on cp24 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:17:08] RECOVERY - cp24 Nginx Backend for phab121 on cp24 is OK: TCP OK - 0.001 second response time on localhost port 8202 [21:17:08] RECOVERY - cp35 Nginx Backend for mail121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:17:18] RECOVERY - cp35 Nginx Backend for mw131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:17:27] RECOVERY - cp35 Nginx Backend for mw133 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:17:29] RECOVERY - cp35 Nginx Backend for mw132 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:17:31] PROBLEM - correypedia.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:17:41] PROBLEM - wiki.songngu.xyz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:17:47] RECOVERY - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is OK: OK - NGINX Error Rate is 26% [21:17:58] RECOVERY - cp35 Varnish Backends on cp35 is OK: All 15 backends are healthy [21:18:04] RECOVERY - cp35 HTTPS on cp35 is OK: HTTP OK: HTTP/2 301 - 3556 bytes in 0.794 second response time [21:18:18] RECOVERY - cp24 HTTPS on cp24 is OK: HTTP OK: HTTP/2 301 - 3556 bytes in 0.046 second response time [21:18:56] RECOVERY - wc.miraheze.org on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:19:07] RECOVERY - cp35 HTTP 4xx/5xx ERROR Rate on cp35 is OK: OK - NGINX Error Rate is 3% [21:19:25] PROBLEM - cp34 Nginx Backend for reports121 on cp34 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:19:26] RECOVERY - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is OK: OK - NGINX Error Rate is 3% [21:19:27] RECOVERY - cp24 Varnish Backends on cp24 is OK: All 15 backends are healthy [21:19:28] PROBLEM - cp34 Nginx Backend for mail121 on cp34 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:19:35] PROBLEM - cp34 Nginx Backend for mw143 on cp34 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:19:48] PROBLEM - cp34 Nginx Backend for test131 on cp34 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:19:48] PROBLEM - cp34 Nginx Backend for mw133 on cp34 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:19:54] PROBLEM - cp34 Nginx Backend for mw131 on cp34 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:20:05] PROBLEM - cp34 Nginx Backend for mwtask141 on cp34 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:20:08] PROBLEM - cp34 Nginx Backend for mw142 on cp34 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:20:21] PROBLEM - cp34 Nginx Backend for phab121 on cp34 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:20:32] PROBLEM - cp34 Nginx Backend for matomo121 on cp34 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:20:39] PROBLEM - cp34 Nginx Backend for mw132 on cp34 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:20:42] PROBLEM - cp34 Nginx Backend for mw134 on cp34 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:20:43] PROBLEM - cp34 Nginx Backend for mw141 on cp34 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:21:47] PROBLEM - cp25 Nginx Backend for phab121 on cp25 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:21:48] PROBLEM - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is CRITICAL: CRITICAL - NGINX Error Rate is 78% [21:21:57] PROBLEM - cp25 Nginx Backend for test131 on cp25 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:21:58] PROBLEM - cp35 Varnish Backends on cp35 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [21:22:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is WARNING: WARNING - load average: 4.53, 7.51, 7.31 [21:22:04] PROBLEM - cp35 HTTPS on cp35 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp35.miraheze.org port 443 after 76 ms: Couldn't connect to server [21:22:05] PROBLEM - cp35 Nginx Backend for mw141 on cp35 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:22:06] PROBLEM - cp35 Nginx Backend for mw142 on cp35 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:22:09] PROBLEM - cp35 Nginx Backend for test131 on cp35 is CRITICAL: connect to address localhost and port 8180: Connection refused [21:22:18] PROBLEM - cp25 Nginx Backend for mw133 on cp25 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:22:23] PROBLEM - cp35 Nginx Backend for mon141 on cp35 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:22:27] PROBLEM - cp25 Nginx Backend for mw131 on cp25 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:22:34] PROBLEM - cp35 Nginx Backend for phab121 on cp35 is CRITICAL: connect to address localhost and port 8202: Connection refused [21:22:38] PROBLEM - cp35 Nginx Backend for mw143 on cp35 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:22:40] PROBLEM - cp25 Nginx Backend for mw142 on cp25 is CRITICAL: connect to address localhost and port 8109: Connection refused [21:22:41] PROBLEM - cp24 Current Load on cp24 is CRITICAL: LOAD CRITICAL - total load average: 8.67, 5.82, 3.00 [21:22:41] PROBLEM - cp35 Nginx Backend for mwtask141 on cp35 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:22:42] PROBLEM - cp25 Nginx Backend for mw141 on cp25 is CRITICAL: connect to address localhost and port 8108: Connection refused [21:22:42] PROBLEM - cp35 Nginx Backend for reports121 on cp35 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:22:46] PROBLEM - cp25 Nginx Backend for mw143 on cp25 is CRITICAL: connect to address localhost and port 8112: Connection refused [21:22:59] PROBLEM - cp35 Nginx Backend for puppet141 on cp35 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:23:02] PROBLEM - cp25 Nginx Backend for mon141 on cp25 is CRITICAL: connect to address localhost and port 8201: Connection refused [21:23:07] PROBLEM - cp25 Nginx Backend for mw132 on cp25 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:23:07] PROBLEM - cp35 HTTP 4xx/5xx ERROR Rate on cp35 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [21:23:08] PROBLEM - cp25 Nginx Backend for mwtask141 on cp25 is CRITICAL: connect to address localhost and port 8150: Connection refused [21:23:08] PROBLEM - cp35 Nginx Backend for mail121 on cp35 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:23:09] PROBLEM - cp25 Varnish Backends on cp25 is CRITICAL: 8 backends are down. mw131 mw132 mw141 mw142 mw133 mw134 mw143 mediawiki [21:23:09] PROBLEM - cp25 Nginx Backend for reports121 on cp25 is CRITICAL: connect to address localhost and port 8205: Connection refused [21:23:18] PROBLEM - cp35 Nginx Backend for mw131 on cp35 is CRITICAL: connect to address localhost and port 8106: Connection refused [21:23:19] PROBLEM - cp25 Nginx Backend for mw134 on cp25 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:23:25] PROBLEM - cp25 Nginx Backend for mail121 on cp25 is CRITICAL: connect to address localhost and port 8200: Connection refused [21:23:26] PROBLEM - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is CRITICAL: CRITICAL - NGINX Error Rate is 74% [21:23:27] PROBLEM - cp35 Nginx Backend for mw133 on cp35 is CRITICAL: connect to address localhost and port 8110: Connection refused [21:23:30] PROBLEM - cp35 Nginx Backend for mw132 on cp35 is CRITICAL: connect to address localhost and port 8107: Connection refused [21:23:31] PROBLEM - cp25 Nginx Backend for puppet141 on cp25 is CRITICAL: connect to address localhost and port 8204: Connection refused [21:23:38] PROBLEM - cp35 Nginx Backend for mw134 on cp35 is CRITICAL: connect to address localhost and port 8111: Connection refused [21:23:41] PROBLEM - cp35 Nginx Backend for matomo121 on cp35 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:23:44] PROBLEM - cp25 Nginx Backend for matomo121 on cp25 is CRITICAL: connect to address localhost and port 8203: Connection refused [21:24:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is CRITICAL: CRITICAL - load average: 9.82, 8.52, 7.69 [21:24:41] RECOVERY - cp24 Current Load on cp24 is OK: LOAD OK - total load average: 3.26, 4.83, 2.99 [21:25:11] RECOVERY - cp34 Nginx Backend for puppet141 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:25:17] RECOVERY - cp34 Nginx Backend for mon141 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:25:25] RECOVERY - cp34 Nginx Backend for reports121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:25:28] RECOVERY - cp34 Nginx Backend for mail121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:25:35] RECOVERY - cp34 Nginx Backend for mw143 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:25:44] RECOVERY - cp34 Nginx Backend for mw133 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:25:47] RECOVERY - cp24 HTTP 4xx/5xx ERROR Rate on cp24 is OK: OK - NGINX Error Rate is 2% [21:25:48] RECOVERY - cp34 Nginx Backend for test131 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:25:55] RECOVERY - cp34 Nginx Backend for mw131 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:25:55] RECOVERY - cp34 Nginx Backend for mwtask141 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:26:00] RECOVERY - cp34 Varnish Backends on cp34 is OK: All 15 backends are healthy [21:26:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 8.34, 6.74, 6.00 [21:26:02] RECOVERY - cp34 Nginx Backend for mw142 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:26:14] RECOVERY - cp34 Nginx Backend for phab121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:26:20] RECOVERY - cp34 Nginx Backend for matomo121 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:26:39] RECOVERY - cp34 Nginx Backend for mw132 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:26:39] RECOVERY - cp34 Nginx Backend for mw141 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8108 [21:26:41] RECOVERY - cp34 HTTP 4xx/5xx ERROR Rate on cp34 is OK: OK - NGINX Error Rate is 5% [21:26:42] RECOVERY - cp34 Nginx Backend for mw134 on cp34 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:27:30] RECOVERY - cp34 HTTPS on cp34 is OK: HTTP OK: HTTP/2 301 - 3556 bytes in 0.483 second response time [21:27:47] RECOVERY - cp25 Nginx Backend for phab121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:27:57] RECOVERY - cp25 Nginx Backend for test131 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:27:59] PROBLEM - swiftobject113 Current Load on swiftobject113 is CRITICAL: CRITICAL - load average: 8.46, 7.88, 6.73 [21:28:18] RECOVERY - cp25 Nginx Backend for mw133 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:28:26] RECOVERY - cp25 Nginx Backend for mw131 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:28:40] RECOVERY - cp25 Nginx Backend for mw142 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:28:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is WARNING: WARNING - load average: 7.57, 6.62, 5.55 [21:28:42] RECOVERY - cp25 Nginx Backend for mw141 on cp25 is OK: TCP OK - 0.001 second response time on localhost port 8108 [21:28:46] RECOVERY - cp25 Nginx Backend for mw143 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:29:02] RECOVERY - cp25 Nginx Backend for mon141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:29:07] RECOVERY - cp25 Varnish Backends on cp25 is OK: All 15 backends are healthy [21:29:07] RECOVERY - cp25 Nginx Backend for mw132 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:29:08] RECOVERY - cp25 Nginx Backend for mwtask141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:29:09] RECOVERY - cp25 Nginx Backend for reports121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:29:19] RECOVERY - cp25 Nginx Backend for mw134 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:29:25] RECOVERY - cp25 Nginx Backend for mail121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:29:26] RECOVERY - cp25 HTTP 4xx/5xx ERROR Rate on cp25 is OK: OK - NGINX Error Rate is 4% [21:29:29] PROBLEM - graylog131 Current Load on graylog131 is WARNING: LOAD WARNING - total load average: 3.71, 2.92, 2.13 [21:29:31] RECOVERY - cp25 Nginx Backend for puppet141 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:29:32] RECOVERY - cp25 HTTPS on cp25 is OK: HTTP OK: HTTP/2 301 - 3556 bytes in 0.033 second response time [21:29:44] RECOVERY - cp25 Nginx Backend for matomo121 on cp25 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:30:33] RECOVERY - wiki.site97.fr - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.site97.fr' will expire on Sun 03 Mar 2024 13:09:55 GMT +0000. [21:30:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is CRITICAL: CRITICAL - load average: 9.22, 7.20, 5.87 [21:30:45] RECOVERY - archive.a2b2.org - LetsEncrypt on sslhost is OK: OK - Certificate 'archive.a2b2.org' will expire on Sat 02 Mar 2024 03:53:54 GMT +0000. [21:30:51] RECOVERY - publictestwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'publictestwiki.com' will expire on Fri 01 Mar 2024 00:25:08 GMT +0000. [21:30:52] RECOVERY - gil.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'gil.wiki' will expire on Thu 11 Jan 2024 16:58:08 GMT +0000. [21:30:52] RECOVERY - wiki.potabi.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.potabi.com' will expire on Sat 02 Mar 2024 11:24:38 GMT +0000. [21:30:55] RECOVERY - revi.wiki - PositiveSSLDV on sslhost is OK: OK - Certificate 'revi.wiki' will expire on Sun 29 Dec 2024 23:59:59 GMT +0000. [21:30:59] RECOVERY - wiki.consid.vn - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.consid.vn' will expire on Sat 02 Mar 2024 10:50:46 GMT +0000. [21:31:10] RECOVERY - wiki.thesimswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'www.thesimswiki.com' will expire on Mon 19 Feb 2024 02:16:01 GMT +0000. [21:31:22] RECOVERY - wiki.wilderyogi.eu - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.wilderyogi.eu' will expire on Sat 02 Mar 2024 03:28:42 GMT +0000. [21:31:22] RECOVERY - wiki.triplescripts.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.triplescripts.org' will expire on Fri 01 Mar 2024 20:47:17 GMT +0000. [21:31:26] RECOVERY - graylog131 Current Load on graylog131 is OK: LOAD OK - total load average: 3.26, 3.00, 2.25 [21:31:41] RECOVERY - hastursnotebook.org - LetsEncrypt on sslhost is OK: OK - Certificate 'hastursnotebook.org' will expire on Mon 04 Mar 2024 11:06:34 GMT +0000. [21:31:58] RECOVERY - apocrypha.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'apocrypha.wiki' will expire on Fri 01 Mar 2024 12:06:59 GMT +0000. [21:32:07] RECOVERY - wikappedia.cc - LetsEncrypt on sslhost is OK: OK - Certificate 'wikappedia.cc' will expire on Sun 17 Mar 2024 17:32:40 GMT +0000. [21:32:42] PROBLEM - swiftobject112 Current Load on swiftobject112 is WARNING: WARNING - load average: 7.38, 7.44, 6.14 [21:34:34] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.gab.pt.eu.org All nameservers failed to answer the query. [21:34:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is CRITICAL: CRITICAL - load average: 10.66, 8.41, 6.63 [21:38:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is WARNING: WARNING - load average: 4.86, 6.86, 6.44 [21:40:05] RECOVERY - cp35 Nginx Backend for mw141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8108 [21:40:06] RECOVERY - cp35 Nginx Backend for mw142 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8109 [21:40:08] RECOVERY - cp35 Nginx Backend for test131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8180 [21:40:23] RECOVERY - cp35 Nginx Backend for mon141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8201 [21:40:34] RECOVERY - cp35 Nginx Backend for phab121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8202 [21:40:38] RECOVERY - cp35 Nginx Backend for mw143 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8112 [21:40:41] RECOVERY - swiftobject112 Current Load on swiftobject112 is OK: OK - load average: 6.75, 6.72, 6.43 [21:40:41] RECOVERY - cp35 Nginx Backend for mwtask141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8150 [21:40:42] RECOVERY - cp35 Nginx Backend for reports121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8205 [21:40:59] RECOVERY - cp35 Nginx Backend for puppet141 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8204 [21:41:05] RECOVERY - wiki.themarkside.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.themarkside.com' will expire on Fri 16 Feb 2024 19:22:49 GMT +0000. [21:41:06] RECOVERY - closinglogosgroup.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:41:07] RECOVERY - cp35 HTTP 4xx/5xx ERROR Rate on cp35 is OK: OK - NGINX Error Rate is 1% [21:41:08] RECOVERY - cp35 Nginx Backend for mail121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8200 [21:41:10] RECOVERY - wiki.cryptoroyale.one - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.cryptoroyale.one' will expire on Sun 03 Mar 2024 17:58:02 GMT +0000. [21:41:11] RECOVERY - pwsc.polandballwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'pwsc.polandballwiki.com' will expire on Sat 02 Mar 2024 12:06:53 GMT +0000. [21:41:18] RECOVERY - wiki.coolstation.space - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.coolstation.space' will expire on Wed 13 Mar 2024 07:35:23 GMT +0000. [21:41:18] RECOVERY - cp35 Nginx Backend for mw131 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8106 [21:41:21] RECOVERY - celeste.ink - LetsEncrypt on sslhost is OK: OK - Certificate 'celeste.ink' will expire on Sat 02 Mar 2024 03:04:52 GMT +0000. [21:41:25] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [21:41:25] RECOVERY - familiacorsi.com - LetsEncrypt on sslhost is OK: OK - Certificate 'familiacorsi.com' will expire on Thu 14 Mar 2024 19:30:01 GMT +0000. [21:41:27] RECOVERY - cp35 Nginx Backend for mw133 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8110 [21:41:29] RECOVERY - cp35 Nginx Backend for mw132 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8107 [21:41:37] RECOVERY - cp35 Nginx Backend for mw134 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8111 [21:41:38] RECOVERY - wiki.thehall.xyz - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.thehall.xyz' will expire on Fri 01 Mar 2024 21:04:02 GMT +0000. [21:41:41] RECOVERY - iceria.org - LetsEncrypt on sslhost is OK: OK - Certificate 'www.iceria.org' will expire on Fri 01 Mar 2024 19:52:36 GMT +0000. [21:41:41] RECOVERY - cp35 Nginx Backend for matomo121 on cp35 is OK: TCP OK - 0.000 second response time on localhost port 8203 [21:41:45] RECOVERY - rarewarewiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'rarewarewiki.com' will expire on Sun 03 Mar 2024 19:39:38 GMT +0000. [21:41:46] RECOVERY - elsterclopedie.marithaime.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'elsterclopedie.marithaime.nl' will expire on Sun 03 Mar 2024 21:41:53 GMT +0000. [21:41:46] RECOVERY - ncuwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'ncuwiki.com' will expire on Sun 03 Mar 2024 20:58:47 GMT +0000. [21:41:47] RECOVERY - wiki.infomedia.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.infomedia.co.uk' will expire on Sun 03 Mar 2024 03:24:52 GMT +0000. [21:41:58] RECOVERY - cp35 Varnish Backends on cp35 is OK: All 15 backends are healthy [21:41:59] RECOVERY - wiki.ivy.cm - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.ivy.cm' will expire on Wed 06 Mar 2024 02:21:23 GMT +0000. [21:42:00] RECOVERY - wiki.worldbuilding.network - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.worldbuilding.network' will expire on Sat 02 Mar 2024 11:53:08 GMT +0000. [21:42:04] RECOVERY - cp35 HTTPS on cp35 is OK: HTTP OK: HTTP/2 301 - 3555 bytes in 0.472 second response time [21:42:06] RECOVERY - wiki.dwarvesrp.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.dwarvesrp.com' will expire on Sun 03 Mar 2024 20:17:35 GMT +0000. [21:42:07] RECOVERY - wiki.lewisgill.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.lewisgill.com' will expire on Mon 26 Feb 2024 23:08:02 GMT +0000. [21:42:07] RECOVERY - history.estill.org - LetsEncrypt on sslhost is OK: OK - Certificate 'history.estill.org' will expire on Fri 01 Mar 2024 19:03:02 GMT +0000. [21:42:10] RECOVERY - wiki.mastodon.kr - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.mastodon.kr' will expire on Sun 03 Mar 2024 13:55:20 GMT +0000. [21:42:11] RECOVERY - rare.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:42:13] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [21:42:14] RECOVERY - www.trollpasta.com - LetsEncrypt on sslhost is OK: OK - Certificate 'trollpasta.com' will expire on Sat 02 Mar 2024 02:16:33 GMT +0000. [21:42:28] RECOVERY - sarovia.graalmilitary.com - LetsEncrypt on sslhost is OK: OK - Certificate 'sarovia.graalmilitary.com' will expire on Sat 02 Mar 2024 04:35:37 GMT +0000. [21:42:28] RECOVERY - wizardia.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'wizardia.wiki' will expire on Wed 13 Mar 2024 05:35:52 GMT +0000. [21:42:31] RECOVERY - infectowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'infectowiki.com' will expire on Fri 01 Mar 2024 18:29:41 GMT +0000. [21:42:41] RECOVERY - metroidpedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'metroidpedia.com' will expire on Sun 03 Mar 2024 19:06:43 GMT +0000. [21:42:42] RECOVERY - partopedia.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'partopedia.ru' will expire on Fri 16 Feb 2024 22:41:20 GMT +0000. [21:42:44] RECOVERY - wiki.yuanpi.eu.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.yuanpi.eu.org' will expire on Sun 18 Feb 2024 10:10:37 GMT +0000. [21:42:49] RECOVERY - portalsofphereon.com - LetsEncrypt on sslhost is OK: OK - Certificate 'www.portalsofphereon.com' will expire on Fri 01 Mar 2024 14:19:42 GMT +0000. [21:42:53] RECOVERY - puritwiki.p-e.kr - LetsEncrypt on sslhost is OK: OK - Certificate 'puritwiki.p-e.kr' will expire on Sun 03 Mar 2024 16:03:07 GMT +0000. [21:42:57] RECOVERY - wiki.wikimedia.cat - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.wikimedia.cat' will expire on Sat 02 Mar 2024 10:08:36 GMT +0000. [21:43:00] RECOVERY - dkpedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'dkpedia.com' will expire on Sun 03 Mar 2024 15:07:28 GMT +0000. [21:43:00] RECOVERY - acgn.sfdev.eu.org - LetsEncrypt on sslhost is OK: OK - Certificate 'acgn.sfdev.eu.org' will expire on Sun 03 Mar 2024 22:21:38 GMT +0000. [21:43:00] RECOVERY - webkinzguide.com - LetsEncrypt on sslhost is OK: OK - Certificate 'webkinzguide.com' will expire on Sun 03 Mar 2024 14:10:51 GMT +0000. [21:43:01] RECOVERY - wiki.closai.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.closai.com' will expire on Sun 28 Jan 2024 10:45:23 GMT +0000. [21:43:03] RECOVERY - files.pornwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'files.pornwiki.org' will expire on Sun 03 Mar 2024 20:20:52 GMT +0000. [21:43:10] RECOVERY - wiki.strangereons.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.strangereons.com' will expire on Fri 02 Feb 2024 19:08:37 GMT +0000. [21:43:10] RECOVERY - wiki.kingmingshrimp.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.kingmingshrimp.com' will expire on Fri 15 Mar 2024 19:05:57 GMT +0000. [21:43:12] RECOVERY - hoseki.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'hoseki.wiki' will expire on Sat 02 Mar 2024 16:41:30 GMT +0000. [21:43:13] RECOVERY - tl.awiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'tl.awiki.org' will expire on Fri 01 Mar 2024 20:19:07 GMT +0000. [21:43:14] RECOVERY - developer-and-testers.wiki.feign-wiki.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'developer-and-testers.wiki.feign-wiki.tk' will expire on Fri 09 Feb 2024 01:02:43 GMT +0000. [21:43:15] RECOVERY - 321nailswiki.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:43:15] RECOVERY - worldtriggerwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'worldtriggerwiki.com' will expire on Tue 20 Feb 2024 06:15:06 GMT +0000. [21:43:18] RECOVERY - opendatascot.org - LetsEncrypt on sslhost is OK: OK - Certificate 'opendatascot.org' will expire on Wed 06 Mar 2024 12:32:10 GMT +0000. [21:43:22] RECOVERY - yoshipedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'yoshipedia.com' will expire on Wed 13 Mar 2024 05:38:50 GMT +0000. [21:43:22] RECOVERY - wmworld.sktz.live - LetsEncrypt on sslhost is OK: OK - Certificate 'wmworld.sktz.live' will expire on Sat 02 Mar 2024 04:27:41 GMT +0000. [21:43:25] RECOVERY - stablestate.org - LetsEncrypt on sslhost is OK: OK - Certificate 'stablestate.org' will expire on Fri 01 Mar 2024 10:54:06 GMT +0000. [21:43:27] RECOVERY - wiki.grab-tools.live - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.grab-tools.live' will expire on Fri 12 Jan 2024 20:53:42 GMT +0000. [21:43:30] RECOVERY - wiki.drycleaninglobby.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.drycleaninglobby.net' will expire on Wed 06 Mar 2024 05:38:31 GMT +0000. [21:43:36] RECOVERY - n64brew.dev - LetsEncrypt on sslhost is OK: OK - Certificate 'n64brew.dev' will expire on Fri 01 Mar 2024 21:32:38 GMT +0000. [21:43:37] RECOVERY - de.berlinwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'de.berlinwiki.org' will expire on Fri 16 Feb 2024 19:18:59 GMT +0000. [21:43:40] RECOVERY - pwiki.arkcls.com - LetsEncrypt on sslhost is OK: OK - Certificate 'pwiki.arkcls.com' will expire on Fri 01 Mar 2024 10:20:44 GMT +0000. [21:43:44] RECOVERY - wiki.cutefame.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.cutefame.net' will expire on Fri 12 Jan 2024 20:52:10 GMT +0000. [21:43:54] RECOVERY - mhdh.pj568.eu.org - LetsEncrypt on sslhost is OK: OK - Certificate 'mhdh.pj568.eu.org' will expire on Thu 21 Mar 2024 17:54:02 GMT +0000. [21:43:55] RECOVERY - encyclopediarobotica.org - LetsEncrypt on sslhost is OK: OK - Certificate 'encyclopediarobotica.org' will expire on Sun 04 Feb 2024 03:32:10 GMT +0000. [21:43:56] RECOVERY - istpcomputing.com - LetsEncrypt on sslhost is OK: OK - Certificate 'istpcomputing.com' will expire on Sun 03 Mar 2024 16:19:48 GMT +0000. [21:43:57] RECOVERY - wiki.moores.tech - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.moores.tech' will expire on Thu 21 Mar 2024 18:05:31 GMT +0000. [21:44:04] RECOVERY - smashbros.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:44:04] RECOVERY - www.deadprem.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'deadprem.wiki' will expire on Wed 31 Jan 2024 12:16:06 GMT +0000. [21:44:17] RECOVERY - www.themagical.world - LetsEncrypt on sslhost is OK: OK - Certificate 'themagical.world' will expire on Wed 24 Jan 2024 17:08:11 GMT +0000. [21:44:27] RECOVERY - heavyironmodding.org - LetsEncrypt on sslhost is OK: OK - Certificate 'heavyironmodding.org' will expire on Sat 02 Mar 2024 02:51:13 GMT +0000. [21:44:29] RECOVERY - fid.koymi.net - LetsEncrypt on sslhost is OK: OK - Certificate 'fid.koymi.net' will expire on Fri 16 Feb 2024 19:19:57 GMT +0000. [21:44:30] RECOVERY - data.wikiyri.org - LetsEncrypt on sslhost is OK: OK - Certificate 'data.wikiyri.org' will expire on Thu 14 Mar 2024 19:51:12 GMT +0000. [21:44:41] RECOVERY - crustypedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'crustypedia.org' will expire on Tue 16 Jan 2024 08:18:21 GMT +0000. [21:44:41] RECOVERY - ajhalili2006.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:44:42] PROBLEM - swiftobject112 Current Load on swiftobject112 is CRITICAL: CRITICAL - load average: 8.92, 7.43, 6.76 [21:44:45] RECOVERY - www.tintinpedia.fr - LetsEncrypt on sslhost is OK: OK - Certificate 'tintinpedia.fr' will expire on Fri 08 Mar 2024 11:56:10 GMT +0000. [21:44:47] RECOVERY - electowiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'electowiki.org' will expire on Fri 01 Mar 2024 14:06:02 GMT +0000. [21:45:00] RECOVERY - wiki.harlonserver.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.harlonserver.net' will expire on Sun 03 Mar 2024 12:23:19 GMT +0000. [21:45:05] RECOVERY - wiki.anempireofdreams.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.anempireofdreams.com' will expire on Tue 13 Feb 2024 06:56:15 GMT +0000. [21:45:18] RECOVERY - lcn.zfc.id.lv - LetsEncrypt on sslhost is OK: OK - Certificate 'lcn.zfc.id.lv' will expire on Sat 02 Mar 2024 12:26:25 GMT +0000. [21:45:18] RECOVERY - wiki.pixandbit.gay - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.pixandbit.gay' will expire on Fri 08 Mar 2024 16:44:39 GMT +0000. [21:45:19] RECOVERY - echoes-wiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'echoes-wiki.com' will expire on Thu 14 Mar 2024 19:43:47 GMT +0000. [21:45:43] RECOVERY - wiki.evscope.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.evscope.org' will expire on Sun 03 Mar 2024 01:12:50 GMT +0000. [21:45:45] RECOVERY - wiki.miraheze.org - Sectigo on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Mon 18 Nov 2024 23:59:59 GMT +0000. [21:46:14] RECOVERY - correypedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'correypedia.org' will expire on Sat 02 Mar 2024 10:08:50 GMT +0000. [21:46:41] PROBLEM - swiftobject112 Current Load on swiftobject112 is WARNING: WARNING - load average: 6.79, 7.41, 6.86 [21:47:30] RECOVERY - wiki.songngu.xyz - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.songngu.xyz' will expire on Fri 19 Jan 2024 14:06:40 GMT +0000. [21:49:05] [02miraheze/puppet] 07The-Voidwalker pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/puppet/compare/a8e2e47097dd...6416946e576e [21:49:06] [02miraheze/puppet] 07The-Voidwalker 036416946 - nginx: ban zimit user agents [21:52:34] [02miraheze/puppet] 07The-Voidwalker pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/puppet/compare/6416946e576e...5bf70ef55b27 [21:52:36] [02miraheze/puppet] 07The-Voidwalker 035bf70ef - bad escape character [21:54:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is WARNING: WARNING - load average: 5.87, 6.93, 7.85 [21:54:41] RECOVERY - swiftobject112 Current Load on swiftobject112 is OK: OK - load average: 4.61, 6.16, 6.59 [22:00:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 9.89, 7.82, 7.81 [22:00:06] RECOVERY - wiki.bikinibottomdiscord.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.bikinibottomdiscord.org' will expire on Sat 02 Mar 2024 04:28:18 GMT +0000. [22:02:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is WARNING: WARNING - load average: 7.85, 7.78, 7.80 [22:03:15] PROBLEM - os141 Current Load on os141 is WARNING: LOAD WARNING - total load average: 3.85, 2.70, 1.63 [22:04:35] PROBLEM - wiki.gab.pt.eu.org - reverse DNS on sslhost is WARNING: NoNameservers: All nameservers failed to answer the query pt.eu.org. IN NS: Server 2606:4700:4700::1111 UDP port 53 answered SERVFAIL [22:05:15] RECOVERY - os141 Current Load on os141 is OK: LOAD OK - total load average: 1.50, 2.11, 1.54 [22:07:14] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 5.26, 6.63, 7.78 [22:10:43] RECOVERY - petrawiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'en.petrawiki.org' will expire on Sun 03 Mar 2024 18:10:17 GMT +0000. [22:11:50] RECOVERY - kirisame-kissaten.cf - LetsEncrypt on sslhost is OK: OK - Certificate 'kirisame-kissaten.cf' will expire on Sun 10 Mar 2024 13:53:38 GMT +0000. [22:12:26] RECOVERY - wiki.jsal.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.jsal.org' will expire on Sat 03 Feb 2024 14:39:59 GMT +0000. [22:14:02] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 8.34, 7.68, 7.56 [22:15:13] PROBLEM - swiftobject113 Current Load on swiftobject113 is CRITICAL: CRITICAL - load average: 9.01, 7.13, 7.31 [22:16:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is WARNING: WARNING - load average: 7.13, 7.43, 7.48 [22:17:14] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 7.45, 7.27, 7.34 [22:21:14] RECOVERY - swiftobject113 Current Load on swiftobject113 is OK: OK - load average: 4.49, 5.84, 6.75 [22:22:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is WARNING: WARNING - load average: 7.49, 7.54, 7.98 [22:26:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is CRITICAL: CRITICAL - load average: 10.16, 7.73, 7.89 [22:28:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is CRITICAL: CRITICAL - load average: 9.19, 7.51, 7.22 [22:30:01] PROBLEM - swiftobject111 Current Load on swiftobject111 is WARNING: WARNING - load average: 6.06, 7.04, 7.10 [22:31:17] PROBLEM - swiftobject113 Current Load on swiftobject113 is CRITICAL: CRITICAL - load average: 9.63, 7.19, 6.74 [22:33:13] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 6.29, 6.83, 6.67 [22:35:14] RECOVERY - swiftobject113 Current Load on swiftobject113 is OK: OK - load average: 4.21, 5.83, 6.31 [22:38:01] RECOVERY - swiftobject111 Current Load on swiftobject111 is OK: OK - load average: 4.35, 6.02, 6.74 [22:38:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is WARNING: WARNING - load average: 5.92, 7.40, 7.87 [22:52:01] PROBLEM - swiftobject121 Current Load on swiftobject121 is CRITICAL: CRITICAL - load average: 8.02, 7.01, 7.18 [22:55:46] PROBLEM - swiftobject113 Current Load on swiftobject113 is WARNING: WARNING - load average: 7.09, 6.75, 6.36 [22:56:02] PROBLEM - swiftobject121 Current Load on swiftobject121 is WARNING: WARNING - load average: 5.04, 6.53, 6.97 [22:57:41] RECOVERY - swiftobject113 Current Load on swiftobject113 is OK: OK - load average: 6.37, 6.69, 6.38 [23:04:02] RECOVERY - swiftobject121 Current Load on swiftobject121 is OK: OK - load average: 4.30, 5.77, 6.54 [23:26:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 5.78, 6.57, 7.81 [23:34:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 8.40, 7.91, 7.90 [23:36:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.19, 7.43, 7.71 [23:40:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 8.88, 7.93, 7.83 [23:42:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is WARNING: WARNING - load average: 7.41, 7.45, 7.65 [23:44:03] PROBLEM - swiftobject101 Current Load on swiftobject101 is CRITICAL: CRITICAL - load average: 8.45, 7.59, 7.66