[00:01:05] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/358624ef22c04aa8206e562f285b2b5cfdc04b68 [00:01:05] 02statichelp/03main 07WikiTideBot 03358624e Bot: Auto-update Tech namespace pages 2026-05-03 00:01:03 [01:10:28] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 26.02, 11.48, 5.13 [01:15:05] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [01:15:22] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [01:15:22] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:15:29] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 3 backends are down. mw172 mw201 mw202 [01:15:31] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 3 backends are down. mw172 mw201 mw202 [01:15:34] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:15:37] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 3 backends are down. mw172 mw201 mw202 [01:16:00] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:05] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:16:05] PROBLEM - db161 PowerDNS Recursor on db161 is CRITICAL: CRITICAL - Plugin timed out while executing system call [01:16:21] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [01:16:23] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:16:27] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:16:27] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:16:28] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:28] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:16:32] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:16:34] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:34] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:16:38] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 4 backends are down. mw153 mw163 mw173 mw201 [01:16:38] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:16:42] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:43] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:16:45] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:46] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:16:50] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:16:52] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:17:09] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:17:15] PROBLEM - db161 APT on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [01:17:21] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:17:22] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:17:30] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 64% [01:17:46] PROBLEM - db161 Puppet on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [01:18:13] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:18:31] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:19:06] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:21:20] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 5.019 second response time [01:21:23] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 4.464 second response time [01:21:23] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.913 second response time [01:21:23] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.194 second response time [01:21:25] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 6.834 second response time [01:21:30] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 44% [01:21:50] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [01:21:56] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.208 second response time [01:22:13] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [01:22:16] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.210 second response time [01:22:18] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [01:22:20] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.463 second response time [01:22:22] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.081 second response time [01:22:24] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.181 second response time [01:22:26] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.078 second response time [01:22:28] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.225 second response time [01:22:28] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [01:22:28] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.180 second response time [01:22:34] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.061 second response time [01:22:35] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.214 second response time [01:22:38] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [01:22:39] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.140 second response time [01:22:40] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.059 second response time [01:22:52] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.488 second response time [01:22:52] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.641 second response time [01:23:30] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 37% [01:25:25] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:25:26] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:25:33] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:25:35] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:25:38] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:25:50] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:03] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:26:20] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:26:22] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:25] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:26:26] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:28] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:26:30] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:26:30] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [01:26:30] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:26:31] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:32] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:26:34] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:38] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 1 backends are down. mw163 [01:26:38] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:26:45] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:26:46] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:26:52] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:26:56] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:27:30] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 72% [01:28:10] PROBLEM - db161 conntrack_table_size on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [01:28:22] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 4.554 second response time [01:28:25] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.021 second response time [01:28:26] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 4.929 second response time [01:28:26] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.237 second response time [01:28:27] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 1.593 second response time [01:28:27] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 5.625 second response time [01:28:28] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.073 second response time [01:28:30] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.796 second response time [01:28:31] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.567 second response time [01:28:31] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.382 second response time [01:28:32] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.866 second response time [01:28:32] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.587 second response time [01:28:38] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [01:28:43] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.210 second response time [01:28:44] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.194 second response time [01:28:51] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.632 second response time [01:29:01] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 6.642 second response time [01:32:16] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:32:20] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:32:22] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:32:24] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:32:28] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.014 second response time [01:32:28] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10005 milliseconds with 0 bytes received [01:32:29] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:32:30] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [01:32:36] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:32:38] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:32:38] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [01:32:47] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [01:32:48] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:32:51] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [01:33:10] PROBLEM - db161 SSH on db161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:33:16] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [01:36:36] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [01:36:38] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 1 backends are down. mw163 [01:36:48] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [01:41:01] !log [void@mwtask181] starting deploy of {'config': True, 'force': True} to all [01:41:12] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 3.085 second response time [01:41:14] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 4.067 second response time [01:41:17] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 6.230 second response time [01:41:20] !log [void@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 19s [01:41:22] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 3.048 second response time [01:41:27] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 3.659 second response time [01:41:28] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.071 second response time [01:41:30] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.065 second response time [01:41:34] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [01:41:39] !log [void@mwtask181] depool c2 [01:41:44] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.080 second response time [01:41:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:41:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:41:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:41:57] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [01:42:10] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.258 second response time [01:42:15] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.082 second response time [01:42:15] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [01:42:17] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.214 second response time [01:42:20] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.242 second response time [01:42:22] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.077 second response time [01:42:23] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.077 second response time [01:42:26] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.217 second response time [01:42:28] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.225 second response time [01:42:32] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.080 second response time [01:42:36] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.084 second response time [01:42:37] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.214 second response time [01:42:38] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [01:42:39] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.076 second response time [01:42:40] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.273 second response time [01:42:40] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.252 second response time [01:43:11] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.085 second response time [01:43:14] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.241 second response time [01:43:15] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.251 second response time [01:43:29] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [01:43:30] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 28% [01:43:32] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [01:43:37] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [01:44:17] PROBLEM - mwtask181 Puppet on mwtask181 is WARNING: WARNING: Puppet is currently disabled, message: reason not specified, last run 11 minutes ago with 0 failures [01:45:44] RECOVERY - db161 SSH on db161 is OK: SSH OK - OpenSSH_10.0p2 (protocol 2.0) [01:52:16] PROBLEM - db161 SSH on db161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:52:50] PROBLEM - db161 MariaDB on db161 is UNKNOWN: [01:53:06] PROBLEM - db161 ferm_active on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [01:53:20] PROBLEM - db161 Check unit status of sql-backup on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [01:55:21] RECOVERY - db161 MariaDB on db161 is OK: Uptime: 1473120 Threads: 78 Questions: 4069806171 Slow queries: 3667 Opens: 5655915 Open tables: 200000 Queries per second avg: 2762.711 [01:58:07] [02TSPortal] 07renovate[bot] created 03renovate/lock-file-maintenance (+1 new commit) 13https://github.com/miraheze/TSPortal/commit/ce5f3a73f498 [01:58:07] 02TSPortal/03renovate/lock-file-maintenance 07renovate[bot] 03ce5f3a7 Lock file maintenance [02:00:38] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [02:02:43] RECOVERY - db161 SSH on db161 is OK: SSH OK - OpenSSH_10.0p2 (protocol 2.0) [02:07:08] PROBLEM - db161 SSH on db161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:14:29] RECOVERY - db161 conntrack_table_size on db161 is OK: OK: nf_conntrack is 0 % full [02:14:29] RECOVERY - db161 PowerDNS Recursor on db161 is OK: DNS OK: 4.635 seconds response time. db161.fsslc.wtnet returns 10.0.16.128 [02:15:24] RECOVERY - db161 SSH on db161 is OK: SSH OK - OpenSSH_10.0p2 (protocol 2.0) [02:15:25] RECOVERY - db161 APT on db161 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [02:15:47] RECOVERY - db161 ferm_active on db161 is OK: OK ferm input default policy is set [02:16:05] RECOVERY - db161 Check unit status of sql-backup on db161 is OK: OK: Status of the systemd unit sql-backup [02:16:33] RECOVERY - db161 Puppet on db161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:17:56] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 0.80, 0.17, 0.05 [02:18:56] !log [void@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [02:18:57] !log [void@mwtask181] DEPLOY ABORTED: Canary check failed for publictestwiki.com@localhost [02:18:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:19:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:19:11] !log [void@mwtask181] starting deploy of {'pull': 'config', 'config': True, 'force': True} to all [02:19:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:19:30] !log [void@mwtask181] finished deploy of {'pull': 'config', 'config': True, 'force': True} to all - SUCCESS in 19s [02:19:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:19:37] !log [void@db161] reboot db161 [02:19:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:22:15] !log [void@mwtask181] starting deploy of {'config': True, 'force': True} to all [02:22:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:22:34] !log [void@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 18s [02:22:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:22:43] !log [void@mwtask181] repool c2 [02:22:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:24:17] RECOVERY - mwtask181 Puppet on mwtask181 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [03:00:20] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/26e869059fc7db9fe35a748aa91338bd06809974 [03:00:20] 02ssl/03main 07WikiTideBot 0326e8690 Bot: Auto-update domain lists [04:30:20] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/9a891171d7f1d79ba8895249dce12a69565a3465 [04:30:20] 02ssl/03main 07WikiTideBot 039a89117 Bot: Auto-update domain lists [05:00:25] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/ffe8b3a2a1de45867182890807e894c7dff7c8d2 [05:00:25] 02ssl/03main 07WikiTideBot 03ffe8b3a Bot: Auto-update domain lists [05:30:19] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/3e4a18b1c72117ab71d9af8ed94533eb973be5af [05:30:19] 02ssl/03main 07WikiTideBot 033e4a18b Bot: Auto-update domain lists [05:33:13] [02TSPortal] 07renovate[bot] merged 03renovate/lock-file-maintenance into 03main 13https://github.com/miraheze/TSPortal/compare/bbc8d48f94fb...ce5f3a73f498 [05:33:14] [02TSPortal] 07renovate[bot] 04deleted 03renovate/lock-file-maintenance at 03ce5f3a7 13https://api.github.com/repos/miraheze/TSPortal/commit/ce5f3a7 [06:43:18] [02ssl] 07WolFoXJotei commented on pull request #913: Commits on May 3, 2026 removed: […] 13https://github.com/miraheze/ssl/pull/913#issuecomment-4365580248 [06:52:42] [02ssl] 07Elaeagnifolia commented on pull request #913: Hello, I'm the bureaucrat for the Wiki and also the domain owner. My Miraheze user is under the same username, and my Github profile is listed under my user profile as well for confirmation. […] 13https://github.com/miraheze/ssl/pull/913#issuecomment-4365596778 [07:53:05] [02python-functions] 07renovate[bot] created 03renovate/all-deps (+1 new commit) 13https://github.com/miraheze/python-functions/commit/0148db2e4ff4 [07:53:05] 02python-functions/03renovate/all-deps 07renovate[bot] 030148db2 chore(deps): update dependency types-requests to v2.33.0.20260503 [08:00:35] [02ssl] 07lihaohong6 commented on pull request #913: @WolFoXJotei @Elaeagnifolia Awesome! Thanks for the confirmation. I'll go ahead and merge this PR. The redirect should take about 30 minutes to take effect. Visitors to the old domain will be automatically taken to the new domain. If you have Google […] 13https://github.com/miraheze/ssl/pull/913#issuecomment-4365705038 [08:01:12] [02ssl] 07lihaohong6 merged 07WolFoXJotei's pull request #913: Add redirect: loveanddeepspace.miraheze.org → lads.wiki (07miraheze:03main...07WolFoXJotei:03patch-1) 13https://github.com/miraheze/ssl/pull/913 [08:01:12] [02ssl] 07lihaohong6 pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/eaf91f6b5cdacac75e3f17a7e9e1a4e682712233 [08:01:12] 02ssl/03main 07WolFoXJotei 03eaf91f6 Add redirect: loveanddeepspace.miraheze.org → lads.wiki (#913) [12:59:21] PROBLEM - mw163 Puppet on mw163 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [12:59:46] PROBLEM - mw151 Puppet on mw151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:24] PROBLEM - mwtask181 Puppet on mwtask181 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:29:12] RECOVERY - mw163 Puppet on mw163 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [13:29:46] RECOVERY - mw151 Puppet on mw151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:34:22] RECOVERY - mwtask181 Puppet on mwtask181 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [13:51:30] PROBLEM - db161 Check unit status of sql-backup on db161 is CRITICAL: CRITICAL: Status of the systemd unit sql-backup [15:09:34] [02mw-config] 07pskyechology requested changes on pull request #6395 13https://github.com/miraheze/mw-config/pull/6395#pullrequestreview-4216454779 [15:09:34] [02mw-config] 07pskyechology left a file comment in pull request #6395 03ccbc7b4: This should be done in ManageWiki instead 13https://github.com/miraheze/mw-config/pull/6395#discussion_r3178303697 [15:53:29] [02mw-config] 07himvat-dev left a file comment in pull request #6395 03ccbc7b4: Removed it 13https://github.com/miraheze/mw-config/pull/6395#discussion_r3178361682 [16:59:11] miraheze/mw-config - himvat-dev the build passed. [17:32:42] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [18:00:42] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [18:30:24] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/bacac6720984fcb06c153c359464c68042766287 [18:30:25] 02ssl/03main 07WikiTideBot 03bacac67 Bot: Auto-update domain lists [22:35:56] !log [void@db161] systemctl reset-failed sql-backup && systemctl restart sql-backup [22:35:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:37:30] RECOVERY - db161 Check unit status of sql-backup on db161 is OK: OK: Status of the systemd unit sql-backup [23:45:33] [02mw-config] 07tbodt left a file comment in pull request #6398 038a471e0: Created https://issue-tracker.miraheze.org/T15330 to attempt to separate this decision into a separate task. 13https://github.com/miraheze/mw-config/pull/6398#discussion_r3178952892