[00:01:21] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/3aa5b3786624ccc3d70ffa5ac28bd446cee9aa3f [00:01:21] 02statichelp/03main 07WikiTideBot 033aa5b37 Bot: Auto-update Tech namespace pages 2025-11-07 00:01:19 [00:11:26] RECOVERY - cp171 Disk Space on cp171 is OK: DISK OK - free space: / 74039MiB (16% inode=99%); [00:12:50] RECOVERY - cp201 Disk Space on cp201 is OK: DISK OK - free space: / 73663MiB (16% inode=99%); [00:12:56] RECOVERY - cp191 Disk Space on cp191 is OK: DISK OK - free space: / 74407MiB (16% inode=99%); [00:14:43] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php Cargo:cargoRecreateData --wiki=100bangaiwiki --table Episode --replacement (END - exit=0) [00:14:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:15:05] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php Cargo:cargoRecreateData --wiki=100bangaiwiki --table Episodes --replacement (END - exit=256) [00:15:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:18] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/17e216fd48f04d40f63f65e916332582678adbe6 [00:25:18] 02ssl/03main 07WikiTideBot 0317e216f Bot: Auto-update domain lists [00:35:23] PROBLEM - mwtask181 Check unit status of mediawiki_job_generate-sitemap-index on mwtask181 is CRITICAL: CRITICAL: Status of the systemd unit mediawiki_job_generate-sitemap-index [01:19:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 11.17, 9.49, 5.16 [01:21:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 6.27, 8.28, 5.25 [01:50:15] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 13.57, 11.85, 8.69 [01:52:10] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 6.33, 9.77, 8.30 [02:17:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 8.97, 10.90, 8.51 [02:19:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 6.21, 9.15, 8.16 [03:12:53] PROBLEM - mw203 Current Load on mw203 is CRITICAL: LOAD CRITICAL - total load average: 28.24, 21.67, 16.47 [03:14:52] RECOVERY - mw203 Current Load on mw203 is OK: LOAD OK - total load average: 12.58, 18.39, 15.94 [04:08:47] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [04:16:47] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [05:51:54] [02mw-config] 07toosplatched commented on pull request #6160: updated! 13https://github.com/miraheze/mw-config/pull/6160#issuecomment-3500865206 [05:52:18] miraheze/mw-config - toosplatched the build passed. [05:53:34] miraheze/mw-config - toosplatched the build passed. [06:15:20] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/e1ad8144ba9acd21678b4349ecd8cca943c300d0 [06:15:20] 02ssl/03main 07WikiTideBot 03e1ad814 Bot: Auto-update domain lists [08:08:46] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 16.13, 11.74, 9.02 [08:10:41] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.77, 9.32, 8.45 [09:48:18] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:18] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:20] 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:48:22] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:48:26] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:28] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:48:28] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.013 second response time [09:48:29] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:32] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:34] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:38] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:47] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [09:48:50] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:52] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:55] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:55] 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:49:02] 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:49:04] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:04] 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:49:05] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:08] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [09:49:10] PROBLEM - db181 Current Load on db181 is CRITICAL: LOAD CRITICAL - total load average: 219.85, 105.78, 42.56 [09:49:19] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:49:20] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [09:49:20] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:20] critical jumpscare [09:49:22] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.013 second response time [09:49:24] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:26] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:49:35] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:40] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:49:42] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:49:44] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.013 second response time [09:49:45] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:46] PROBLEM - mw202 HTTPS on mw202 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 [09:49:46] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:49:47] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:49:52] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:55] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:49:58] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:50:05] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:50:08] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:51:05] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 71% [09:51:56] PROBLEM - db181 APT on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [09:52:22] PROBLEM - db181 MariaDB Connections on db181 is UNKNOWN: [09:52:57] PROBLEM - db181 MariaDB on db181 is UNKNOWN: [09:53:01] PROBLEM - db181 Puppet on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [09:53:05] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 1.408 second response time [09:53:06] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 4.436 second response time [09:53:08] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.188 second response time [09:53:09] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 4.454 second response time [09:53:09] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 4.170 second response time [09:53:20] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.107 second response time [09:53:22] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.190 second response time [09:53:23] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.024 second response time [09:53:24] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.068 second response time [09:53:25] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 6.283 second response time [09:53:26] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.237 second response time [09:53:35] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.092 second response time [09:53:36] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.055 second response time [09:53:38] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.169 second response time [09:53:38] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.205 second response time [09:53:39] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 3.284 second response time [09:53:44] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.180 second response time [09:53:45] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [09:53:46] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.179 second response time [09:53:56] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.079 second response time [09:53:57] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 5.233 second response time [09:53:58] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.057 second response time [09:54:05] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.064 second response time [09:54:08] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.070 second response time [09:54:14] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.052 second response time [09:54:14] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.183 second response time [09:54:14] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.060 second response time [09:54:18] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.215 second response time [09:54:22] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.069 second response time [09:54:28] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.207 second response time [09:54:28] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.264 second response time [09:54:29] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.059 second response time [09:54:32] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.055 second response time [09:54:34] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4328 bytes in 0.195 second response time [09:54:38] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.261 second response time [09:54:47] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.195 second response time [09:54:50] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [09:54:52] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.056 second response time [09:54:55] PROBLEM - db181 MariaDB on db181 is CRITICAL: Too many connections [09:54:55] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.071 second response time [09:54:56] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.696 second response time [09:55:05] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 33% [09:55:21] !log put c4/db181 into maintenance mode [09:55:21] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [09:55:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:55:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [09:55:48] !log [blankeclair@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 26s [09:55:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:07:11] RECOVERY - db181 Puppet on db181 is OK: OK: Puppet is currently enabled, last run 38 minutes ago with 0 failures [10:07:44] !log hit db181 with a slightly larger hammer (kill -9) as it was stuck restarting MySQL for unknown reasons ... [10:07:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:08:05] RECOVERY - db181 MariaDB Connections on db181 is OK: OK connection usage: 0.1%Current connections: 1 [10:08:33] RECOVERY - db181 MariaDB on db181 is OK: Uptime: 63 Threads: 2 Questions: 1412 Slow queries: 0 Opens: 530 Open tables: 524 Queries per second avg: 22.412 [10:08:41] RECOVERY - db181 APT on db181 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [10:09:39] !log put c4/db181 out of maintenance mode [10:09:40] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [10:09:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:09:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:10:02] !log [blankeclair@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 22s [10:10:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:01:44] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:01:44] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:01:48] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:01:52] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:01:52] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:01:55] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:01:58] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:01:58] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:05] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:08] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:11] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:11] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:11] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.026 second response time [11:02:14] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:02:19] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:02:22] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:22] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:02:23] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:26] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:02:28] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:02:28] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:02:29] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:32] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:34] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:38] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:47] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:02:52] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:55] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:02:55] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.015 second response time [11:03:00] PROBLEM - mw172 HTTPS on mw172 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 [11:03:02] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:03:04] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:03:04] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:03:05] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:03:05] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 69% [11:03:08] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:03:24] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:03:26] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:03:27] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:03:32] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:03:36] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:04:57] PROBLEM - db181 MariaDB on db181 is UNKNOWN: [11:05:01] PROBLEM - db181 Puppet on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [11:05:55] PROBLEM - db181 APT on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [11:06:22] PROBLEM - db181 MariaDB Connections on db181 is UNKNOWN: [11:06:32] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 4.068 second response time [11:06:33] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 3.682 second response time [11:06:34] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 2.332 second response time [11:06:34] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 6.273 second response time [11:06:34] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4328 bytes in 0.712 second response time [11:06:42] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 4.558 second response time [11:06:47] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.212 second response time [11:06:53] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.056 second response time [11:06:55] PROBLEM - db181 MariaDB on db181 is CRITICAL: Too many connections [11:06:56] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.658 second response time [11:06:56] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 4.918 second response time [11:06:58] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 3.244 second response time [11:07:02] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.198 second response time [11:07:04] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [11:07:05] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 57% [11:07:05] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.799 second response time [11:07:05] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.627 second response time [11:07:12] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 3.856 second response time [11:07:24] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.064 second response time [11:07:26] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.189 second response time [11:07:26] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.181 second response time [11:07:32] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.215 second response time [11:07:36] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.069 second response time [11:07:38] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.182 second response time [11:07:44] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.205 second response time [11:07:45] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.059 second response time [11:07:47] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.202 second response time [11:07:52] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.124 second response time [11:07:56] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.914 second response time [11:07:56] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.066 second response time [11:07:59] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.058 second response time [11:07:59] !log put c4/db181 into maintenance mode, again [11:08:00] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [11:08:03] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.319 second response time [11:08:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:08:05] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.126 second response time [11:08:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:08:08] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.066 second response time [11:08:11] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.237 second response time [11:08:11] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.059 second response time [11:08:11] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.170 second response time [11:08:12] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.209 second response time [11:08:14] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [11:08:20] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.293 second response time [11:08:21] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.309 second response time [11:08:22] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.078 second response time [11:08:24] !log [blankeclair@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 24s [11:08:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:08:47] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [11:09:05] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 63% [11:10:24] [02statichelp] 07anpang54 opened pull request #1: You misspelled "documentation" (07miraheze:03main...07anpang54:03patch-1) 13https://github.com/miraheze/statichelp/pull/1 [11:10:35] [02statichelp] 07coderabbitai[bot] commented on pull request #1:

[…] 13https://github.com/miraheze/statichelp/pull/1#issuecomment-3501926982 [11:11:05] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 21% [11:16:47] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [11:17:20] PROBLEM - db181 PowerDNS Recursor on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:18:25] PROBLEM - db181 SSH on db181 is CRITICAL: connect to address 10.0.18.102 and port 22: Connection refused [11:18:46] PROBLEM - db181 Disk Space on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:19:01] PROBLEM - db181 ferm_active on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:19:46] PROBLEM - db181 Check unit status of sql-backup on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:20:06] PROBLEM - db181 NTP time on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:20:13] PROBLEM - db181 conntrack_table_size on db181 is CRITICAL: connect to address 10.0.18.102 port 5666: Connection refusedconnect to host 10.0.18.102 port 5666: Connection refused [11:36:56] RECOVERY - db181 PowerDNS Recursor on db181 is OK: DNS OK: 0.429 seconds response time. db181.fsslc.wtnet returns 10.0.18.102 [11:36:56] RECOVERY - db181 ferm_active on db181 is OK: OK ferm input default policy is set [11:37:09] RECOVERY - db181 Current Load on db181 is OK: LOAD OK - total load average: 0.66, 0.16, 0.05 [11:37:41] RECOVERY - db181 Check unit status of sql-backup on db181 is OK: OK: Status of the systemd unit sql-backup [11:37:47] RECOVERY - db181 MariaDB Connections on db181 is OK: OK connection usage: 0.2%Current connections: 2 [11:38:01] RECOVERY - db181 NTP time on db181 is OK: NTP OK: Offset -4.196166992e-05 secs [11:38:02] RECOVERY - db181 conntrack_table_size on db181 is OK: OK: nf_conntrack is 0 % full [11:38:03] RECOVERY - db181 Puppet on db181 is OK: OK: Puppet is currently enabled, last run 39 minutes ago with 0 failures [11:38:03] RECOVERY - db181 MariaDB on db181 is OK: Uptime: 70 Threads: 1 Questions: 2794 Slow queries: 0 Opens: 2231 Open tables: 2225 Queries per second avg: 39.914 [11:38:25] RECOVERY - db181 SSH on db181 is OK: SSH OK - OpenSSH_9.2p1 Debian-2+deb12u7 (protocol 2.0) [11:38:31] RECOVERY - db181 APT on db181 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [11:38:48] RECOVERY - db181 Disk Space on db181 is OK: DISK OK - free space: / 438698MiB (49% inode=97%); [11:43:09] !log put c4/db181 out of maintenance mode, again [11:43:10] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [11:43:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:43:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:43:33] !log [blankeclair@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 22s [11:43:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:11:41] !log [somerandomdeveloper@test151] starting deploy of {'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 [13:11:43] !log [somerandomdeveloper@test151] finished deploy of {'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 - SUCCESS in 2s [13:11:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:11:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:12:28] !log [somerandomdeveloper@test151] starting deploy of {'l10n': True, 'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 [13:12:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:12:50] PROBLEM - cp201 Disk Space on cp201 is WARNING: DISK WARNING - free space: / 49787MiB (10% inode=99%); [13:18:27] [02mw-config] 07SomeMWDev created 03T14328 (+1 new commit) 13https://github.com/miraheze/mw-config/commit/1d9742fffd5e [13:18:27] 02mw-config/03T14328 07SomeRandomDeveloper 031d9742f T14328: Allow enabling CommentStreams on talk namespaces… [13:19:48] [02mw-config] 07SomeMWDev opened pull request #6163: T14328: Allow enabling CommentStreams on talk namespaces (03main...03T14328) 13https://github.com/miraheze/mw-config/pull/6163 [13:20:41] miraheze/mw-config - SomeMWDev the build passed. [13:22:57] !log [somerandomdeveloper@test151] finished deploy of {'l10n': True, 'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 - SUCCESS in 628s [13:23:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:25:26] !log [somerandomdeveloper@mwtask181] starting deploy of {'l10n': True, 'versions': '1.44', 'upgrade_extensions': 'CommentStreams'} to all [13:25:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:33:56] !log [somerandomdeveloper@mwtask181] finished deploy of {'l10n': True, 'versions': '1.44', 'upgrade_extensions': 'CommentStreams'} to all - SUCCESS in 510s [13:34:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:39:24] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [13:39:25] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [13:39:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:40:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:41:32] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=glumforgewiki --new=helldevwiki --user=Skye (END - exit=0) [13:41:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:41:43] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 23.64, 15.40, 9.51 [13:42:41] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=helldevwiki (END - exit=0) [13:42:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:44:56] PROBLEM - cp191 Disk Space on cp191 is WARNING: DISK WARNING - free space: / 49859MiB (10% inode=99%); [13:45:23] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/fc85e05860171fe4d7bbf86c0a0ad910cd304e68 [13:45:23] 02ssl/03main 07WikiTideBot 03fc85e05 Bot: Auto-update domain lists [13:45:35] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=snxyzincubatorwiki --new=snxyzmetawiki --user=Skye (END - exit=0) [13:45:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:47:26] PROBLEM - cp171 Disk Space on cp171 is WARNING: DISK WARNING - free space: / 49827MiB (10% inode=99%); [13:47:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 6.14, 11.98, 10.00 [13:49:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.68, 9.90, 9.48 [13:51:01] [02mw-config] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/a60b12684640049369d06be1debdd5712817383b [13:51:03] 02mw-config/03main 07SomeRandomDeveloper 03a60b126 T14328: Allow enabling CommentStreams on talk namespaces (#6163)… [13:51:05] [02mw-config] 07SomeMWDev merged pull request #6163: T14328: Allow enabling CommentStreams on talk namespaces (03main...03T14328) 13https://github.com/miraheze/mw-config/pull/6163 [13:51:07] [02mw-config] 07SomeMWDev 04deleted 03T14328 at 031d9742f 13https://api.github.com/repos/miraheze/mw-config/commit/1d9742f [13:51:16] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [13:51:17] !log [somerandomdeveloper@test151] DEPLOY ABORTED: Non-Zero Exit Code in prep, see output. [13:51:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:51:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:51:30] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [13:51:31] !log [somerandomdeveloper@test151] finished deploy of {'pull': 'config', 'config': True} to test151 - SUCCESS in 0s [13:51:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:51:37] !log [somerandomdeveloper@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [13:51:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:51:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:51:59] miraheze/mw-config - SomeMWDev the build passed. [13:52:01] !log [somerandomdeveloper@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 24s [13:52:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:53:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 9.30, 11.11, 10.17 [13:54:43] !log [somerandomdeveloper@test151] starting deploy of {'l10n': True, 'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 [13:54:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:54:48] !log [somerandomdeveloper@mwtask181] starting deploy of {'l10n': True, 'versions': '1.44', 'upgrade_extensions': 'CommentStreams'} to all [13:54:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:55:43] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 15.61, 14.13, 11.47 [13:57:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 5.64, 10.92, 10.62 [13:59:05] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=snxyzmetawiki (END - exit=0) [13:59:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:59:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.26, 8.99, 9.95 [14:01:38] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:ResetWiki --wiki=loginwiki --dbname=snxyzmetawiki --requester=Pisces (END - exit=0) [14:01:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:03:53] !log [somerandomdeveloper@mwtask181] finished deploy of {'l10n': True, 'versions': '1.44', 'upgrade_extensions': 'CommentStreams'} to all - SUCCESS in 545s [14:03:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:05:08] !log [somerandomdeveloper@test151] finished deploy of {'l10n': True, 'versions': ['1.44', '1.45'], 'upgrade_extensions': 'CommentStreams'} to test151 - SUCCESS in 625s [14:05:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:05:21] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/41039c56e3f2ae48ccc8dba6f710e78cd0c6e772 [14:05:21] 02ssl/03main 07WikiTideBot 0341039c5 Bot: Auto-update domain lists [14:21:07] !log [somerandomdeveloper@test151] starting deploy of {'config': True} to test151 [14:21:08] !log [somerandomdeveloper@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [14:21:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:21:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:25:17] [02mw-config] 07SomeMWDev approved pull request #6160 13https://github.com/miraheze/mw-config/pull/6160#pullrequestreview-3434272184 [14:25:53] [02mw-config] 07SomeMWDev merged 07toosplatched's pull request #6160: T14450: Add $wgLakeusWikiDefaultColorScheme (07miraheze:03main...07toosplatched:03T14450) 13https://github.com/miraheze/mw-config/pull/6160 [14:25:55] [02mw-config] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/571719e022b8ca2d4d9ccb97ed741f7aaad342d2 [14:25:56] 02mw-config/03main 07stackd 03571719e T14450: Add $wgLakeusWikiDefaultColorScheme to ManageWiki (#6160)… [14:26:39] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [14:26:40] !log [somerandomdeveloper@test151] finished deploy of {'pull': 'config', 'config': True} to test151 - SUCCESS in 0s [14:26:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:26:44] !log [somerandomdeveloper@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [14:26:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:26:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:26:52] miraheze/mw-config - SomeMWDev the build passed. [14:27:08] !log [somerandomdeveloper@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 23s [14:27:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:10:35] [02mw-config] 07originalcloudcrafter opened pull request #6164: Add lawcommonswiki and lawpediawiki to GlobalUsage settings (07miraheze:03main...07originalcloudcrafter:03patch-1) 13https://github.com/miraheze/mw-config/pull/6164 [15:15:53] miraheze/mw-config - originalcloudcrafter the build passed. [16:19:07] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 18.83, 12.02, 9.12 [16:21:02] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.14, 9.27, 8.46 [16:41:26] [02mw-config] 07pixDeVl opened pull request #6165: Update wiki creator to wiki reviewer in canned CW messages (07miraheze:03main...07pixDeVl:03patch-3) 13https://github.com/miraheze/mw-config/pull/6165 [16:42:18] miraheze/mw-config - pixDeVl the build passed. [16:42:42] [02statichelp] 07RhinosF1 merged 07anpang54's pull request #1: You misspelled "documentation" (07miraheze:03main...07anpang54:03patch-1) 13https://github.com/miraheze/statichelp/pull/1 [16:42:43] [02statichelp] 07RhinosF1 pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/0cef4efa41ce6e463000c194b57d7fda37b7aa83 [16:42:44] 02statichelp/03main 07Anpang 030cef4ef you misspelled documentation (#1) [17:21:25] `Lỗi không rõ xuất hiện trong phía sau lưu trữ “miraheze-swift”.` [17:22:11] Lemme guess, we have forgot a script while moving my db to `snxyzmetawiki`... [18:32:39] PROBLEM - mw181 Current Load on mw181 is WARNING: LOAD WARNING - total load average: 20.56, 18.14, 14.97 [18:34:39] RECOVERY - mw181 Current Load on mw181 is OK: LOAD OK - total load average: 12.95, 16.30, 14.69 [18:39:28] [02mw-config] 07pskyechology approved pull request #6165 13https://github.com/miraheze/mw-config/pull/6165#pullrequestreview-3435696446 [18:39:39] [02mw-config] 07pskyechology merged 07pixDeVl's pull request #6165: Update wiki creator to wiki reviewer in canned CW messages (07miraheze:03main...07pixDeVl:03patch-3) 13https://github.com/miraheze/mw-config/pull/6165 [18:39:40] [02mw-config] 07pskyechology pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/1645769ca4043068e9d92a9dffe012c8169a148e [18:39:40] 02mw-config/03main 07PixDeVl 031645769 Update wiki creator to wiki reviewer in canned CW messages (#6165)… [18:40:22] !log [skye@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [18:40:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:40:47] miraheze/mw-config - pskyechology the build passed. [18:40:48] !log [skye@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 26s [18:40:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:09:43] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 11.05, 10.88, 7.91 [19:11:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 5.20, 9.02, 7.62 [19:18:25] [02mw-config] 07songnguxyz opened pull request #6166: --body (07miraheze:03main...07songnguxyz:03setupfootericonsnxyz) 13https://github.com/miraheze/mw-config/pull/6166 [19:18:47] [02mw-config] 07songnguxyz retitled PR #6166: "--body" ➜ "Setting up footer icons for snxyzmetawiki" 13https://github.com/miraheze/mw-config/pull/6166 [19:19:18] miraheze/mw-config - songnguxyz the build passed. [19:23:43] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 11.06, 12.27, 9.39 [19:25:43] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 4.12, 9.52, 8.75 [19:28:47] db171.... pls no,,,,, [19:32:52] PROBLEM - mw151 Puppet on mw151 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_femiwiki-deploy-1.44] [19:35:21] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/4647bbc485ad2599c7ef2e65a8c54367be8b7b55 [19:35:21] 02ssl/03main 07WikiTideBot 034647bbc Bot: Auto-update domain lists [19:37:00] [02mw-config] 07SomeMWDev created 03T14475 (+1 new commit) 13https://github.com/miraheze/mw-config/commit/2f85a25d282a [19:37:00] 02mw-config/03T14475 07SomeRandomDeveloper 032f85a25 T14475: Add two Monaco settings to ManageWiki [19:38:02] [02mw-config] 07SomeMWDev opened pull request #6167: T14475: Add two Monaco settings to ManageWiki (03main...03T14475) 13https://github.com/miraheze/mw-config/pull/6167 [19:38:58]