[00:00:02] smh do i need to buy a sharpie and draw evil faces on it [00:00:45] RECOVERY - phorge171 Current Load on phorge171 is OK: LOAD OK - total load average: 0.92, 5.17, 6.12 [00:00:52] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/03bb08c61f6c6d91aa0398878af54a17e9b77f28 [00:00:52] 02statichelp/03main 07WikiTideBot 0303bb08c Bot: Auto-update Tech namespace pages 2026-06-21 00:00:50 [06:24:35] PROBLEM - os151 Current Load on os151 is WARNING: LOAD WARNING - total load average: 3.57, 2.96, 2.03 [06:26:35] RECOVERY - os151 Current Load on os151 is OK: LOAD OK - total load average: 1.57, 2.46, 1.96 [08:18:17] PROBLEM - mem151 APT on mem151 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:18:35] PROBLEM - os201 APT on os201 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:18:54] tuff updates [08:19:05] PROBLEM - os151 APT on os151 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:19:08] PROBLEM - cloud15 APT on cloud15 is CRITICAL: APT CRITICAL: 137 packages available for upgrade (3 critical updates). [08:19:12] PROBLEM - cloud21 APT on cloud21 is CRITICAL: APT CRITICAL: 131 packages available for upgrade (3 critical updates). [08:19:55] PROBLEM - ns1 APT on ns1 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [08:20:02] PROBLEM - mw193 APT on mw193 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:21:03] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:21:47] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:21:57] PROBLEM - db171 APT on db171 is CRITICAL: APT CRITICAL: 86 packages available for upgrade (1 critical updates). [08:22:57] PROBLEM - mw191 APT on mw191 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:23:09] PROBLEM - kafka182 APT on kafka182 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [08:23:24] PROBLEM - db182 APT on db182 is CRITICAL: APT CRITICAL: 86 packages available for upgrade (1 critical updates). [08:23:44] PROBLEM - db201 APT on db201 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (1 critical updates). [08:25:28] PROBLEM - cloud19 APT on cloud19 is CRITICAL: APT CRITICAL: 137 packages available for upgrade (3 critical updates). [08:25:55] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 89 packages available for upgrade (1 critical updates). [08:26:06] PROBLEM - cp191 APT on cp191 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [08:26:43] PROBLEM - mw192 APT on mw192 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:27:28] PROBLEM - cp161 APT on cp161 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:28:10] PROBLEM - os162 APT on os162 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:28:14] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:28:42] PROBLEM - mem191 APT on mem191 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:29:18] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:29:30] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:29:38] PROBLEM - graylog161 APT on graylog161 is CRITICAL: APT CRITICAL: 80 packages available for upgrade (1 critical updates). [08:30:09] PROBLEM - os202 APT on os202 is CRITICAL: APT CRITICAL: 79 packages available for upgrade (1 critical updates). [08:31:46] PROBLEM - db181 APT on db181 is CRITICAL: APT CRITICAL: 86 packages available for upgrade (1 critical updates). [08:31:51] PROBLEM - ns2 APT on ns2 is CRITICAL: APT CRITICAL: 82 packages available for upgrade (1 critical updates). [08:32:08] PROBLEM - cloud18 APT on cloud18 is CRITICAL: APT CRITICAL: 131 packages available for upgrade (3 critical updates). [08:32:13] PROBLEM - reports171 APT on reports171 is CRITICAL: APT CRITICAL: 80 packages available for upgrade (1 critical updates). [08:32:49] PROBLEM - os191 APT on os191 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:32:49] PROBLEM - os161 APT on os161 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:33:20] PROBLEM - db151 APT on db151 is CRITICAL: APT CRITICAL: 86 packages available for upgrade (1 critical updates). [08:33:36] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:33:49] PROBLEM - eventgate182 APT on eventgate182 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [08:33:50] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [08:34:07] PROBLEM - db192 APT on db192 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (1 critical updates). [08:34:12] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:34:21] PROBLEM - cloud20 APT on cloud20 is CRITICAL: APT CRITICAL: 137 packages available for upgrade (3 critical updates). [08:34:22] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [08:34:35] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:34:46] PROBLEM - bast181 APT on bast181 is CRITICAL: APT CRITICAL: 85 packages available for upgrade (1 critical updates). [08:35:02] PROBLEM - mon181 APT on mon181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [08:35:04] PROBLEM - ldap171 APT on ldap171 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:35:06] PROBLEM - mw201 APT on mw201 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:35:34] PROBLEM - cloud16 APT on cloud16 is CRITICAL: APT CRITICAL: 131 packages available for upgrade (3 critical updates). [08:35:46] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:35:57] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:36:34] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:36:54] PROBLEM - swiftobject211 APT on swiftobject211 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (1 critical updates). [08:37:57] PROBLEM - cloud17 APT on cloud17 is CRITICAL: APT CRITICAL: 131 packages available for upgrade (3 critical updates). [08:38:05] PROBLEM - mattermost2 APT on mattermost2 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [08:38:57] PROBLEM - prometheus151 APT on prometheus151 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:39:04] PROBLEM - mem201 APT on mem201 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:39:25] PROBLEM - matomo151 APT on matomo151 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [08:39:28] PROBLEM - changeprop202 APT on changeprop202 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [08:40:14] PROBLEM - db172 APT on db172 is CRITICAL: APT CRITICAL: 86 packages available for upgrade (1 critical updates). [08:40:41] PROBLEM - mw202 APT on mw202 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:40:47] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:40:58] PROBLEM - cp201 APT on cp201 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [08:41:09] PROBLEM - cp171 APT on cp171 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [08:41:11] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:41:29] PROBLEM - rdb191 APT on rdb191 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [08:41:39] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:42:03] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:42:05] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 117 packages available for upgrade (1 critical updates). [08:42:07] PROBLEM - bast161 APT on bast161 is CRITICAL: APT CRITICAL: 84 packages available for upgrade (1 critical updates). [08:42:11] PROBLEM - llm191 APT on llm191 is CRITICAL: APT CRITICAL: 84 packages available for upgrade (1 critical updates). [08:42:14] PROBLEM - mw203 APT on mw203 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:42:26] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:42:57] PROBLEM - swiftobject201 APT on swiftobject201 is CRITICAL: APT CRITICAL: 82 packages available for upgrade (1 critical updates). [08:43:37] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 82 packages available for upgrade (1 critical updates). [08:43:54] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [08:44:02] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:44:09] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:44:10] PROBLEM - puppet181 APT on puppet181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [08:44:27] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [08:45:26] PROBLEM - phorge171 APT on phorge171 is CRITICAL: APT CRITICAL: 79 packages available for upgrade (1 critical updates). [08:45:40] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 81 packages available for upgrade (1 critical updates). [08:46:12] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 82 packages available for upgrade (1 critical updates). [08:46:57] PROBLEM - db161 APT on db161 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [10:49:40] you want me to eat sharpies too??? sure why not [10:58:22] !log MediaWiki\Extension\CentralAuth\User\CentralAuthUser::getInstance( User::newFromName( 'FrivolousCreature' ) )->attach( 'dustbunnywiki', 'admin' ); [10:58:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:24:12] [02mediawiki-repos] 07renovate[bot] pushed 1 new commit to 03main 13https://github.com/miraheze/mediawiki-repos/commit/38582286cd22cabab5b9cb4f9e0ad55bd0c0aa1b [11:24:12] 02mediawiki-repos/03main 07renovate[bot] 033858228 chore(deps): update all dependencies to v7 [11:24:13] [02mediawiki-repos] 07renovate[bot] 04deleted 03renovate/all-deps at 033858228 13https://api.github.com/repos/miraheze/mediawiki-repos/commit/3858228 [11:58:26] [02puppet] 07paladox created 03paladox-patch-2 (+1 new commit) 13https://github.com/miraheze/puppet/commit/cc1ec489de46 [11:58:27] 02puppet/03paladox-patch-2 07paladox 03cc1ec48 matomo: Increase archivers to 3 [11:58:33] [02puppet] 07paladox opened pull request #4873: matomo: Increase archivers to 3 (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4873 [12:01:37] [02python-functions] 07renovate[bot] 04force-pushed 03renovate/all-deps from 03d0a2c13 to 03d072c3c 13https://api.github.com/repos/miraheze/python-functions/commits/renovate/all-deps [12:01:37] 02python-functions/03renovate/all-deps 07renovate[bot] 03d072c3c chore(deps): update all dependencies [12:08:49] !log [wwr@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php MirahezeMagic:ResetWiki --wiki=loginwiki --dbname=minecraftminigameswiki --requester=MC mrjone (END - exit=0) [12:08:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:11:36] [02puppet] 07paladox merged pull request #4873: matomo: Increase archivers to 3 (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4873 [12:11:38] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/31a0cbb56d6213af310f51f15375134895b79ad7 [12:11:40] [02puppet] 07paladox 04deleted 03paladox-patch-2 at 03cc1ec48 13https://api.github.com/repos/miraheze/puppet/commit/cc1ec48 [12:11:41] 02puppet/03main 07paladox 0331a0cbb matomo: Increase archivers to 3 (#4873) [12:13:44] !log [wwr@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php CreateWiki:SetContainersAccess --wiki=minecraftminigameswiki (END - exit=0) [12:13:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:14:33] PROBLEM - puppet181 Puppet on puppet181 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_puppet] [12:20:33] RECOVERY - puppet181 Puppet on puppet181 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [12:25:17] !log [wwr@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php createAndPromote --wiki=minecraftminigameswiki MC_mrjone --bureaucrat --sysop --interface-admin --force (END - exit=256) [12:25:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:09:30] PROBLEM - cp171 APT on cp171 is WARNING: APT WARNING: 0 packages available for upgrade (0 critical updates). warnings detected, errors detected. [14:10:33] PROBLEM - mem161 APT on mem161 is WARNING: APT WARNING: 0 packages available for upgrade (0 critical updates). warnings detected, errors detected. [14:11:30] PROBLEM - cp171 APT on cp171 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [14:12:35] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (1 critical updates). [14:22:44] PROBLEM - bots171 APT on bots171 is WARNING: APT WARNING: 0 packages available for upgrade (0 critical updates). warnings detected, errors detected. [14:23:38] PROBLEM - cp191 APT on cp191 is WARNING: APT WARNING: 0 packages available for upgrade (0 critical updates). warnings detected, errors detected. [14:24:45] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 89 packages available for upgrade (1 critical updates). [14:25:40] PROBLEM - cp191 APT on cp191 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [15:23:40] PROBLEM - os201 Current Load on os201 is WARNING: LOAD WARNING - total load average: 3.75, 2.75, 1.74 [15:27:40] RECOVERY - os201 Current Load on os201 is OK: LOAD OK - total load average: 1.54, 2.40, 1.86 [15:36:19] [02landing] 07renovate[bot] pushed 1 new commit to 03main 13https://github.com/miraheze/landing/commit/6ce33bf53a82e6b218db568c362a86db1307d354 [15:36:19] 02landing/03main 07renovate[bot] 036ce33bf Update all dependencies to v7 [15:36:20] [02landing] 07renovate[bot] 04deleted 03renovate/all-deps at 036ce33bf 13https://api.github.com/repos/miraheze/landing/commit/6ce33bf [15:37:03] miraheze/landing - renovate[bot] the build passed. [17:40:44] PROBLEM - swiftobject191 APT on swiftobject191 is WARNING: APT WARNING: 0 packages available for upgrade (0 critical updates). warnings detected, errors detected. [17:42:47] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 83 packages available for upgrade (2 critical updates). [19:35:59] [02pywikibot-config] 07renovate[bot] pushed 1 new commit to 03main 13https://github.com/miraheze/pywikibot-config/commit/53c45726fa44c036fa493d32090448a1f37a7585 [19:36:00] 02pywikibot-config/03main 07renovate[bot] 0353c4572 Update all dependencies to v7 [19:36:02] [02pywikibot-config] 07renovate[bot] 04deleted 03renovate/all-deps at 0353c4572 13https://api.github.com/repos/miraheze/pywikibot-config/commit/53c4572 [22:25:25] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 176.14, 59.74, 23.59 [22:26:44] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:26:50] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:26:51] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [22:26:54] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:26:55] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:27:05] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 11 backends are down. mw151 mw161 mw171 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [22:27:42] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:27:44] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:44] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:46] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [22:27:46] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:47] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:48] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:51] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [22:27:53] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:27:58] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 11 backends are down. mw151 mw161 mw171 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [22:28:08] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 11 backends are down. mw151 mw161 mw171 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [22:28:09] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 93% [22:29:46] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:29:47] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [22:29:48] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:29:49] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:29:49] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:29:50] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:29:51] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:29:56] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [22:29:59] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:30:05] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:30:07] PROBLEM - mw201 HTTPS on mw201 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 [22:30:14] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:30:14] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:30:17] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:30:17] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:30:19] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.013 second response time [22:30:20] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:30:20] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:30:21] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:30:23] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:30:24] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [22:30:25] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10005 milliseconds with 0 bytes received [22:30:26] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 11 backends are down. mw151 mw161 mw171 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [22:30:26] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10005 milliseconds with 0 bytes received [22:30:28] 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 10003 milliseconds with 0 bytes received [22:30:31] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [22:30:41] 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 [22:32:19] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [22:32:31] PROBLEM - db161 MariaDB Connections on db161 is WARNING: Warning connection usage: 89%Current connections: 890 [22:33:45] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.218 second response time [22:33:46] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.073 second response time [22:33:49] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.068 second response time [22:33:50] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.216 second response time [22:33:52] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.066 second response time [22:33:53] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.213 second response time [22:33:54] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.218 second response time [22:33:55] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [22:33:58] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [22:34:04] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.223 second response time [22:34:12] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.073 second response time [22:34:26] RECOVERY - db161 MariaDB Connections on db161 is OK: OK connection usage: 74.6%Current connections: 746 [22:34:29] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.067 second response time [22:34:29] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.067 second response time [22:35:00] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.947 second response time [22:35:54] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.215 second response time [22:36:24] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.759 second response time [22:36:25] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.433 second response time [22:36:46] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.084 second response time [22:37:15] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [22:37:38] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 1.086 second response time [22:37:38] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.322 second response time [22:37:38] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.069 second response time [22:37:39] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.149 second response time [22:37:42] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.760 second response time [22:37:46] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.083 second response time [22:37:53] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.076 second response time [22:37:58] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [22:37:59] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.070 second response time [22:38:02] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [22:38:03] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [22:38:08] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [22:38:09] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 12% [22:38:17] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.076 second response time [22:38:17] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.075 second response time [22:38:20] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [22:38:21] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [22:38:21] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.083 second response time [22:38:23] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.174 second response time [22:38:35] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.185 second response time [22:38:38] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.215 second response time [22:38:46] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [22:38:49] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.076 second response time [22:38:50] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.083 second response time [22:38:54] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.279 second response time [22:39:05] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [23:00:19] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [23:35:24] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 2.81, 3.60, 10.99 [23:37:24] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 1.89, 3.08, 9.91 [23:48:49] !log [void@puppet181] Upgraded packages on bast161: linux-libc-dev, squid-common, and squid [23:48:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:49:03] !log [void@puppet181] Upgraded packages on cloud21: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:49:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:49:17] !log [void@puppet181] Upgraded packages on db172: linux-libc-dev [23:49:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:49:35] !log [void@puppet181] Upgraded packages on cloud15: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:49:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:49:39] RECOVERY - db172 APT on db172 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [23:49:46] RECOVERY - bast161 APT on bast161 is OK: APT OK: 83 packages available for upgrade (0 critical updates). [23:49:51] !log [void@puppet181] Upgraded packages on bots171: linux-libc-dev and python3-pil [23:49:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:50:08] !log [void@puppet181] Upgraded packages on cloud17: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:50:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:50:14] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 134 packages available for upgrade (0 critical updates). [23:50:26] RECOVERY - cloud21 APT on cloud21 is OK: APT OK: 128 packages available for upgrade (0 critical updates). [23:50:27] !log [void@puppet181] Upgraded packages on cloud19: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:50:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:50:42] !log [void@puppet181] Upgraded packages on db161: linux-libc-dev [23:50:45] RECOVERY - bots171 APT on bots171 is OK: APT OK: 88 packages available for upgrade (0 critical updates). [23:50:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:51:00] !log [void@puppet181] Upgraded packages on cloud16: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:51:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:51:16] !log [void@puppet181] Upgraded packages on cp171: linux-libc-dev [23:51:16] RECOVERY - cloud19 APT on cloud19 is OK: APT OK: 134 packages available for upgrade (0 critical updates). [23:51:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:51:30] !log [void@puppet181] Upgraded packages on cp161: linux-libc-dev [23:51:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:51:40] RECOVERY - db161 APT on db161 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [23:51:47] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 128 packages available for upgrade (0 critical updates). [23:51:48] !log [void@puppet181] Upgraded packages on cloud18: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:51:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:52:05] !log [void@puppet181] Upgraded packages on db171: linux-libc-dev [23:52:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:52:22] !log [void@puppet181] Upgraded packages on db151: linux-libc-dev [23:52:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:52:29] RECOVERY - cloud18 APT on cloud18 is OK: APT OK: 128 packages available for upgrade (0 critical updates). [23:52:59] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 128 packages available for upgrade (0 critical updates). [23:53:06] RECOVERY - cp171 APT on cp171 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [23:53:11] RECOVERY - cp161 APT on cp161 is OK: APT OK: 76 packages available for upgrade (0 critical updates). [23:53:14] !log [void@puppet181] Upgraded packages on bast181: linux-libc-dev, squid-common, and squid [23:53:14] RECOVERY - bast181 APT on bast181 is OK: APT OK: 84 packages available for upgrade (0 critical updates). [23:53:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:53:35] !log [void@puppet181] Upgraded packages on changeprop202: linux-libc-dev and libhttp-daemon-perl [23:53:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:53:45] RECOVERY - db171 APT on db171 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [23:53:52] RECOVERY - changeprop202 APT on changeprop202 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [23:53:52] !log [void@puppet181] Upgraded packages on cp191: linux-libc-dev [23:53:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:54:09] !log [void@puppet181] Upgraded packages on eventgate182: linux-libc-dev and libhttp-daemon-perl [23:54:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:54:13] RECOVERY - db151 APT on db151 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [23:54:22] RECOVERY - eventgate182 APT on eventgate182 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [23:54:28] !log [void@puppet181] Upgraded packages on cloud20: linux-libc-dev, libcpupower1, libhttp-daemon-perl, and linux-cpupower [23:54:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:54:45] !log [void@puppet181] Upgraded packages on db182: linux-libc-dev [23:54:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:55:02] !log [void@puppet181] Upgraded packages on cp201: linux-libc-dev [23:55:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:55:20] !log [void@puppet181] Upgraded packages on db181: linux-libc-dev [23:55:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:55:40] !log [void@puppet181] Upgraded packages on db192: linux-libc-dev [23:55:41] RECOVERY - cp191 APT on cp191 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [23:55:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:55:52] RECOVERY - cp201 APT on cp201 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [23:56:00] !log [void@puppet181] Upgraded packages on db201: linux-libc-dev [23:56:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:56:09] RECOVERY - db182 APT on db182 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [23:56:15] RECOVERY - db201 APT on db201 is OK: APT OK: 93 packages available for upgrade (0 critical updates). [23:56:17] !log [void@puppet181] Upgraded packages on graylog161: linux-libc-dev [23:56:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:56:28] !log [void@puppet181] Upgraded packages on mattermost2: linux-libc-dev [23:56:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:56:32] RECOVERY - cloud20 APT on cloud20 is OK: APT OK: 134 packages available for upgrade (0 critical updates). [23:56:36] RECOVERY - db192 APT on db192 is OK: APT OK: 93 packages available for upgrade (0 critical updates). [23:56:47] !log [void@puppet181] Upgraded packages on kafka182: linux-libc-dev [23:56:47] RECOVERY - mattermost2 APT on mattermost2 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [23:56:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:56:59] RECOVERY - kafka182 APT on kafka182 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [23:57:02] !log [void@puppet181] Upgraded packages on mem151: linux-libc-dev [23:57:05] PROBLEM - bots171 Puppet on bots171 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): Exec[git_pull_Pywikibot-stable],Exec[git_pull_IRC-Discord-Relay-relaybot] [23:57:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:57:06] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 79 packages available for upgrade (0 critical updates). [23:57:18] !log [void@puppet181] Upgraded packages on matomo151: linux-libc-dev [23:57:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:57:22] RECOVERY - db181 APT on db181 is OK: APT OK: 85 packages available for upgrade (0 critical updates). [23:57:34] !log [void@puppet181] Upgraded packages on mem161: linux-libc-dev [23:57:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:57:50] !log [void@puppet181] Upgraded packages on llm191: linux-libc-dev [23:57:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:57:55] RECOVERY - matomo151 APT on matomo151 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [23:58:06] !log [void@puppet181] Upgraded packages on mem201: linux-libc-dev [23:58:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:58:12] RECOVERY - mem201 APT on mem201 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [23:58:29] !log [void@puppet181] Upgraded packages on mw151: linux-libc-dev, libimage-magick-perl, imagemagick-7-common, libmagickcore-7.q16-10, libimage-magick-q16-perl, libmagickwand-7.q16-10, imagemagick-7.q16, imagemagick, libhttp-daemon-perl, libmagickcore-7.q16-10-extra, and python3-pil [23:58:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:58:35] RECOVERY - mem161 APT on mem161 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [23:58:52] RECOVERY - mem151 APT on mem151 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [23:58:52] !log [void@puppet181] Upgraded packages on mw162: linux-libc-dev, libimage-magick-perl, imagemagick-7-common, libmagickcore-7.q16-10, libimage-magick-q16-perl, libmagickwand-7.q16-10, imagemagick-7.q16, imagemagick, libhttp-daemon-perl, libmagickcore-7.q16-10-extra, and python3-pil [23:58:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:59:08] RECOVERY - mw151 APT on mw151 is OK: APT OK: 115 packages available for upgrade (0 critical updates). [23:59:16] !log [void@puppet181] Upgraded packages on mw161: linux-libc-dev, libimage-magick-perl, imagemagick-7-common, libmagickcore-7.q16-10, libimage-magick-q16-perl, libmagickwand-7.q16-10, imagemagick-7.q16, imagemagick, libhttp-daemon-perl, libmagickcore-7.q16-10-extra, and python3-pil [23:59:18] RECOVERY - mw162 APT on mw162 is OK: APT OK: 115 packages available for upgrade (0 critical updates). [23:59:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:59:31] !log [void@puppet181] Upgraded packages on mon181: linux-libc-dev [23:59:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [23:59:37] RECOVERY - mw161 APT on mw161 is OK: APT OK: 115 packages available for upgrade (0 critical updates). [23:59:51] RECOVERY - llm191 APT on llm191 is OK: APT OK: 83 packages available for upgrade (0 critical updates). [23:59:54] !log [void@puppet181] Upgraded packages on mw152: linux-libc-dev, libimage-magick-perl, imagemagick-7-common, libmagickcore-7.q16-10, libimage-magick-q16-perl, libmagickwand-7.q16-10, imagemagick-7.q16, imagemagick, libhttp-daemon-perl, libmagickcore-7.q16-10-extra, and python3-pil [23:59:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log