[00:01:02] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/e6ae1560b9f7a97f4b655b670114b614bca39a4d [00:01:02] 02statichelp/03main 07WikiTideBot 03e6ae156 Bot: Auto-update Tech namespace pages 2026-05-15 00:00:59 [03:03:26] PROBLEM - puppet181 Check unit status of git_pull_ssl on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit git_pull_ssl [03:07:38] PROBLEM - mwtask181 Puppet on mwtask181 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_femiwiki-deploy-1.45] [03:09:26] RECOVERY - puppet181 Check unit status of git_pull_ssl on puppet181 is OK: OK: Status of the systemd unit git_pull_ssl [03:33:38] RECOVERY - mwtask181 Puppet on mwtask181 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:37:01] PROBLEM - bast181 Current Load on bast181 is CRITICAL: LOAD CRITICAL - total load average: 4.91, 3.84, 1.72 [05:38:57] RECOVERY - bast181 Current Load on bast181 is OK: LOAD OK - total load average: 0.75, 2.62, 1.52 [05:39:20] PROBLEM - mw182 Puppet on mw182 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 2 minutes ago with 2 failures. Failed resources (up to 3 shown): Exec[git_pull_femiwiki-deploy-1.45],Exec[git_pull_3d2png] [05:39:37] PROBLEM - mw183 Puppet on mw183 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): Exec[git_pull_femiwiki-deploy-1.45],Exec[git_pull_3d2png] [06:05:20] RECOVERY - mw182 Puppet on mw182 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [06:05:34] RECOVERY - mw183 Puppet on mw183 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [08:32:10] [02TSPortal] 07renovate[bot] created 03renovate/dev-deps (+1 new commit) 13https://github.com/miraheze/TSPortal/commit/c5a422a1b353 [08:32:10] 02TSPortal/03renovate/dev-deps 07renovate[bot] 03c5a422a Update dependency phpunit/phpunit to v13.1.10 [09:31:13] [02WikiDiscover] 07Reception123 created 03Reception123-patch-2 (+1 new commit) 13https://github.com/miraheze/WikiDiscover/commit/149bff745846 [09:31:13] 02WikiDiscover/03Reception123-patch-2 07Reception123 03149bff7 Create Special:InactivityExemptWikis page (T10674) [09:32:41] [02WikiDiscover] 07Reception123 04deleted 03Reception123-patch-2 at 03149bff7 13https://api.github.com/repos/miraheze/WikiDiscover/commit/149bff7 [09:37:53] [02WikiDiscover] 07Reception123 created 03Reception123-patch-2 (+1 new commit) 13https://github.com/miraheze/WikiDiscover/commit/5627c4064105 [09:37:53] 02WikiDiscover/03Reception123-patch-2 07Reception123 035627c40 Create Special:InactivityExemptWikis page (T10674) [09:39:35] [02WikiDiscover] 07Reception123 opened pull request #160: Create Special:InactivityExemptWikis page (T10674) (03main...03Reception123-patch-2) 13https://github.com/miraheze/WikiDiscover/pull/160 [09:43:54] miraheze/WikiDiscover - Reception123 the build passed. [13:26:36] [02TSPortal] 07renovate[bot] merged 03renovate/dev-deps into 03main 13https://github.com/miraheze/TSPortal/compare/0ffea5eb80f4...c5a422a1b353 [13:26:36] [02TSPortal] 07renovate[bot] 04deleted 03renovate/dev-deps at 03c5a422a 13https://api.github.com/repos/miraheze/TSPortal/commit/c5a422a [13:27:01] [02TSPortal] 07renovate[bot] 04force-pushed 03renovate/prod-deps from 0384a23d6 to 03962d87b 13https://api.github.com/repos/miraheze/TSPortal/commits/renovate/prod-deps [13:27:01] 02TSPortal/03renovate/prod-deps 07renovate[bot] 03962d87b Update dependency laravel/framework to v13.9.0 [14:18:27] [02mw-config] 07dependabot[bot] created 03dependabot/composer/phpunit/phpunit-13.1.10 (+1 new commit) 13https://github.com/miraheze/mw-config/commit/73ed0ce4728e [14:18:27] 02mw-config/03dependabot/composer/phpunit/phpunit-13.1.10 07dependabot[bot] 0373ed0ce Update phpunit/phpunit requirement from 13.1.8 to 13.1.10… [14:18:29] [02mw-config] 07dependabot[bot] added the label 'dependencies' to pull request #6410 (Update phpunit/phpunit requirement from 13.1.8 to 13.1.10) 13https://github.com/miraheze/mw-config/pull/6410 [14:18:29] [02mw-config] 07dependabot[bot] opened pull request #6410: Update phpunit/phpunit requirement from 13.1.8 to 13.1.10 (03main...03dependabot/composer/phpunit/phpunit-13.1.10) 13https://github.com/miraheze/mw-config/pull/6410 [14:18:31] [02mw-config] 07dependabot[bot] added the label 'php' to pull request #6410 (Update phpunit/phpunit requirement from 13.1.8 to 13.1.10) 13https://github.com/miraheze/mw-config/pull/6410 [14:18:33] [02mw-config] 07dependabot[bot] added the label 'dependencies' to pull request #6410 (Update phpunit/phpunit requirement from 13.1.8 to 13.1.10) 13https://github.com/miraheze/mw-config/pull/6410 [14:18:35] [02mw-config] 07dependabot[bot] added the label 'php' to pull request #6410 (Update phpunit/phpunit requirement from 13.1.8 to 13.1.10) 13https://github.com/miraheze/mw-config/pull/6410 [14:18:37] [02mw-config] 07dependabot[bot] commented on pull request #6409: Superseded by #6410. 13https://github.com/miraheze/mw-config/pull/6409#issuecomment-4460548256 [14:18:39] [02mw-config] 07dependabot[bot] closed pull request #6409: Update phpunit/phpunit requirement from 13.1.8 to 13.1.9 (03main...03dependabot/composer/phpunit/phpunit-13.1.9) 13https://github.com/miraheze/mw-config/pull/6409 [14:18:41] [02mw-config] 07dependabot[bot] 04deleted 03dependabot/composer/phpunit/phpunit-13.1.9 at 03d6b69ff 13https://api.github.com/repos/miraheze/mw-config/commit/d6b69ff [14:19:52] miraheze/mw-config - dependabot[bot] the build passed. [17:27:19] [02ssl] 07pskyechology pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/d85e08d2bf3b3b5bffbedc1376b05098c4457959 [17:27:19] 02ssl/03main 07Skye 03d85e08d T15380: Add redirect for itemasylumwiki [17:30:19] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/5940069823da35f25cbefab9f67b521209397eb7 [17:30:19] 02ssl/03main 07WikiTideBot 035940069 Bot: Auto-update domain lists [17:42:21] PROBLEM - swiftproxy161 Swift NGINX SSL check on swiftproxy161 is CRITICAL: connect to address localhost and port 443: Connection refused [17:43:43] PROBLEM - swiftproxy161 HTTPS on swiftproxy161 is CRITICAL: connect to address 10.0.16.135 and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [17:46:32] PROBLEM - swiftproxy171 Check unit status of swift_dispersion_stats on swiftproxy171 is CRITICAL: CRITICAL: Status of the systemd unit swift_dispersion_stats [17:46:58] um [17:47:12] @rhinosf1 swift is dead can you poke it [17:47:38] Oh that again [17:48:44] Done @pskyechology [17:49:40] RECOVERY - swiftproxy161 HTTPS on swiftproxy161 is OK: HTTP OK: Status line output matched "HTTP/1.1 404" - 352 bytes in 0.030 second response time [17:50:05] RECOVERY - swiftproxy161 Swift NGINX SSL check on swiftproxy161 is OK: OK - Certificate 'wikitide.net' will expire on Sun May 31 22:19:44 2026 +0000.TCP OK - 0.011 second response time on localhost port 443 [17:50:41] PROBLEM - cloud21 APT on cloud21 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (3 critical updates). [17:50:48] PROBLEM - db171 APT on db171 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [17:51:09] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [17:51:48] PROBLEM - db182 APT on db182 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [17:52:02] not the apt again [17:52:33] PROBLEM - db201 APT on db201 is CRITICAL: APT CRITICAL: 84 packages available for upgrade (1 critical updates). [17:53:11] PROBLEM - mw191 APT on mw191 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [17:53:22] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [17:53:55] PROBLEM - kafka182 APT on kafka182 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [17:54:43] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [17:54:58] PROBLEM - cloud19 APT on cloud19 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [17:56:32] PROBLEM - cp191 APT on cp191 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [17:57:15] PROBLEM - mem191 APT on mem191 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [17:57:24] PROBLEM - mw192 APT on mw192 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [17:57:58] PROBLEM - cp161 APT on cp161 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [17:57:58] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [17:58:14] PROBLEM - graylog161 APT on graylog161 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [17:58:25] RECOVERY - swiftproxy171 Check unit status of swift_dispersion_stats on swiftproxy171 is OK: OK: Status of the systemd unit swift_dispersion_stats [17:58:30] PROBLEM - os162 APT on os162 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [17:59:41] PROBLEM - os202 APT on os202 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [18:00:18] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:00:21] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:01:15] PROBLEM - cloud18 APT on cloud18 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [18:01:15] PROBLEM - mw202 APT on mw202 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:01:29] PROBLEM - db181 APT on db181 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [18:02:02] PROBLEM - ns2 APT on ns2 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [18:02:10] PROBLEM - os191 APT on os191 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:02:12] PROBLEM - db151 APT on db151 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [18:02:48] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (1 critical updates). [18:02:50] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:03:17] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [18:03:22] PROBLEM - reports171 APT on reports171 is CRITICAL: APT CRITICAL: 63 packages available for upgrade (1 critical updates). [18:03:24] PROBLEM - os161 APT on os161 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:03:42] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [18:03:49] PROBLEM - db192 APT on db192 is CRITICAL: APT CRITICAL: 84 packages available for upgrade (1 critical updates). [18:03:55] PROBLEM - cloud20 APT on cloud20 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [18:04:12] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:04:22] PROBLEM - eventgate182 APT on eventgate182 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:04:59] PROBLEM - mw201 APT on mw201 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:05:10] PROBLEM - ldap171 APT on ldap171 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:05:33] PROBLEM - cloud16 APT on cloud16 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [18:05:47] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:05:48] PROBLEM - mon181 APT on mon181 is CRITICAL: APT CRITICAL: 66 packages available for upgrade (1 critical updates). [18:06:26] PROBLEM - swiftobject211 APT on swiftobject211 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:06:31] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:06:41] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:06:41] PROBLEM - bast181 APT on bast181 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [18:06:44] PROBLEM - cloud17 APT on cloud17 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [18:07:51] PROBLEM - mem201 APT on mem201 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:08:04] PROBLEM - prometheus151 APT on prometheus151 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:08:16] PROBLEM - matomo151 APT on matomo151 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:08:29] PROBLEM - mattermost2 APT on mattermost2 is CRITICAL: APT CRITICAL: 60 packages available for upgrade (1 critical updates). [18:09:43] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:09:46] PROBLEM - changeprop202 APT on changeprop202 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:09:51] PROBLEM - cp201 APT on cp201 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:10:28] PROBLEM - db172 APT on db172 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [18:10:49] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:11:05] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:11:51] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:12:02] PROBLEM - cp171 APT on cp171 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:12:18] PROBLEM - rdb191 APT on rdb191 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:12:35] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:12:54] PROBLEM - bast161 APT on bast161 is CRITICAL: APT CRITICAL: 73 packages available for upgrade (1 critical updates). [18:13:00] PROBLEM - puppet181 APT on puppet181 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (1 critical updates). [18:13:05] PROBLEM - mw203 APT on mw203 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:13:11] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:13:26] PROBLEM - llm191 APT on llm191 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [18:13:53] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:14:07] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:14:10] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [18:14:16] PROBLEM - swiftobject201 APT on swiftobject201 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [18:14:39] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:14:48] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:14:58] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:15:49] PROBLEM - phorge171 APT on phorge171 is CRITICAL: APT CRITICAL: 63 packages available for upgrade (1 critical updates). [18:16:14] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [18:16:37] PROBLEM - os201 APT on os201 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:17:18] PROBLEM - db161 APT on db161 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [18:18:02] PROBLEM - os151 APT on os151 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [18:18:38] PROBLEM - mw193 APT on mw193 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [18:19:01] PROBLEM - cloud15 APT on cloud15 is CRITICAL: APT CRITICAL: 122 packages available for upgrade (3 critical updates). [18:19:56] PROBLEM - ns1 APT on ns1 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:20:03] PROBLEM - mem151 APT on mem151 is CRITICAL: APT CRITICAL: 61 packages available for upgrade (1 critical updates). [18:53:09] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:53:33] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 92.53, 46.51, 19.13 [18:54:17] db161 what are you doing [18:55:06] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.077 second response time [19:00:21] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/ac14aac43cfef26749412a9d7f1178dec632b78e [19:00:21] 02ssl/03main 07WikiTideBot 03ac14aac Bot: Auto-update domain lists [19:10:54] PROBLEM - db172 Disk Space on db172 is WARNING: DISK WARNING - free space: / 2950MiB (10.0% inode=95%); [19:13:33] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 1.48, 3.50, 11.23 [19:15:33] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 1.34, 2.79, 10.03 [19:30:20] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/38a3f0ed82e2757f9629172d0a1bc6d04371e9ab [19:30:20] 02ssl/03main 07WikiTideBot 0338a3f0e Bot: Auto-update domain lists [20:23:41] !log [void@puppet181] Upgraded packages on db172: linux-libc-dev [20:23:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:23:54] !log [void@puppet181] Upgraded packages on bots171: linux-libc-dev [20:23:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:24:06] !log [void@puppet181] Upgraded packages on cp161: linux-libc-dev [20:24:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:24:19] !log [void@puppet181] Upgraded packages on db171: linux-libc-dev [20:24:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:24:35] RECOVERY - bots171 APT on bots171 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:24:37] !log [void@puppet181] Upgraded packages on db192: linux-libc-dev [20:24:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:24:51] !log [void@puppet181] Upgraded packages on db161: linux-libc-dev [20:24:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:25:04] RECOVERY - db171 APT on db171 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:25:05] !log [void@puppet181] Upgraded packages on db151: linux-libc-dev [20:25:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:25:16] RECOVERY - db161 APT on db161 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:25:17] RECOVERY - cp161 APT on cp161 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:25:19] !log [void@puppet181] Upgraded packages on bast161: linux-libc-dev [20:25:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:25:33] !log [void@puppet181] Upgraded packages on bast181: linux-libc-dev [20:25:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:25:41] RECOVERY - db172 APT on db172 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:25:46] !log [void@puppet181] Upgraded packages on cloud21: linux-libc-dev, libcpupower1, and linux-cpupower [20:25:46] RECOVERY - db192 APT on db192 is OK: APT OK: 83 packages available for upgrade (0 critical updates). [20:25:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:00] !log [void@puppet181] Upgraded packages on db182: linux-libc-dev [20:26:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:14] !log [void@puppet181] Upgraded packages on cloud15: linux-libc-dev, libcpupower1, and linux-cpupower [20:26:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:28] !log [void@puppet181] Upgraded packages on eventgate182: linux-libc-dev [20:26:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:39] RECOVERY - bast181 APT on bast181 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [20:26:43] !log [void@puppet181] Upgraded packages on cp171: linux-libc-dev [20:26:44] RECOVERY - db151 APT on db151 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:26:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:52] RECOVERY - bast161 APT on bast161 is OK: APT OK: 72 packages available for upgrade (0 critical updates). [20:26:53] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:26:57] !log [void@puppet181] Upgraded packages on graylog161: linux-libc-dev [20:26:57] RECOVERY - db182 APT on db182 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:27:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:09] RECOVERY - cloud21 APT on cloud21 is OK: APT OK: 115 packages available for upgrade (0 critical updates). [20:27:11] RECOVERY - eventgate182 APT on eventgate182 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:27:12] !log [void@puppet181] Upgraded packages on cloud16: linux-libc-dev, libcpupower1, and linux-cpupower [20:27:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:27] !log [void@puppet181] Upgraded packages on cp201: linux-libc-dev [20:27:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:42] !log [void@puppet181] Upgraded packages on cloud17: linux-libc-dev, libcpupower1, and linux-cpupower [20:27:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:52] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [20:27:52] RECOVERY - cp171 APT on cp171 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:27:57] !log [void@puppet181] Upgraded packages on cp191: linux-libc-dev [20:27:58] RECOVERY - cp201 APT on cp201 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:28:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:28:13] !log [void@puppet181] Upgraded packages on db181: linux-libc-dev [20:28:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:28:30] !log [void@puppet181] Upgraded packages on cloud20: linux-libc-dev, libcpupower1, and linux-cpupower [20:28:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:28:43] RECOVERY - cp191 APT on cp191 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:28:46] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:28:47] !log [void@puppet181] Upgraded packages on cloud18: linux-libc-dev, libcpupower1, and linux-cpupower [20:28:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:28:54] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:29:04] !log [void@puppet181] Upgraded packages on cloud19: linux-libc-dev, libcpupower1, and linux-cpupower [20:29:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:29:15] !log [void@puppet181] Upgraded packages on mattermost2: linux-libc-dev [20:29:16] RECOVERY - db181 APT on db181 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:29:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:29:21] RECOVERY - cloud20 APT on cloud20 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:29:28] !log [void@puppet181] Upgraded packages on ldap171: linux-libc-dev [20:29:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:29:33] RECOVERY - cloud19 APT on cloud19 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:29:39] RECOVERY - cloud18 APT on cloud18 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [20:29:46] !log [void@puppet181] Upgraded packages on kafka182: linux-libc-dev [20:29:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:29:59] !log [void@puppet181] Upgraded packages on matomo151: linux-libc-dev [20:30:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:30:13] !log [void@puppet181] Upgraded packages on mem151: linux-libc-dev [20:30:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:30:26] !log [void@puppet181] Upgraded packages on mem161: linux-libc-dev [20:30:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:30:38] RECOVERY - mattermost2 APT on mattermost2 is OK: APT OK: 59 packages available for upgrade (0 critical updates). [20:30:40] !log [void@puppet181] Upgraded packages on mem201: linux-libc-dev [20:30:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:30:55] !log [void@puppet181] Upgraded packages on llm191: linux-libc-dev [20:30:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:31:08] RECOVERY - ldap171 APT on ldap171 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:31:12] !log [void@puppet181] Upgraded packages on changeprop202: linux-libc-dev [20:31:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:31:20] RECOVERY - kafka182 APT on kafka182 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:31:21] RECOVERY - mem201 APT on mem201 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:31:27] !log [void@puppet181] Upgraded packages on mw152: linux-libc-dev [20:31:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:31:42] !log [void@puppet181] Upgraded packages on mw151: linux-libc-dev [20:31:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:31:48] RECOVERY - matomo151 APT on matomo151 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:31:52] RECOVERY - llm191 APT on llm191 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:31:52] RECOVERY - mem161 APT on mem161 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:32:00] !log [void@puppet181] Upgraded packages on db201: linux-libc-dev [20:32:03] RECOVERY - mem151 APT on mem151 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:32:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:32:04] RECOVERY - changeprop202 APT on changeprop202 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:32:15] !log [void@puppet181] Upgraded packages on mem191: linux-libc-dev [20:32:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:32:31] !log [void@puppet181] Upgraded packages on mon181: linux-libc-dev [20:32:40] RECOVERY - mw152 APT on mw152 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:32:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:32:46] RECOVERY - mw151 APT on mw151 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:32:58] RECOVERY - mon181 APT on mon181 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [20:33:02] RECOVERY - mem191 APT on mem191 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:33:19] !log [void@puppet181] Upgraded packages on mw153: linux-libc-dev [20:33:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:33:34] !log [void@puppet181] Upgraded packages on mw161: linux-libc-dev [20:33:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:33:39] RECOVERY - mw161 APT on mw161 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:33:50] !log [void@puppet181] Upgraded packages on mw162: linux-libc-dev [20:33:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:33:59] RECOVERY - db201 APT on db201 is OK: APT OK: 83 packages available for upgrade (0 critical updates). [20:34:05] !log [void@puppet181] Upgraded packages on mw171: linux-libc-dev [20:34:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:34:21] !log [void@puppet181] Upgraded packages on mw163: linux-libc-dev [20:34:21] RECOVERY - mw153 APT on mw153 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:34:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:34:36] !log [void@puppet181] Upgraded packages on mw172: linux-libc-dev [20:34:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:34:52] !log [void@puppet181] Upgraded packages on mw173: linux-libc-dev [20:34:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:35:04] RECOVERY - mw171 APT on mw171 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:35:08] !log [void@puppet181] Upgraded packages on mw181: linux-libc-dev [20:35:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:35:24] !log [void@puppet181] Upgraded packages on mw182: linux-libc-dev [20:35:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:35:40] !log [void@puppet181] Upgraded packages on mw191: linux-libc-dev [20:35:40] RECOVERY - mw162 APT on mw162 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:35:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:35:46] RECOVERY - mw172 APT on mw172 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:35:56] !log [void@puppet181] Upgraded packages on mw183: linux-libc-dev [20:35:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:35:59] RECOVERY - mw181 APT on mw181 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:12] !log [void@puppet181] Upgraded packages on mw192: linux-libc-dev [20:36:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:36:24] RECOVERY - mw163 APT on mw163 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:26] RECOVERY - mw173 APT on mw173 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:27] !log [void@puppet181] Upgraded packages on mw201: linux-libc-dev [20:36:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:36:33] RECOVERY - mw191 APT on mw191 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:38] RECOVERY - mw182 APT on mw182 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:43] !log [void@puppet181] Upgraded packages on mw193: linux-libc-dev [20:36:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:36:46] RECOVERY - mw192 APT on mw192 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:36:59] !log [void@puppet181] Upgraded packages on mw202: linux-libc-dev [20:37:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:37:11] RECOVERY - mw202 APT on mw202 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:37:14] !log [void@puppet181] Upgraded packages on mwtask151: linux-libc-dev [20:37:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:37:18] RECOVERY - mw183 APT on mw183 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:37:30] !log [void@puppet181] Upgraded packages on mw203: linux-libc-dev [20:37:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:37:45] !log [void@puppet181] Upgraded packages on mwtask161: linux-libc-dev [20:37:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:37:53] RECOVERY - mwtask151 APT on mwtask151 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:37:58] !log [void@puppet181] Upgraded packages on ns1: linux-libc-dev [20:38:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:38:16] !log [void@puppet181] Upgraded packages on rdb191: linux-libc-dev [20:38:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:38:22] RECOVERY - mw201 APT on mw201 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:38:29] !log [void@puppet181] Upgraded packages on os161: linux-libc-dev [20:38:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:38:33] RECOVERY - os161 APT on os161 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:38:35] RECOVERY - mw193 APT on mw193 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:38:43] !log [void@puppet181] Upgraded packages on prometheus151: linux-libc-dev [20:38:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:38:58] !log [void@puppet181] Upgraded packages on os151: linux-libc-dev [20:39:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:39:05] RECOVERY - os151 APT on os151 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:39:09] RECOVERY - mw203 APT on mw203 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:39:12] !log [void@puppet181] Upgraded packages on mwtask171: linux-libc-dev [20:39:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:39:21] RECOVERY - mwtask161 APT on mwtask161 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:39:34] !log [void@puppet181] Upgraded packages on os202: linux-libc-dev [20:39:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:39:48] !log [void@puppet181] Upgraded packages on puppet181: linux-libc-dev [20:39:50] RECOVERY - os202 APT on os202 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:39:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:39:54] RECOVERY - ns1 APT on ns1 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:39:59] RECOVERY - prometheus151 APT on prometheus151 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:40:02] !log [void@puppet181] Upgraded packages on reports171: linux-libc-dev [20:40:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:40:08] RECOVERY - rdb191 APT on rdb191 is OK: APT OK: 60 packages available for upgrade (0 critical updates). [20:40:10] RECOVERY - mwtask171 APT on mwtask171 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:40:16] !log [void@puppet181] Upgraded packages on os162: linux-libc-dev [20:40:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:40:30] !log [void@puppet181] Upgraded packages on phorge171: linux-libc-dev [20:40:31] RECOVERY - reports171 APT on reports171 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [20:40:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:40:44] !log [void@puppet181] Upgraded packages on os191: linux-libc-dev [20:40:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:41:02] !log [void@puppet181] Upgraded packages on mwtask181: linux-libc-dev [20:41:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:41:16] !log [void@puppet181] Upgraded packages on swiftobject151: linux-libc-dev [20:41:17] RECOVERY - puppet181 APT on puppet181 is OK: APT OK: 67 packages available for upgrade (0 critical updates). [20:41:17] RECOVERY - phorge171 APT on phorge171 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [20:41:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:41:19] RECOVERY - os162 APT on os162 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:41:32] !log [void@puppet181] Upgraded packages on os201: linux-libc-dev [20:41:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:41:48] !log [void@puppet181] Upgraded packages on swiftobject161: linux-libc-dev [20:41:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:41:57] RECOVERY - os201 APT on os201 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:42:03] !log [void@puppet181] Upgraded packages on swiftac171: linux-libc-dev [20:42:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:42:09] RECOVERY - os191 APT on os191 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:42:24] !log [void@puppet181] Upgraded packages on ns2: linux-libc-dev [20:42:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:42:28] RECOVERY - swiftobject151 APT on swiftobject151 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:42:39] !log [void@puppet181] Upgraded packages on swiftobject171: linux-libc-dev [20:42:40] RECOVERY - swiftac171 APT on swiftac171 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:42:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:42:44] RECOVERY - mwtask181 APT on mwtask181 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [20:42:52] !log [void@puppet181] Upgraded packages on swiftobject211: linux-libc-dev [20:42:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:42:56] RECOVERY - ns2 APT on ns2 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [20:43:10] !log [void@puppet181] Upgraded packages on swiftobject181: linux-libc-dev [20:43:11] RECOVERY - swiftobject161 APT on swiftobject161 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:43:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:43:15] RECOVERY - swiftobject211 APT on swiftobject211 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:43:26] !log [void@puppet181] Upgraded packages on test151: linux-libc-dev [20:43:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:43:39] RECOVERY - swiftobject171 APT on swiftobject171 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [20:43:41] RECOVERY - test151 APT on test151 is OK: APT OK: 67 packages available for upgrade (0 critical updates). [20:43:41] !log [void@puppet181] Upgraded packages on swiftproxy171: linux-libc-dev [20:43:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:43:44] RECOVERY - swiftproxy171 APT on swiftproxy171 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:43:58] !log [void@puppet181] Upgraded packages on swiftobject191: linux-libc-dev [20:44:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:44:13] !log [void@puppet181] Upgraded packages on swiftproxy161: linux-libc-dev [20:44:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:44:17] RECOVERY - swiftobject181 APT on swiftobject181 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [20:44:29] !log [void@puppet181] Upgraded packages on swiftobject201: linux-libc-dev [20:44:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:44:47] RECOVERY - swiftproxy161 APT on swiftproxy161 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [20:45:10] RECOVERY - swiftobject201 APT on swiftobject201 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [20:45:25] RECOVERY - swiftobject191 APT on swiftobject191 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [20:56:19] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 43% [20:59:33] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 11.45, 7.99, 3.95 [21:01:33] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 2.32, 5.62, 3.57 [21:22:19] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 39% [21:39:59] @zipppee cmon it's like you're not even trying any more [21:41:24] just update your apt packages more [21:41:27] I'm not paid enough [21:48:38] PROBLEM - mw193 APT on mw193 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [21:51:03] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [21:52:18] PROBLEM - mw191 APT on mw191 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [21:52:22] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [21:52:31] lmao [21:56:40] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (1 critical updates). [21:57:23] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [21:58:29] PROBLEM - mw192 APT on mw192 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [21:59:30] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:00:05] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:02:03] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:02:31] void's thoughts: :stare: [22:02:46] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:03:11] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [22:03:15] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (1 critical updates). [22:03:45] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (1 critical updates). [22:04:25] PROBLEM - mw201 APT on mw201 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:04:40] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:06:43] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:07:15] PROBLEM - swiftobject211 APT on swiftobject211 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [22:07:23] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:09:15] PROBLEM - mw202 APT on mw202 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:10:25] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [22:11:43] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:11:46] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:11:51] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:12:09] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [22:12:13] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:13:12] PROBLEM - swiftobject201 APT on swiftobject201 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [22:13:16] PROBLEM - mw203 APT on mw203 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:13:21] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:13:24] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [22:14:34] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:14:43] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 62 packages available for upgrade (1 critical updates). [22:15:00] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (1 critical updates). [22:16:22] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (1 critical updates). [22:21:53] PROBLEM - graylog161 graylog tls port 12210 ssl cert check on graylog161 is WARNING: WARNING - Certificate 'wikitide.net' expires in 15 day(s) (Sun May 31 22:19:44 2026 +0000). [22:30:22] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/f1b6bb2d8d3829a97f7eff0d41d518248aafea78 [22:30:22] 02ssl/03main 07WikiTideBot 03f1b6bb2 Bot: Auto-update domain lists [23:09:33] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 83.12, 34.94, 14.42 [23:09:48] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:09:54] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:07] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:07] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.014 second response time [23:10:10] im getting 502s 😭 [23:10:11] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:10:12] same [23:10:13] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:19] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:10:19] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 94% [23:10:20] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:23] 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 10006 milliseconds with 0 bytes received [23:10:32] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:33] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:10:43] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:10:49] bruhhhh [23:10:56] now im no tech but "critical" is generally not what you're aiming for [23:10:59] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:00] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [23:11:05] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:05] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:07] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:08] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 2 backends are down. mw172 mw163 [23:11:13] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:16] 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 10002 milliseconds with 0 bytes received [23:11:23] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:24] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:11:28] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:11:39] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:11:40] PROBLEM - cp161 HTTPS on cp161 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 [23:11:47] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:48] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:11:50] 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 10005 milliseconds with 0 bytes received [23:12:02] 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 10005 milliseconds with 0 bytes received [23:12:08] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [23:12:12] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:12:37] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 9.733 second response time [23:12:42] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 9.632 second response time [23:13:03] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 8.612 second response time [23:13:04] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.002 second response time [23:13:07] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 7.437 second response time [23:13:24] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 3.517 second response time [23:13:24] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 5.497 second response time [23:13:34] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.101 second response time [23:13:35] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 8.885 second response time [23:13:43] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 7.965 second response time [23:13:55] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.857 second response time [23:13:55] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 7.862 second response time [23:14:00] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 8.232 second response time [23:14:18] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.858 second response time [23:14:24] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 9.228 second response time [23:15:14] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 8.912 second response time [23:15:15] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.806 second response time [23:15:16] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 4.696 second response time [23:15:20] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 1.709 second response time [23:15:50] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.064 second response time [23:15:53] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.242 second response time [23:16:08] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.086 second response time [23:16:08] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.354 second response time [23:16:18] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 6.517 second response time [23:16:19] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.233 second response time [23:16:19] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 44% [23:16:28] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.080 second response time [23:16:31] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.190 second response time [23:16:34] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.237 second response time [23:16:40] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.131 second response time [23:17:00] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.064 second response time [23:17:08] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [23:26:19] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 61% [23:28:17] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:28:25] 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 10005 milliseconds with 0 bytes received [23:28:28] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:28:40] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [23:28:43] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:28:47] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:28:48] looking [23:28:50] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:28:53] 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 10006 milliseconds with 0 bytes received [23:29:07] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:29:08] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 1 backends are down. mw173 [23:29:09] 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 [23:29:13] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:29:15] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [23:29:19] 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 10006 milliseconds with 0 bytes received [23:29:22] 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 10003 milliseconds with 0 bytes received [23:29:23] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:29:23] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:29:24] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [23:29:30] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:29:34] PROBLEM - cp161 HTTPS on cp161 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 [23:29:46] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 2 backends are down. mw163 mw201 [23:29:48] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [23:29:57] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10006 milliseconds with 0 bytes received [23:29:59] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 1 backends are down. mw201 [23:30:04] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.012 second response time [23:30:24] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 1 backends are down. mw201 [23:30:32] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.130 second response time [23:30: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 10006 milliseconds with 0 bytes received [23:30:47] !log [somerandomdeveloper@mwtask181] starting deploy of {'config': True, 'force': True} to all [23:30:51] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 8.974 second response time [23:31:02] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 9.715 second response time [23:31:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:31:07] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.083 second response time [23:31:07] !log [somerandomdeveloper@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 20s [23:31:07] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.660 second response time [23:31:08] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.280 second response time [23:31:08] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [23:31:10] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.087 second response time [23:31:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:31:11] !log depool c2 [23:31:13] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.076 second response time [23:31:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:31:19] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.072 second response time [23:31:19] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.253 second response time [23:31:21] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.227 second response time [23:31:21] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [23:31:26] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.225 second response time [23:31:27] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.089 second response time [23:31:44] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.081 second response time [23:31:46] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [23:31:54] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.082 second response time [23:31:56] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [23:31:58] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.241 second response time [23:32:09] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.246 second response time [23:32:19] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is WARNING: WARNING - NGINX Error Rate is 58% [23:32:23] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [23:32:35] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.229 second response time [23:32:38] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.089 second response time [23:32:45] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [23:32:49] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.079 second response time [23:32:50] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.258 second response time [23:37:27] !log [somerandomdeveloper@mwtask181] starting deploy of {'config': True, 'force': True} to all [23:37:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:37:45] !log [somerandomdeveloper@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 18s [23:37:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:37:57] !log repool c2 [23:38:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:40:19] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 31% [23:57:33] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 2.44, 3.18, 11.26