[00:01:11] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/38e1273f12c39229847dadc15301353aa9a8a092 [00:01:11] 02statichelp/03main 07WikiTideBot 0338e1273 Bot: Auto-update Tech namespace pages 2025-08-17 00:01:08 [00:06:07] RECOVERY - cp171 Disk Space on cp171 is OK: DISK OK - free space: / 57384MiB (12% inode=99%); [00:06:49] RECOVERY - cp191 Disk Space on cp191 is OK: DISK OK - free space: / 57941MiB (12% inode=99%); [00:07:06] RECOVERY - cp201 Disk Space on cp201 is OK: DISK OK - free space: / 57052MiB (12% inode=99%); [00:30:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 42% [00:32:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 37% [03:04:47] PROBLEM - puppet181 Disk Space on puppet181 is WARNING: DISK WARNING - free space: / 2328MiB (7% inode=81%); [03:06:48] RECOVERY - puppet181 Disk Space on puppet181 is OK: DISK OK - free space: / 4398MiB (14% inode=81%); [04:24:59] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 17.21, 10.47, 4.69 [04:26:58] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 3.39, 7.48, 4.30 [05:47:53] [Grafana] FIRING: The estimated time for the MediaWiki JobQueue to clear is excessively high (8 hours) for an extended time period https://grafana.wikitide.net/d/GtxbP1Xnk?from=1755406040000&orgId=1&to=1755409673356 [05:52:53] [Grafana] RESOLVED: MediaWiki JobQueue is stalled https://grafana.wikitide.net/d/GtxbP1Xnk?from=1755406220000&orgId=1&to=1755409820000 [06:08:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 45% [06:10:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 28% [07:17:53] [Grafana] FIRING: The estimated time for the MediaWiki JobQueue to clear is excessively high (8 hours) for an extended time period https://grafana.wikitide.net/d/GtxbP1Xnk?from=1755411440000&orgId=1&to=1755415073359 [07:22:53] [Grafana] RESOLVED: MediaWiki JobQueue is stalled https://grafana.wikitide.net/d/GtxbP1Xnk?from=1755411680000&orgId=1&to=1755415280000 [08:12:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 52% [08:14:54] !log MediaWiki\Extension\CentralAuth\User\CentralAuthUser::getInstance( User::newFromName( 'Janwexel' ) )->attach( 'osterholtwiki', 'admin' ); [08:14:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 31% [08:14:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:17:57] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:03] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:07] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:18:09] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:13] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [09:18:14] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:15] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:15] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:16] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:18:17] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:18:24] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:25] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:25] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:18:31] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:35] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:18:38] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:18:41] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:18:42] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 206.64, 97.15, 38.56 [09:18:48] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [09:18:56] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.020 second response time [09:18:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 81% [09:18:56] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:19:00] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:19:02] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [09:19:03] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:19:03] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:19:04] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:19:09] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:19:19] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [09:19:27] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:29] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:32] 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 10000 milliseconds with 0 bytes received [09:19:35] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [09:19:35] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:37] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:39] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [09:19:41] PROBLEM - mw173 HTTPS on mw173 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 [09:19:42] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:42] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [09:19:44] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:45] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19:45] 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 10004 milliseconds with 0 bytes received [09:19:49] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:19: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 10004 milliseconds with 0 bytes received [09:19:57] 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 10000 milliseconds with 0 bytes received [09:20:07] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [09:21:24] PROBLEM - db161 APT on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [09:22:10] PROBLEM - db161 Puppet on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [09:22:31] PROBLEM - db161 MariaDB Connections on db161 is UNKNOWN: [09:22:39] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 9.895 second response time [09:22:44] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 8.955 second response time [09:22:44] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.352 second response time [09:22:46] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.689 second response time [09:22:50] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.187 second response time [09:22:58] PROBLEM - db161 MariaDB on db161 is UNKNOWN: [09:23:01] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.196 second response time [09:23:02] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.070 second response time [09:23:04] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [09:23:06] PROBLEM - cp201 Disk Space on cp201 is WARNING: DISK WARNING - free space: / 49745MiB (10% inode=99%); [09:23:09] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.072 second response time [09:23:10] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.218 second response time [09:23:12] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.080 second response time [09:23:16] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.195 second response time [09:23:19] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4216 bytes in 0.078 second response time [09:23:28] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.183 second response time [09:23:35] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [09:23:36] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.189 second response time [09:23:36] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.179 second response time [09:23:36] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.068 second response time [09:23:39] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [09:23:40] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.062 second response time [09:23:42] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.280 second response time [09:23:42] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.178 second response time [09:23:43] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.183 second response time [09:23:51] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.180 second response time [09:23:53] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 4371 bytes in 0.179 second response time [09:23:53] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.173 second response time [09:23:54] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.071 second response time [09:23:59] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.064 second response time [09:24:01] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.085 second response time [09:24:03] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.072 second response time [09:24:07] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [09:24:10] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.062 second response time [09:24:13] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [09:24:17] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.177 second response time [09:24:22] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.071 second response time [09:24:24] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.061 second response time [09:24:25] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [09:24:27] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.073 second response time [09:24:27] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.063 second response time [09:24:31] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.060 second response time [09:24:33] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.191 second response time [09:24:33] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.076 second response time [09:24:48] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.063 second response time [09:24:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 51% [09:24:56] PROBLEM - db161 MariaDB on db161 is CRITICAL: Too many connections [09:25:02] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.065 second response time [09:30:07] PROBLEM - cp171 Disk Space on cp171 is WARNING: DISK WARNING - free space: / 49824MiB (10% inode=99%); [09:40:49] PROBLEM - cp191 Disk Space on cp191 is WARNING: DISK WARNING - free space: / 49857MiB (10% inode=99%); [09:50:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 21% [09:52:21] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [09:52:23] !log [blankeclair@mwtask181] DEPLOY ABORTED: Canary check failed for publictestwiki.com@localhost [09:52:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:52:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:52:31] !log [blankeclair@mwtask181] starting deploy of {'config': True, 'force': True} to all [09:52:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:52:38] !log put c2 (db161) into maintenance [09:52:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:52:57] !log [blankeclair@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 25s [09:53:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:56:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 54% [10:15:02] PROBLEM - db161 Puppet on db161 is WARNING: WARNING: Puppet last ran 1 hour ago [10:15:53] hmm i wonder why [10:15:58] RECOVERY - db161 MariaDB on db161 is OK: Uptime: 34 Threads: 2 Questions: 1510 Slow queries: 0 Opens: 280 Open tables: 274 Queries per second avg: 44.411 [10:16:36] !log [blankeclair@mwtask181] starting deploy of {'config': True, 'force': True} to all [10:16:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:16:44] !log put c2 (db161) out of maintenane [10:16:45] !log kill mysql because it was being dumb and I don't have time to debug why [10:16:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:16:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:16:59] RECOVERY - db161 APT on db161 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [10:16:59] !log [blankeclair@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 22s [10:17:01] RECOVERY - db161 Puppet on db161 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [10:17:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:17:31] RECOVERY - db161 MariaDB Connections on db161 is OK: OK connection usage: 1.9%Current connections: 19 [10:18:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 22% [10:27:55] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [10:27:59] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:28:03] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:28:04] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:28:07] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:28:13] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:28:51] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [10:29:02] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [10:29:04] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:05] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:06] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:07] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:09] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [10:29:13] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:19] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:24] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [10:29:24] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [10:29:26] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:26] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:32] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.017 second response time [10:29:33] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [10:29:35] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [10:29:35] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:36] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:36] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [10:29:39] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [10:29:42] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [10:29:42] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [10:30:08] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [10:30:13] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:18] PROBLEM - mw181 HTTPS on mw181 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 [10:30:18] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:19] PROBLEM - mw152 HTTPS on mw152 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 [10:30:20] 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 10003 milliseconds with 0 bytes received [10:30:26] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:34] 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 10001 milliseconds with 0 bytes received [10:30:34] 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 10004 milliseconds with 0 bytes received [10:30:35] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:43] PROBLEM - mw151 HTTPS on mw151 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 [10:30:45] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10002 milliseconds with 0 bytes received [10:30:46] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:48] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:49] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:51] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:30:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 78% [10:31:55] PROBLEM - db161 APT on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [10:32:31] PROBLEM - db161 MariaDB Connections on db161 is UNKNOWN: [10:32:58] PROBLEM - db161 MariaDB on db161 is UNKNOWN: [10:33:36] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.240 second response time [10:33:39] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 7.305 second response time [10:33:39] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.868 second response time [10:33:43] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 8.642 second response time [10:33:43] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.195 second response time [10:33:44] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.188 second response time [10:33:45] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.063 second response time [10:33:47] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.178 second response time [10:33:58] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.062 second response time [10:34:07] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.068 second response time [10:34:08] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.086 second response time [10:34:10] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.067 second response time [10:34:17] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.180 second response time [10:34:19] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.070 second response time [10:34:20] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.055 second response time [10:34:21] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.198 second response time [10:34:24] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.065 second response time [10:34:24] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.076 second response time [10:34:31] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.072 second response time [10:34:33] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.168 second response time [10:34:33] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.057 second response time [10:34:34] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.192 second response time [10:34:44] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.062 second response time [10:34:45] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.067 second response time [10:34:48] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.087 second response time [10:34:50] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.174 second response time [10:34:52] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.167 second response time [10:34:53] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.186 second response time [10:34:55] PROBLEM - db161 MariaDB on db161 is CRITICAL: Too many connections [10:34:56] PROBLEM - db161 Puppet on db161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [10:34:59] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.217 second response time [10:35:02] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.069 second response time [10:35:08] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.189 second response time [10:35:09] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.198 second response time [10:35:13] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.064 second response time [10:35:16] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.072 second response time [10:35:17] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.211 second response time [10:35:18] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [10:35:19] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4216 bytes in 0.077 second response time [10:35:24] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.194 second response time [10:35:28] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.166 second response time [10:35:32] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4112 bytes in 0.074 second response time [10:35:35] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [10:35:40] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [10:35:42] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4161 bytes in 0.069 second response time [10:36:07] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [10:36:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 52% [10:45:52] !log [blankeclair@mwtask181] starting deploy of {'config': True, 'force': True} to all [10:45:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:45:59] !log put c2 (db161) back into maintenance where it belongs [10:46:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:46:15] !log [blankeclair@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 23s [10:46:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:46:38] RECOVERY - db161 Puppet on db161 is OK: OK: Puppet is currently enabled, last run 29 minutes ago with 0 failures [10:46:39] RECOVERY - db161 APT on db161 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [10:47:49] RECOVERY - db161 MariaDB Connections on db161 is OK: OK connection usage: 0.2%Current connections: 2 [10:48:39] RECOVERY - db161 MariaDB on db161 is OK: Uptime: 114 Threads: 9 Questions: 14502 Slow queries: 0 Opens: 1691 Open tables: 1685 Queries per second avg: 127.210 [10:52:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 60% [10:54:56] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 58% [10:59:25] !log [blankeclair@mwtask181] starting deploy of {'config': True, 'force': True} to all [10:59:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:59:31] !log unmaint c2 [10:59:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:59:47] !log [blankeclair@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 22s [10:59:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:02:56] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 32% [11:11:47] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php ManageWiki:PopulateNamespaces --wiki=morerandomstuffwikibeta (END - exit=65280) [11:11:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:12:31] `Fatal error: Uncaught Error: Class "WikiMap" not found in /srv/mediawiki/1.44/extensions/SemanticMediaWiki/includes/GlobalFunctions.php:165` [11:12:33] wasn't SMW fixed? [11:13:18] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php ManageWiki:PopulateNamespaces --wiki=morerandomstuffwikibeta (END - exit=256) [11:13:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:13:36] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php ManageWiki:PopulateNamespaces --wiki=morerandomstuffwikibeta --force (END - exit=0) [11:13:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:13:55] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php ManageWiki:PopulateNamespaces --wiki=randomstuffwikibeta --force (END - exit=0) [11:13:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:21:07] [02mw-config] 07SomeMWDev created 03userfunctions-namespaces (+1 new commit) 13https://github.com/miraheze/mw-config/commit/fb2d48fef1ce [11:21:07] 02mw-config/03userfunctions-namespaces 07SomeRandomDeveloper 03fb2d48f Use associative array for $wgUFAllowedNamespaces… [11:22:37] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [11:22:38] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [11:22:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:22:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:25:40] [02mw-config] 07SomeMWDev pushed 2 new commits to 03userfunctions-namespaces 13https://github.com/miraheze/mw-config/compare/fb2d48fef1ce...4e174a9668d0 [11:25:40] 02mw-config/03userfunctions-namespaces 07SomeRandomDeveloper 0345bd2d2 Fix default value [11:25:42] 02mw-config/03userfunctions-namespaces 07SomeRandomDeveloper 034e174a9 Use int instead of string [11:26:05] did we upgrade lol [11:26:09] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [11:26:10] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [11:26:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:26:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:26:56] apparently we did [11:26:57] [GitHub] [miraheze/mediawiki-repos] composer.local.json @ main | L3: "mediawiki/semantic-media-wiki": "6.x-dev", [11:27:25] [1/2] What is this thing [11:27:26] [2/2] And why does he speak in runes [11:28:03] logging the deployment of mediawiki configuration changes [11:28:53] Sounds important :3 [11:29:37] [1/7] ```php [11:29:37] [2/7] > $wgUFAllowedNamespaces; [11:29:38] [3/7] = [ [11:29:38] [4/7] true, [11:29:38] [5/7] ] [11:29:39] [6/7] ``` [11:29:39] [7/7] that is not supposed to happen [11:35:23] [02mw-config] 07SomeMWDev pushed 1 new commit to 03userfunctions-namespaces 13https://github.com/miraheze/mw-config/commit/35ba7000cc320eb23844cd16eef7ae7fa281560f [11:35:23] 02mw-config/03userfunctions-namespaces 07SomeRandomDeveloper 0335ba700 Use NS_MEDIAWIKI constant [11:35:52] lmfao that's even better [11:36:04] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [11:36:05] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [11:36:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:36:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:36:14] it fixed itself for some reason [11:36:36] ?? mediawiki magic [11:36:56] miraheze magic [11:37:15] [02mw-config] 07SomeMWDev opened pull request #6062: Use associative array for $wgUFAllowedNamespaces (03main...03userfunctions-namespaces) 13https://github.com/miraheze/mw-config/pull/6062 [11:37:44] [02mw-config] 07github-actions[bot] pushed 1 new commit to 03userfunctions-namespaces 13https://github.com/miraheze/mw-config/commit/bd5922b8beab15c55baebbd5e0ff5a614a4d29d7 [11:37:44] 02mw-config/03userfunctions-namespaces 07github-actions 03bd5922b CI: lint code to MediaWiki standards… [11:38:13] miraheze/mw-config - SomeMWDev the build passed. [11:39:50] [02mw-config] 07SomeMWDev merged pull request #6062: Use associative array for $wgUFAllowedNamespaces (03main...03userfunctions-namespaces) 13https://github.com/miraheze/mw-config/pull/6062 [11:39:50] [02mw-config] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/27ccc4317f44a07d23a560d339ebac28e509f823 [11:39:52] 02mw-config/03main 07SomeRandomDeveloper 0327ccc43 Use associative array for $wgUFAllowedNamespaces (#6062)… [11:39:54] [02mw-config] 07SomeMWDev 04deleted 03userfunctions-namespaces at 03bd5922b 13https://api.github.com/repos/miraheze/mw-config/commit/bd5922b [11:40:23] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [11:40:24] !log [somerandomdeveloper@test151] finished deploy of {'pull': 'config', 'config': True} to test151 - SUCCESS in 0s [11:40:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:40:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:40:46] miraheze/mw-config - SomeMWDev the build passed. [11:40:58] !log [somerandomdeveloper@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [11:41:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:41:22] !log [somerandomdeveloper@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 24s [11:41:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:45:41] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 1.14, 1.22, 11.50 [11:46:07] uh oh [11:46:10] please don't [11:47:13] oh that's the 15m load average [11:47:17] that's probably fine then [11:49:36] [1/2] I DIDN'T HEAR NO BELL! [11:49:36] [2/2] -db161, probably [11:49:39] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 1.05, 1.17, 9.14 [11:54:04] [02mw-config] 07SomeMWDev 04force-pushed 03cleanup-requirements from 03a798df8 to 03531afa9 13https://api.github.com/repos/miraheze/mw-config/commits/cleanup-requirements [11:54:04] 02mw-config/03cleanup-requirements 07SomeRandomDeveloper 03531afa9 Clean up redundant settings requirements… [11:54:59] miraheze/mw-config - SomeMWDev the build passed. [11:55:22] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [11:55:23] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [11:55:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:55:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:57:33] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [11:57:34] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [11:57:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:57:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:58:12] gonna (finally) merge this later today when I have time to test it again [16:13:24] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 16.02, 12.80, 6.87 [16:21:22] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 11.34, 11.91, 9.34 [16:23:22] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 17.91, 15.27, 10.97 [16:35:19] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 10.85, 10.99, 11.83 [16:41:18] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 0.93, 5.41, 9.38 [17:23:11] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 85.28, 36.68, 15.16 [17:31:09] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 1.67, 9.76, 10.68 [17:33:09] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 0.81, 6.76, 9.46 [18:24:53] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [18:24:54] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [18:24:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:25:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:28:29] [02mw-config] 07SomeMWDev readied pull request #5992: Clean up redundant settings requirements (03main...03cleanup-requirements) 13https://github.com/miraheze/mw-config/pull/5992 [18:29:12] [02mw-config] 07SomeMWDev merged pull request #5992: Clean up redundant settings requirements (03main...03cleanup-requirements) 13https://github.com/miraheze/mw-config/pull/5992 [18:29:14] [02mw-config] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/47932dbc7b64af4b4698c78524ae2e55ac346f85 [18:29:16] [02mw-config] 07SomeMWDev 04deleted 03cleanup-requirements at 03531afa9 13https://api.github.com/repos/miraheze/mw-config/commit/531afa9 [18:29:17]