[00:11:48] RECOVERY - cp171 Disk Space on cp171 is OK: DISK OK - free space: / 73939MiB (16% inode=99%); [00:13:18] RECOVERY - cp191 Disk Space on cp191 is OK: DISK OK - free space: / 74464MiB (16% inode=99%); [00:13:49] RECOVERY - cp201 Disk Space on cp201 is OK: DISK OK - free space: / 73434MiB (16% inode=99%); [06:36:14] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 10.28, 9.52, 6.61 [06:38:13] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.93, 8.01, 6.41 [12:24:22] miraheze/puppet - paladox the build passed. [12:24:28] miraheze/puppet - paladox the build passed. [12:26:37] miraheze/puppet - paladox the build passed. [12:31:14] miraheze/puppet - paladox the build passed. [12:33:16] miraheze/puppet - paladox the build passed. [12:33:42] miraheze/puppet - paladox the build passed. [12:36:59] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:02] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:03] PROBLEM - mwtask161 videoscaler.svc.fsslc.wtnet HTTP on mwtask161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:06] PROBLEM - swiftproxy161 HTTP on swiftproxy161 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:07] PROBLEM - phorge171 phorge-static.wikitide.net HTTPS on phorge171 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:08] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:11] PROBLEM - test151 HTTPS on test151 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:12] PROBLEM - mwtask161 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:12] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:13] PROBLEM - swiftproxy171 HTTPS on swiftproxy171 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:17] PROBLEM - mon181 monitoring.wikitide.net HTTPS on mon181 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:17] PROBLEM - mwtask151 HTTPS on mwtask151 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:19] PROBLEM - llm191 HTTPS on llm191 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:21] PROBLEM - cp201 health.wikitide.net HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:23] PROBLEM - mwtask181 videoscaler.svc.fsslc.wtnet HTTP on mwtask181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:23] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:24] PROBLEM - swiftproxy161 HTTPS on swiftproxy161 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:27] PROBLEM - reports171 HTTPS on reports171 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:30] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:32] PROBLEM - phorge171 issue-tracker.miraheze.org HTTPS on phorge171 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:37:35] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:35] PROBLEM - mwtask171 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:36] PROBLEM - cp171 health.wikitide.net HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:37] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:37:40] PROBLEM - mwtask151 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:40] PROBLEM - mwtask181 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:37:55] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:01] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:05] PROBLEM - mwtask151 jobrunner.svc.fsslc.wtnet HTTP on mwtask151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:05] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:11] PROBLEM - mwtask151 videoscaler.svc.fsslc.wtnet HTTP on mwtask151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:17] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:18] PROBLEM - mwtask171 videoscaler.svc.fsslc.wtnet HTTP on mwtask171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:19] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:19] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:20] PROBLEM - prometheus151 Puppet on prometheus151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:38:20] PROBLEM - mw151 Puppet on mw151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:38:27] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:28] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:28] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:30] PROBLEM - mwtask171 jobrunner.svc.fsslc.wtnet HTTP on mwtask171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:31] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:31] PROBLEM - mwtask171 HTTPS on mwtask171 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:33] PROBLEM - graylog161 HTTPS on graylog161 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:33] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:41] PROBLEM - mwtask181 HTTPS on mwtask181 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:41] PROBLEM - mon181 HTTPS on mon181 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:43] PROBLEM - mwtask181 jobrunner.svc.fsslc.wtnet HTTP on mwtask181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:43] PROBLEM - mon181 grafana.wikitide.net HTTPS on mon181 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:38:43] PROBLEM - cp191 health.wikitide.net HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:45] PROBLEM - matomo151 HTTPS on matomo151 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:51] PROBLEM - mw153.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.800B7905A2140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:38:52] PROBLEM - mwtask161 HTTPS on mwtask161 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:54] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:54] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:55] PROBLEM - mwtask161 jobrunner.svc.fsslc.wtnet HTTP on mwtask161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 9005: cURL returned 3 - URL using bad/illegal format or missing URL [12:38:55] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Unable to lookup IP address for '': getaddrinfo returned -2 - Name or service not known [12:38:59] PROBLEM - swiftproxy171 HTTP on swiftproxy171 is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:39:27] PROBLEM - mw171.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.804B3892C9140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:39:59] PROBLEM - mw152.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.806B576208150000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:41:24] PROBLEM - mw202.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.80EB090F90140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:41:27] PROBLEM - mw202 Puppet on mw202 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:41:41] miraheze/puppet - paladox the build passed. [12:42:07] PROBLEM - mw162 Puppet on mw162 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:42:10] PROBLEM - mw172 Puppet on mw172 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:42:34] PROBLEM - mw161 Puppet on mw161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:42:39] PROBLEM - mwtask171 Puppet on mwtask171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:42:57] PROBLEM - mw161.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.803B69FF67140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:42:59] PROBLEM - mw151.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.809BFE2277140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:43:12] PROBLEM - mw173.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.808B048706150000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:43:23] PROBLEM - mw193.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.805B89B285140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:43:50] PROBLEM - mw203 Puppet on mw203 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:43:56] miraheze/puppet - paladox the build passed. [12:44:09] PROBLEM - mwtask161 Puppet on mwtask161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:44:35] miraheze/puppet - paladox the build passed. [12:44:52] PROBLEM - mw162.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.80BB013670140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:45:21] miraheze/puppet - paladox the build passed. [12:45:21] PROBLEM - mwtask151 Puppet on mwtask151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:45:31] PROBLEM - mw163.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.80BB132C6A140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:45:56] huh [12:46:05] PROBLEM - mw173 Puppet on mw173 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:46:43] PROBLEM - swift-lb.wikitide.net - LetsEncrypt on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [12:47:43] PROBLEM - mw193 Puppet on mw193 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:47:56] PROBLEM - mw181.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.807BB279CD140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:49:22] PROBLEM - mw191.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.80DB302036150000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:49:26] PROBLEM - mw182.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.807BDDBD54150000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:50:17] PROBLEM - mw192.fsslc.wtnet SSL Check on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection.80DBC5B292140000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1605:SSL alert number 40 [12:51:45] PROBLEM - mw153 Puppet on mw153 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:51:55] PROBLEM - mw171 Puppet on mw171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:52:44] RECOVERY - mwtask181 videoscaler.svc.fsslc.wtnet HTTP on mwtask181 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:52:45] RECOVERY - mwtask161 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask161 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.003 second response time [12:52:46] RECOVERY - reports171 HTTPS on reports171 is OK: HTTP OK: HTTP/2 200 - 1139 bytes in 0.024 second response time [12:52:47] RECOVERY - mw181.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [12:52:47] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.057 second response time [12:52:50] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [12:52:51] RECOVERY - mw192.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [12:52:53] RECOVERY - mwtask151 HTTPS on mwtask151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4228 bytes in 0.060 second response time [12:52:54] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.067 second response time [12:52:56] RECOVERY - cp171 health.wikitide.net HTTPS on cp171 is OK: HTTP OK: HTTP/2 200 - 112 bytes in 0.009 second response time [12:52:58] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.062 second response time [12:52:58] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.063 second response time [12:53:00] RECOVERY - swiftproxy171 HTTPS on swiftproxy171 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.034 second response time [12:53:04] RECOVERY - llm191 HTTPS on llm191 is OK: HTTP OK: HTTP/2 200 - 354 bytes in 0.046 second response time [12:53:07] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.065 second response time [12:53:07] fixed, some how puppet applied the old icinga config [12:53:08] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.064 second response time [12:53:12] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.068 second response time [12:53:12] RECOVERY - cp201 health.wikitide.net HTTPS on cp201 is OK: HTTP OK: HTTP/2 200 - 112 bytes in 0.010 second response time [12:53:13] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.056 second response time [12:53:16] RECOVERY - swiftproxy161 HTTPS on swiftproxy161 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.024 second response time [12:53:18] RECOVERY - mwtask181 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask181 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:53:20] RECOVERY - phorge171 issue-tracker.miraheze.org HTTPS on phorge171 is OK: HTTP OK: HTTP/1.1 200 OK - 19375 bytes in 0.063 second response time [12:53:20] i guess maybe a race condition [12:53:21] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.056 second response time [12:53:21] RECOVERY - mwtask171 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask171 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:53:22] RECOVERY - mon181 monitoring.wikitide.net HTTPS on mon181 is OK: HTTP OK: HTTP/1.1 302 Found - 298 bytes in 0.016 second response time [12:53:23] RECOVERY - mwtask151 jobrunner-high.svc.fsslc.wtnet HTTP on mwtask151 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.003 second response time [12:53:23] PROBLEM - mw191 Puppet on mw191 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:53:34] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.064 second response time [12:53:34] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [12:53:36] RECOVERY - test151 HTTPS on test151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4226 bytes in 0.060 second response time [12:53:38] RECOVERY - swiftproxy171 HTTP on swiftproxy171 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.013 second response time [12:53:39] RECOVERY - matomo151 HTTPS on matomo151 is OK: HTTP OK: HTTP/2 200 - 553 bytes in 0.203 second response time [12:53:39] RECOVERY - mwtask151 videoscaler.svc.fsslc.wtnet HTTP on mwtask151 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.004 second response time [12:53:40] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4328 bytes in 0.070 second response time [12:53:51] RECOVERY - mwtask171 videoscaler.svc.fsslc.wtnet HTTP on mwtask171 is OK: HTTP OK: HTTP/1.1 204 No Content - 167 bytes in 0.002 second response time [12:54:00] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.060 second response time [12:54:03] RECOVERY - mwtask171 HTTPS on mwtask171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4228 bytes in 0.062 second response time [12:54:05] RECOVERY - mon181 grafana.wikitide.net HTTPS on mon181 is OK: HTTP OK: HTTP/1.1 200 OK - 63858 bytes in 0.024 second response time [12:54:10] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.052 second response time [12:54:11] RECOVERY - mwtask171 jobrunner.svc.fsslc.wtnet HTTP on mwtask171 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:54:12] RECOVERY - mon181 HTTPS on mon181 is OK: HTTP OK: HTTP/2 200 - 336 bytes in 0.023 second response time [12:54:13] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.054 second response time [12:54:13] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.055 second response time [12:54:16] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.068 second response time [12:54:17] RECOVERY - graylog161 HTTPS on graylog161 is OK: HTTP OK: HTTP/2 200 - 646 bytes in 0.020 second response time [12:54:18] RECOVERY - mwtask161 HTTPS on mwtask161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4228 bytes in 0.057 second response time [12:54:18] RECOVERY - mwtask151 jobrunner.svc.fsslc.wtnet HTTP on mwtask151 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.003 second response time [12:54:20] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.054 second response time [12:54:23] RECOVERY - mwtask181 HTTPS on mwtask181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4228 bytes in 0.058 second response time [12:54:25] RECOVERY - swiftproxy161 HTTP on swiftproxy161 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.023 second response time [12:54:26] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.059 second response time [12:54:29] RECOVERY - phorge171 phorge-static.wikitide.net HTTPS on phorge171 is OK: HTTP OK: Status line output matched "HTTP/1.1 200" - 17668 bytes in 0.033 second response time [12:54:30] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.048 second response time [12:54:31] RECOVERY - mwtask161 jobrunner.svc.fsslc.wtnet HTTP on mwtask161 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:54:33] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.059 second response time [12:54:38] RECOVERY - cp191 health.wikitide.net HTTPS on cp191 is OK: HTTP OK: HTTP/2 200 - 112 bytes in 0.009 second response time [12:54:39] RECOVERY - mwtask181 jobrunner.svc.fsslc.wtnet HTTP on mwtask181 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.002 second response time [12:54:39] RECOVERY - mwtask161 videoscaler.svc.fsslc.wtnet HTTP on mwtask161 is OK: HTTP OK: HTTP/1.1 204 No Content - 168 bytes in 0.003 second response time [12:58:19] PROBLEM - mw192 Puppet on mw192 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:00:16] PROBLEM - mw163 Puppet on mw163 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:14] PROBLEM - mw181 Puppet on mw181 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:55] PROBLEM - mw201 Puppet on mw201 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:05:03] RECOVERY - prometheus151 Puppet on prometheus151 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [13:05:55] miraheze/puppet - paladox the build passed. [13:06:03] PROBLEM - mw152 Puppet on mw152 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:06:15] miraheze/puppet - paladox the build passed. [13:06:36] PROBLEM - mw182 Puppet on mw182 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:06:43] PROBLEM - mw183 Puppet on mw183 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:07:01] miraheze/puppet - paladox the build passed. [13:07:21] RECOVERY - mw153.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:08:19] RECOVERY - mw171.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:08:36] miraheze/puppet - paladox the build passed. [13:08:52] RECOVERY - mw152.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:09:35] RECOVERY - mw162 Puppet on mw162 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [13:09:36] RECOVERY - mw151 Puppet on mw151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:09:40] RECOVERY - mw202 Puppet on mw202 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [13:10:01] RECOVERY - mw202.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:10:08] RECOVERY - mw161 Puppet on mw161 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [13:11:14] RECOVERY - mw172 Puppet on mw172 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:11:48] RECOVERY - mw151.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:11:51] RECOVERY - mw173.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:12:06] RECOVERY - mw161.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:12:10] RECOVERY - mwtask161 Puppet on mwtask161 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [13:12:18] RECOVERY - mwtask171 Puppet on mwtask171 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [13:12:26] RECOVERY - mw193.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:12:27] RECOVERY - mw203 Puppet on mw203 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:13:32] RECOVERY - mw162.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:13:44] RECOVERY - mw173 Puppet on mw173 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [13:14:04] RECOVERY - mw163.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:14:49] RECOVERY - mwtask151 Puppet on mwtask151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:15:04] miraheze/puppet - paladox the build passed. [13:16:05] RECOVERY - swift-lb.wikitide.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.net' will expire on Mon 29 Dec 2025 03:38:37 PM GMT +0000. [13:17:45] RECOVERY - mw193 Puppet on mw193 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [13:19:05] RECOVERY - mw182.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:19:11] RECOVERY - mw191.fsslc.wtnet SSL Check on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Tue 03 Apr 2040 12:14:00 PM GMT +0000. [13:21:12] RECOVERY - mw171 Puppet on mw171 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [13:22:26] RECOVERY - mw153 Puppet on mw153 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:22:56] RECOVERY - mw191 Puppet on mw191 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:26:21] miraheze/puppet - paladox the build passed. [13:27:26] miraheze/puppet - paladox the build passed. [13:27:46] RECOVERY - mw192 Puppet on mw192 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:28:02] miraheze/puppet - paladox the build passed. [13:29:16] RECOVERY - mw163 Puppet on mw163 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:30:12] miraheze/puppet - paladox the build passed. [13:32:06] RECOVERY - mw181 Puppet on mw181 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [13:33:30] miraheze/puppet - paladox the build passed. [13:34:43] RECOVERY - mw201 Puppet on mw201 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:35:48] RECOVERY - mw182 Puppet on mw182 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [13:36:23] RECOVERY - mw152 Puppet on mw152 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:37:22] RECOVERY - mw183 Puppet on mw183 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:44:39] miraheze/puppet - paladox the build passed. [13:46:36] miraheze/puppet - paladox the build passed. [13:58:41] miraheze/puppet - paladox the build passed. [14:00:15] miraheze/puppet - paladox the build passed. [14:03:00] miraheze/puppet - paladox the build passed. [14:09:46] miraheze/puppet - paladox the build passed. [14:18:19] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [14:26:19] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [14:31:55] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php /srv/mediawiki/1.44/maintenance/deleteBatch.php --wiki=regailiawiki --r '[[phab:T14395|Requested]]' /home/somerandomdeveloper/T14395.txt (START) [14:31:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:32:13] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php /srv/mediawiki/1.44/maintenance/deleteBatch.php --wiki=regailiawiki --r '[[phab:T14395|Requested]]' /home/somerandomdeveloper/T14395.txt (END - exit=0) [14:32:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:11:05] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/3b418e04c1a6403d2af9e20e399243bd86028c6c [16:11:05] 02puppet/03main 07paladox 033b418e0 Revert "mediawiki: set opcache.max_wasted_percentage to 3% (#4557)"… [16:55:36] PROBLEM - cp201 Disk Space on cp201 is WARNING: DISK WARNING - free space: / 49791MiB (10% inode=99%); [17:09:28] PROBLEM - cp171 Disk Space on cp171 is WARNING: DISK WARNING - free space: / 49839MiB (10% inode=99%); [17:37:17] PROBLEM - cp191 Disk Space on cp191 is WARNING: DISK WARNING - free space: / 49878MiB (10% inode=99%); [17:49:07] !log [reception@mwtask181] starting deploy of {'pull': 'config', 'config': True, 'force': True} to all [17:49:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:49:30] !log [reception@mwtask181] finished deploy of {'pull': 'config', 'config': True, 'force': True} to all - SUCCESS in 23s [17:49:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:49:54] miraheze/mw-config - Reception123 the build passed. [19:24:19] miraheze/mw-config - SomeMWDev the build passed. [19:24:27] miraheze/mw-config - SomeMWDev the build passed. [19:24:27] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [19:24:28] !log [somerandomdeveloper@test151] finished deploy of {'pull': 'config', 'config': True} to test151 - SUCCESS in 0s [19:24:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:24:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:24:39] !log [somerandomdeveloper@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [19:24:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:25:03] !log [somerandomdeveloper@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 23s [19:25:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:58:27] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 65.12, 27.12, 11.04 [20:22:01] @paladox any change you can take a look at db171, it's been critical for 30 mins [20:25:40] !log [paladox@mwtask181] starting deploy of {'config': True, 'force': True} to all [20:25:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:03] !log [paladox@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 23s [20:26:50] [Grafana] FIRING: Some MediaWiki Appservers are running out of PHP-FPM workers. https://grafana.wikitide.net/d/GtxbP1Xnk?from=1760469980000&orgId=1&to=1760473610034 [20:27:02] !log [paladox@mwtask181] starting deploy of {'config': True, 'force': True} to all [20:27:25] !log [paladox@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 23s [20:27:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:31:50] [Grafana] RESOLVED: PHP-FPM Worker Usage High https://grafana.wikitide.net/d/GtxbP1Xnk?from=1760470010000&orgId=1&to=1760473610000 [20:54:27] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 1.38, 3.10, 11.83 [20:58:27] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 2.16, 3.42, 10.00 [21:09:54] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php /srv/mediawiki/1.44/maintenance/deleteBatch.php --wiki=regailiawiki --r '[[phab:T14395|Requested]]' /home/somerandomdeveloper/T14395-2.txt (START) [21:09:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:13:04] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php /srv/mediawiki/1.44/maintenance/deleteBatch.php --wiki=regailiawiki --r '[[phab:T14395|Requested]]' /home/somerandomdeveloper/T14395-2.txt (END - exit=0) [21:13:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:18:27] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 11.77, 10.83, 8.36 [21:20:27] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 32.63, 15.94, 10.31 [22:02:22] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [22:02:23] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [22:02:27] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 4.63, 7.88, 11.55 [22:02:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:02:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:08:27] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 4.18, 6.28, 9.88 [22:12:48] [02mw-config] 07SomeMWDev created 03T14400 (+2 new commits) 13https://github.com/miraheze/mw-config/compare/5c055e68b64a^...fa773e4bb797 [22:12:48] 02mw-config/03T14400 07SomeRandomDeveloper 035c055e6 Reapply "Change default extensions for new wikis" (#6142)… [22:12:48] 02mw-config/03T14400 07SomeRandomDeveloper 03fa773e4 Add TimedMediaHandler SQL to wgCreateWikiSQLFiles… [22:13:06] [02mw-config] 07SomeMWDev drafted pull request #6143: T14400 (03main...03T14400) 13https://github.com/miraheze/mw-config/pull/6143 [22:13:15] [02mw-config] 07SomeMWDev retitled PR #6143: "T14400" ➜ "Restore default extension changes" 13https://github.com/miraheze/mw-config/pull/6143 [22:13:58] miraheze/mw-config - SomeMWDev the build passed. [22:14:29] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [22:14:30] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [22:14:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:14:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:22:36] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [22:22:37] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [22:22:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:22:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:23:17] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 12.38, 13.38, 10.85 [22:29:08] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 4.65, 9.71, 10.30 [22:31:04] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 4.91, 8.20, 9.67 [22:40:42] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 9.76, 11.23, 10.58 [22:42:39] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 15.56, 12.77, 11.22 [22:48:29] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 6.66, 11.86, 11.65 [22:54:27] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 4.43, 6.93, 9.49 [23:40:27] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 23.27, 13.98, 8.74 [23:55:26] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/9287528c7ee9931f25a3fcd0e2a568e1d8774c44 [23:55:26] 02ssl/03main 07WikiTideBot 039287528 Bot: Auto-update domain lists [23:58:27] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 4.73, 8.58, 11.89