[00:00:54] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/f35b6800af0c924bee570c31ca59b0a5d8bc960f [00:00:55] 02statichelp/03main 07WikiTideBot 03f35b680 Bot: Auto-update Tech namespace pages 2026-07-17 00:00:51 [00:16:26] miraheze/MirahezeMagic - dmehus the build passed. [00:29:32] miraheze/MirahezeMagic - dmehus the build passed. [04:26:08] !log [petramagna@test151] starting deploy of {'folders': '1.46/extensions/ConfirmEdit'} to test151 [04:26:09] !log [petramagna@test151] finished deploy of {'folders': '1.46/extensions/ConfirmEdit'} to test151 - SUCCESS in 0s [04:26:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [04:26:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [04:35:30] RECOVERY - test151 Puppet on test151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:51:00] [02mw-config] 0790gq29 commented on pull request #6465: @YTFGolf u right 13https://github.com/miraheze/mw-config/pull/6465#issuecomment-4999442924 [15:30:31] [02ssl] 07lihaohong6 opened pull request #923: T15283: automatically redirect wikis to custom domain (07miraheze:03main...07lihaohong6:03auto) 13https://github.com/miraheze/ssl/pull/923 [15:34:12] [02ssl] 07coderabbitai[bot] commented on pull request #923: [![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change- […] 13https://github.com/miraheze/ssl/pull/923#issuecomment-5004871987 [15:34:16] [02ssl] 07coderabbitai[bot] left a review on pull request #923: **Actionable comments posted: 1** […] 13https://github.com/miraheze/ssl/pull/923#pullrequestreview-4724027808 [15:34:16] [02ssl] 07coderabbitai[bot] left a file comment in pull request #923 0387c1ab7: _🗄️ Data Integrity & Integration_ | _🟠 Major_ | _🏗️ Heavy lift_ […] 13https://github.com/miraheze/ssl/pull/923#discussion_r3604331239 [19:52:38] [02landing] 07renovate[bot] created 03renovate/all-deps (+1 new commit) 13https://github.com/miraheze/landing/commit/e4aef0eeea44 [19:52:38] 02landing/03renovate/all-deps 07renovate[bot] 03e4aef0e Update dependency svgo to v4.0.2 [23:16:28] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:16:37] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 15 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw163 mw183 mw191 mw192 mw193 mw201 mw203 [23:16:46] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:16:47] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:17:00] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:17:07] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:17:08] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:17:13] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:17:13] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 11.77, 7.10, 4.05 [23:17:20] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 95% [23:17:22] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 15 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw183 mw191 mw192 mw193 mw203 [23:17:32] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 16 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw183 mw191 mw192 mw193 mw201 mw203 [23:17:32] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:17:45] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 16 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw183 mw191 mw192 mw193 mw201 mw203 [23:18:06] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:19:09] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.916 second response time [23:19:10] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:19:22] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:19:29] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:19:39] PROBLEM - swiftproxy171 Check unit status of swift_dispersion_stats on swiftproxy171 is CRITICAL: CRITICAL: Status of the systemd unit swift_dispersion_stats [23:20:03] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.068 second response time [23:20:28] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [23:20:36] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:20:37] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.015 second response time [23:20:38] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:20:44] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:21:11] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.257 second response time [23:21:22] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.075 second response time [23:21:26] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [23:21:45] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:22:25] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.185 second response time [23:22:35] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.226 second response time [23:22:36] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.227 second response time [23:22:37] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.181 second response time [23:22:40] 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 [23:22:53] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.849 second response time [23:23:12] PROBLEM - swiftproxy171 Check unit status of swift-container-stats_mw-media on swiftproxy171 is CRITICAL: CRITICAL: Status of the systemd unit swift-container-stats_mw-media [23:23:20] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 49% [23:23:32] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.315 second response time [23:23:45] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 3.532 second response time [23:24:07] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.013 second response time [23:25:06] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 6.239 second response time [23:25:16] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:26:14] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:26:14] wow! That’s entertaining! [23:26:37] https://klipy.com/gifs/ishowspeed-ishowspeed-yeah-right [23:27:10] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.202 second response time [23:27:16] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 3.442 second response time [23:27:20] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 62% [23:27:32] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:27:57] sybau [23:28:18] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 5.837 second response time [23:28:44] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [23:28:50] yeah MirahezeRelay is spitting some BARS 🔥🔥🔥🔥🔥 [23:28:59] https://klipy.com/gifs/bruh-bars [23:29:08] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.604 second response time [23:29:20] amazing jo- 💥 [23:29:20] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 49% [23:29:23] yall don’t know about this robot stuff 🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖 [23:29:27] SYBAU [23:29:28] getting bad gateway errors: [23:29:28] The web server reported a bad gateway error. [23:29:28] Ray ID: a1cd06606d64adab Your IP address: Error reference number: 502 Cloudflare Location: Vancouver [23:29:38] on metawiki [23:29:49] https://klipy.com/gifs/ouu-shi-shit [23:30:12] can't even verify lmao [23:30:16] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.202 second response time [23:30:33] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.073 second response time [23:30:37] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [23:30:46] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.261 second response time [23:30:48] RECOVERY - swiftproxy161 APT on swiftproxy161 is OK: APT OK: 111 packages available for upgrade (0 critical updates). [23:30:57] looks like I must've been hitting cp161 I guess [23:31:12] RECOVERY - swiftproxy171 Check unit status of swift-container-stats_mw-media on swiftproxy171 is OK: OK: Status of the systemd unit swift-container-stats_mw-media [23:31:20] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 1% [23:31:22] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [23:31:32] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [23:31:32] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.068 second response time [23:31:45] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [23:32:28] PROBLEM - swiftproxy161 HTTPS on swiftproxy161 is CRITICAL: connect to address 10.0.16.135 and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [23:33:13] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 0.72, 6.98, 7.50 [23:33:20] mhm [23:33:27] PROBLEM - swiftproxy161 Swift NGINX SSL check on swiftproxy161 is CRITICAL: connect to address localhost and port 443: Connection refused [23:33:49] PROBLEM - swift-lb.wikitide.net - LetsEncrypt on sslhost is CRITICAL: connect to address swift-lb.wikitide.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [23:34:02] boooo you should get muted! You’re spamming! [23:34:22] :moonch: [23:34:33] :moonch: [23:35:13] RECOVERY - swiftproxy161 Current Load on swiftproxy161 is OK: LOAD OK - total load average: 0.21, 4.71, 6.60 [23:35:28] RECOVERY - swiftproxy161 Swift NGINX SSL check on swiftproxy161 is OK: OK - Certificate 'wikitide.net' will expire on Tue Aug 18 00:55:21 2026 +0000.TCP OK - 0.033 second response time on localhost port 443 [23:36:15] RECOVERY - swiftproxy161 HTTPS on swiftproxy161 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.168 second response time [23:36:22] !log [void@swiftproxy161] restart nginx (OOM) [23:37:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:38:37] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 12 backends are down. mw151 mw152 mw161 mw172 mw181 mw182 mw163 mw183 mw192 mw193 mw201 mw203 [23:38:47] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:38:55] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:38:56] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:39:02] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:39:13] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 12.89, 9.69, 8.25 [23:39:22] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 4 backends are down. mw182 mw163 mw183 mw191 [23:39:32] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 6 backends are down. mw162 mw172 mw182 mw153 mw163 mw191 [23:39:45] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 6 backends are down. mw162 mw182 mw163 mw191 mw192 mw193 [23:40:47] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 4.659 second response time [23:42:37] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [23:42:49] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.222 second response time [23:43:02] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.260 second response time [23:43:09] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.223 second response time [23:43:22] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [23:43:32] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [23:43:45] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [23:52:37] RECOVERY - swift-lb.wikitide.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.net' will expire on Tue 18 Aug 2026 12:55:21 AM GMT +0000. [23:53:17] RECOVERY - swiftproxy171 Check unit status of swift_dispersion_stats on swiftproxy171 is OK: OK: Status of the systemd unit swift_dispersion_stats