[00:01:24] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/7e2a12f6d2152466821c4ec32c6b50a173e3d07a [00:01:24] 02statichelp/03main 07WikiTideBot 037e2a12f Bot: Auto-update Tech namespace pages 2025-12-10 00:01:21 [00:14:34] RECOVERY - cp191 Disk Space on cp191 is OK: DISK OK - free space: / 72608MiB (15% inode=99%); [00:14:46] RECOVERY - cp171 Disk Space on cp171 is OK: DISK OK - free space: / 72736MiB (16% inode=99%); [00:16:52] RECOVERY - cp201 Disk Space on cp201 is OK: DISK OK - free space: / 70519MiB (15% inode=99%); [08:57:13] PROBLEM - mem191 APT on mem191 is CRITICAL: APT CRITICAL: 110 packages available for upgrade (1 critical updates). [08:58:03] PROBLEM - mw192 APT on mw192 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [08:58:26] PROBLEM - changeprop201 APT on changeprop201 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [08:58:29] PROBLEM - os162 APT on os162 is CRITICAL: APT CRITICAL: 113 packages available for upgrade (1 critical updates). [08:58:30] PROBLEM - graylog161 APT on graylog161 is CRITICAL: APT CRITICAL: 115 packages available for upgrade (1 critical updates). [09:00:01] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:00:04] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 134 packages available for upgrade (3 critical updates). [09:00:08] PROBLEM - os202 APT on os202 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:00:11] PROBLEM - db181 APT on db181 is CRITICAL: APT CRITICAL: 120 packages available for upgrade (1 critical updates). [09:02:00] PROBLEM - ns2 APT on ns2 is CRITICAL: APT CRITICAL: 115 packages available for upgrade (1 critical updates). [09:02:11] PROBLEM - mattermost1 APT on mattermost1 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [09:02:22] PROBLEM - db151 APT on db151 is CRITICAL: APT CRITICAL: 128 packages available for upgrade (1 critical updates). [09:02:34] PROBLEM - reports171 APT on reports171 is CRITICAL: APT CRITICAL: 114 packages available for upgrade (1 critical updates). [09:02:37] PROBLEM - os191 APT on os191 is CRITICAL: APT CRITICAL: 111 packages available for upgrade (1 critical updates). [09:02:45] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:02:57] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:03:14] PROBLEM - os161 APT on os161 is CRITICAL: APT CRITICAL: 111 packages available for upgrade (1 critical updates). [09:03:17] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:03:25] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (3 critical updates). [09:03:42] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 120 packages available for upgrade (3 critical updates). [09:03:49] PROBLEM - mw201 APT on mw201 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:04:09] PROBLEM - cloud20 APT on cloud20 is CRITICAL: APT CRITICAL: 190 packages available for upgrade (1 critical updates). [09:04:19] PROBLEM - mon181 APT on mon181 is CRITICAL: APT CRITICAL: 20 packages available for upgrade (1 critical updates). [09:04:26] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:04:40] PROBLEM - ldap171 APT on ldap171 is CRITICAL: APT CRITICAL: 110 packages available for upgrade (1 critical updates). [09:05:15] PROBLEM - bast181 APT on bast181 is CRITICAL: APT CRITICAL: 1 packages available for upgrade (1 critical updates). [09:05:20] PROBLEM - db192 APT on db192 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [09:05:31] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:06:37] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:07:18] PROBLEM - matomo151 APT on matomo151 is CRITICAL: APT CRITICAL: 73 packages available for upgrade (1 critical updates). [09:07:20] PROBLEM - prometheus151 APT on prometheus151 is CRITICAL: APT CRITICAL: 114 packages available for upgrade (1 critical updates). [09:08:49] PROBLEM - mem201 APT on mem201 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [09:08:51] PROBLEM - cp201 APT on cp201 is CRITICAL: APT CRITICAL: 80 packages available for upgrade (1 critical updates). [09:10:09] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:10:28] PROBLEM - db172 APT on db172 is CRITICAL: APT CRITICAL: 93 packages available for upgrade (1 critical updates). [09:10:38] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 127 packages available for upgrade (1 critical updates). [09:10:54] PROBLEM - bast161 APT on bast161 is CRITICAL: APT CRITICAL: 1 packages available for upgrade (1 critical updates). [09:10:57] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:11:25] PROBLEM - mw202 APT on mw202 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:12:00] PROBLEM - llm191 APT on llm191 is CRITICAL: APT CRITICAL: 5 packages available for upgrade (1 critical updates). [09:12:02] PROBLEM - mw203 APT on mw203 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:12:05] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 136 packages available for upgrade (3 critical updates). [09:12:05] PROBLEM - cp171 APT on cp171 is CRITICAL: APT CRITICAL: 109 packages available for upgrade (1 critical updates). [09:12:16] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 127 packages available for upgrade (1 critical updates). [09:12:18] PROBLEM - eventgate181 APT on eventgate181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [09:12:24] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:13:05] PROBLEM - puppet181 APT on puppet181 is CRITICAL: APT CRITICAL: 78 packages available for upgrade (1 critical updates). [09:13:33] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:13:40] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 136 packages available for upgrade (3 critical updates). [09:13:56] PROBLEM - swiftobject201 APT on swiftobject201 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:13:59] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:14:01] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [09:14:25] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 136 packages available for upgrade (3 critical updates). [09:14:50] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:15:44] PROBLEM - phorge171 APT on phorge171 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (1 critical updates). [09:16:32] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 125 packages available for upgrade (1 critical updates). [09:17:04] PROBLEM - db161 APT on db161 is CRITICAL: APT CRITICAL: 128 packages available for upgrade (1 critical updates). [09:17:05] PROBLEM - os201 APT on os201 is CRITICAL: APT CRITICAL: 83 packages available for upgrade (1 critical updates). [09:17:22] PROBLEM - cloud15 APT on cloud15 is CRITICAL: APT CRITICAL: 189 packages available for upgrade (1 critical updates). [09:18:42] PROBLEM - cloud16 APT on cloud16 is CRITICAL: APT CRITICAL: 186 packages available for upgrade (1 critical updates). [09:18:54] PROBLEM - ns1 APT on ns1 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [09:19:06] PROBLEM - os151 APT on os151 is CRITICAL: APT CRITICAL: 113 packages available for upgrade (1 critical updates). [09:19:40] PROBLEM - mem151 APT on mem151 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [09:19:40] PROBLEM - mw193 APT on mw193 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:19:46] PROBLEM - db171 APT on db171 is CRITICAL: APT CRITICAL: 120 packages available for upgrade (1 critical updates). [09:21:09] PROBLEM - kafka181 APT on kafka181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [09:21:44] PROBLEM - mw191 APT on mw191 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:22:10] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:22:19] PROBLEM - db182 APT on db182 is CRITICAL: APT CRITICAL: 83 packages available for upgrade (1 critical updates). [09:22:29] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 132 packages available for upgrade (3 critical updates). [09:22:38] PROBLEM - cloud17 APT on cloud17 is CRITICAL: APT CRITICAL: 186 packages available for upgrade (1 critical updates). [09:22:48] PROBLEM - db201 APT on db201 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (1 critical updates). [09:23:23] PROBLEM - cloud19 APT on cloud19 is CRITICAL: APT CRITICAL: 6 packages available for upgrade (1 critical updates). [09:25:05] PROBLEM - cloud18 APT on cloud18 is CRITICAL: APT CRITICAL: 186 packages available for upgrade (1 critical updates). [09:25:18] PROBLEM - cp191 APT on cp191 is CRITICAL: APT CRITICAL: 109 packages available for upgrade (1 critical updates). [09:26:17] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 116 packages available for upgrade (1 critical updates). [09:27:22] PROBLEM - cp161 APT on cp161 is CRITICAL: APT CRITICAL: 119 packages available for upgrade (1 critical updates). [09:27:37] PROBLEM - rdb151 APT on rdb151 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (1 critical updates). [09:28:32] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (1 critical updates). [09:46:39] !log Miraheze\MatomoAnalytics\MatomoAnalytics::addSite( 'itemasylumwiki' ) [09:46:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:15:27] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:27] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:33] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:34] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.013 second response time [11:15:39] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:15:39] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:39] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:15:46] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 10 backends are down. mw151 mw161 mw162 mw181 mw153 mw163 mw191 mw192 mw193 mw201 [11:15:50] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 81% [11:15:51] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:53] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:15:57] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:15:59] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:03] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:03] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:05] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:09] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:16:15] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:18] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [11:16:22] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:33] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.019 second response time [11:16:45] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [11:16:46] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:16:46] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:57] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:16:58] PROBLEM - db181 Current Load on db181 is CRITICAL: LOAD CRITICAL - total load average: 244.50, 111.52, 45.67 [11:17:02] 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 10004 milliseconds with 0 bytes received [11:17:03] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:03] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:17:05] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10002 milliseconds with 0 bytes received [11:17:05] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:05] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:07] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:17:07] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [11:17:10] 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 [11:17:14] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:17:15] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [11:17:15] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [11:17:18] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:18] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.019 second response time [11:17:18] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 10 backends are down. mw151 mw161 mw162 mw181 mw153 mw163 mw191 mw192 mw193 mw201 [11:17:20] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 10 backends are down. mw151 mw161 mw162 mw181 mw153 mw163 mw191 mw192 mw193 mw201 [11:17:21] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:24] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:17:27] 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 10002 milliseconds with 0 bytes received [11:18:45] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [11:19:12] !log put c4/d181 into maint mode [11:19:13] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [11:19:38] PROBLEM - db181 MariaDB Connections on db181 is UNKNOWN: [11:19:43] !log [blankeclair@mwtask181] starting deploy of {'config': True, 'force': True} to all [11:19:50] PROBLEM - db181 Puppet on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [11:20:06] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 8.867 second response time [11:20:07] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.252 second response time [11:20:09] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.415 second response time [11:20:10] PROBLEM - db181 MariaDB on db181 is UNKNOWN: [11:20:14] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4328 bytes in 0.066 second response time [11:20:22] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.061 second response time [11:20:23] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.076 second response time [11:20:30] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.058 second response time [11:20:40] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.203 second response time [11:20:46] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.207 second response time [11:20:46] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.074 second response time [11:20:46] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.647 second response time [11:20:51] !log [blankeclair@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 68s [11:20:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:20:57] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.076 second response time [11:21:04] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.064 second response time [11:21:04] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.056 second response time [11:21:05] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.214 second response time [11:21:06] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.201 second response time [11:21:07] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.068 second response time [11:21:07] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.065 second response time [11:21:07] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.075 second response time [11:21:09] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.065 second response time [11:21:10] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.232 second response time [11:21:15] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.222 second response time [11:21:15] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.215 second response time [11:21:18] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.227 second response time [11:21:18] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [11:21:19] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.206 second response time [11:21:20] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [11:21:23] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.072 second response time [11:21:24] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.062 second response time [11:21:26] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.226 second response time [11:21:28] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.227 second response time [11:21:28] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.065 second response time [11:21:33] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.066 second response time [11:21:34] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.071 second response time [11:21:39] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.065 second response time [11:21:39] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.247 second response time [11:21:46] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [11:21:50] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 38% [11:21:51] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.240 second response time [11:21:51] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.214 second response time [11:21:57] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.077 second response time [11:21:59] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4273 bytes in 0.074 second response time [11:22:04] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 4224 bytes in 0.064 second response time [11:22:07] PROBLEM - db181 MariaDB on db181 is CRITICAL: Too many connections [11:22:09] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.228 second response time [11:25:55] !log reboot db181 [11:26:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:26:38] RECOVERY - db181 Puppet on db181 is OK: OK: Puppet is currently enabled, last run 27 minutes ago with 0 failures [11:26:45] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [11:26:56] RECOVERY - db181 Current Load on db181 is OK: LOAD OK - total load average: 0.75, 0.25, 0.09 [11:27:21] RECOVERY - db181 MariaDB Connections on db181 is OK: OK connection usage: 0.1%Current connections: 1 [11:27:59] RECOVERY - db181 MariaDB on db181 is OK: Uptime: 121 Threads: 1 Questions: 6236 Slow queries: 0 Opens: 1686 Open tables: 1680 Queries per second avg: 51.537 [11:30:13] @blankeclair or @pskyechology you can repool db181 [11:30:22] I don't think I can use nano on my phone [11:30:25] ok [11:30:42] !log put c4/db181 out of maint mode [11:30:45] !log [blankeclair@mwtask181] starting deploy of {'config': True} to all [11:30:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:30:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:30:55] thx [11:31:07] !log [blankeclair@mwtask181] finished deploy of {'config': True} to all - SUCCESS in 21s [11:31:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:52:52] PROBLEM - cp201 Disk Space on cp201 is WARNING: DISK WARNING - free space: / 49768MiB (10% inode=99%); [11:59:07] You can't it's just painful [12:54:46] um [12:55:03] you won't believe this, but i learned python with nano on my phone [13:16:08] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php SemanticMediaWiki:rebuildData --wiki=morerandomstuffwikibeta -v (END - exit=65280) [13:16:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:17:02] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php SemanticMediaWiki:rebuildData --wiki=morerandomstuffwikibeta -v (END - exit=0) [13:17:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:19:17] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php SemanticMediaWiki:rebuildData --wiki=gwikiwiki -v (END - exit=0) [13:19:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:19:30] I would [13:19:58] no way, it survived [13:20:42] didn't expect SMW's maintenance scripts to work better than some core ones [13:20:55] (I still have PTSD from https://phabricator.wikimedia.org/T410179) [13:38:34] PROBLEM - cp191 Disk Space on cp191 is WARNING: DISK WARNING - free space: / 49904MiB (10% inode=99%); [14:22:46] PROBLEM - cp171 Disk Space on cp171 is WARNING: DISK WARNING - free space: / 49797MiB (10% inode=99%); [14:33:08] [02ssl] 07pskyechology pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/1b9985cd12265b919e2484865d8af3e482b52953 [14:33:08] 02ssl/03main 07Skye 031b9985c T14643: Add redirect for thethaotocdowiki [16:06:23] [02ssl] 07pskyechology pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/3fc23dd42b2bc08cd8a2e1229e978d22a99688c5 [16:06:23] 02ssl/03main 07Skye 033fc23dd T14638: Update redirect to arsenalwiki [17:36:21] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:DeleteWiki --wiki=loginwiki --delete --deletewiki projectremixwiki (END - exit=0) [17:36:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:41:56] !log c1: DROP DATABASE projectremixwiki; [17:42:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:44:14] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=projectremixwikiwiki --new=projectremixwiki --user=Skye (END - exit=256) [17:44:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:44:19] had a heart attack thinking i deleted the wrong wiki lol [17:44:41] "wikiwiki" should be illegal [17:47:00] wdym cluster not found [17:48:19] oh they provided the wrong url [17:49:39] @tamq i think you should know the subdomain of your own wiki [17:49:56] https://issue-tracker.miraheze.org/T14562 vs https://projectremixroblox.miraheze.org/wiki/User:TamQ [17:57:06] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=projectremixrobloxwiki --new=projectremixwiki --user=Skye (END - exit=0) [17:57:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:07:58] [02mw-config] 07pskyechology pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/fd3c468f23930049d83c63cb9b0c4aa8dfe00127 [18:07:58] 02mw-config/03main 07Skye 03fd3c468 Add editmoderatorprotected for fischwiki… [18:08:08] !log [skye@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [18:08:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:08:32] !log [skye@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 24s [18:08:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:09:10] miraheze/mw-config - pskyechology the build passed. [18:23:22] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=projectremixwiki (END - exit=0) [18:23:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:35:22] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/f105b10268b51ccab2f38a4a4f55dc1ff00d9bf9 [18:35:22] 02ssl/03main 07WikiTideBot 03f105b10 Bot: Auto-update domain lists [18:58:13] Oh woops my bad 😭😭 [19:03:24] [02.github] 07dependabot[bot] created 03dependabot/github_actions/codecov/codecov-action-5.5.2 (+1 new commit) 13https://github.com/miraheze/.github/commit/c240adb03b43 [19:03:24] 02.github/03dependabot/github_actions/codecov/codecov-action-5.5.2 07dependabot[bot] 03c240adb Bump codecov/codecov-action from 5.5.1 to 5.5.2… [19:03:24] [02.github] 07dependabot[bot] added the label 'dependencies' to pull request #78 (Bump codecov/codecov-action from 5.5.1 to 5.5.2) 13https://github.com/miraheze/.github/pull/78 [19:03:25] [02.github] 07dependabot[bot] added the label 'github_actions' to pull request #78 (Bump codecov/codecov-action from 5.5.1 to 5.5.2) 13https://github.com/miraheze/.github/pull/78 [19:03:26] [02.github] 07dependabot[bot] opened pull request #78: Bump codecov/codecov-action from 5.5.1 to 5.5.2 (03main...03dependabot/github_actions/codecov/codecov-action-5.5.2) 13https://github.com/miraheze/.github/pull/78 [19:03:54] [02.github] 07coderabbitai[bot] commented on pull request #78: --- […] 13https://github.com/miraheze/.github/pull/78#issuecomment-3638552577 [20:04:35] [02.github] 07dependabot[bot] added the label 'dependencies' to pull request #78 (Bump codecov/codecov-action from 5.5.1 to 5.5.2) 13https://github.com/miraheze/.github/pull/78 [20:04:35] [02.github] 07dependabot[bot] added the label 'github_actions' to pull request #78 (Bump codecov/codecov-action from 5.5.1 to 5.5.2) 13https://github.com/miraheze/.github/pull/78 [20:25:09] !log [somerandomdeveloper@test151] starting deploy of {'folders': '1.44/extensions/RemoveRedlinks,1.45/extensions/RemoveRedlinks'} to test151 [20:25:10] !log [somerandomdeveloper@test151] finished deploy of {'folders': '1.44/extensions/RemoveRedlinks,1.45/extensions/RemoveRedlinks'} to test151 - SUCCESS in 0s [20:25:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:25:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:26:50] !log [somerandomdeveloper@mwtask181] starting deploy of {'folders': '1.44/extensions/RemoveRedlinks'} to all [20:26:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:13] !log [somerandomdeveloper@mwtask181] finished deploy of {'folders': '1.44/extensions/RemoveRedlinks'} to all - SUCCESS in 23s [20:27:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:27:38] !log deployed local patch for T14432 [20:27:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:33:30] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:DeleteWiki --wiki=loginwiki --delete --deletewiki abysswiki (END - exit=0) [20:33:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:39:04] !log c4: DROP DATABASE abysswiki; [20:39:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:48:39] [02mw-config] 07SomeMWDev created 03fix-smw-namespaces (+1 new commit) 13https://github.com/miraheze/mw-config/commit/14124516f6b4 [20:48:41] 02mw-config/03fix-smw-namespaces 07SomeRandomDeveloper 031412451 Fix $smwgNamespacesWithSemanticLinks not being set correctly [20:48:56] [02mw-config] 07SomeMWDev opened pull request #6208: Fix $smwgNamespacesWithSemanticLinks not being set correctly (03main...03fix-smw-namespaces) 13https://github.com/miraheze/mw-config/pull/6208 [20:49:50] miraheze/mw-config - SomeMWDev the build passed. [20:50:12] [02mw-config] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mw-config/commit/b3727fcc21c40e95bf4fd9133f97c68534963fb3 [20:50:12] 02mw-config/03main 07SomeRandomDeveloper 03b3727fc Fix $smwgNamespacesWithSemanticLinks not being set correctly (#6208)… [20:50:12] [02mw-config] 07SomeMWDev merged pull request #6208: Fix $smwgNamespacesWithSemanticLinks not being set correctly (03main...03fix-smw-namespaces) 13https://github.com/miraheze/mw-config/pull/6208 [20:50:13] [02mw-config] 07SomeMWDev 04deleted 03fix-smw-namespaces at 031412451 13https://api.github.com/repos/miraheze/mw-config/commit/1412451 [20:50:14] !log [somerandomdeveloper@test151] starting deploy of {'pull': 'config', 'config': True} to test151 [20:50:15] !log [somerandomdeveloper@test151] finished deploy of {'pull': 'config', 'config': True} to test151 - SUCCESS in 0s [20:50:17] !log [somerandomdeveloper@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [20:50:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:39] !log [somerandomdeveloper@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 22s [20:50:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:24] miraheze/mw-config - SomeMWDev the build passed. [20:51:37] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=abysswikiwiki --new=abysswiki --user=Skye (END - exit=0) [20:51:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:07] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php SemanticMediaWiki:rebuildData --wiki=gwikiwiki -v (END - exit=0) [20:52:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:37] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=abysswiki (END - exit=0) [20:52:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:31] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=athvdanwiki --new=factionalworldwiki --user=Skye (END - exit=0) [20:56:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:57:06] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=factionalworldwiki (END - exit=0) [20:57:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:00:53] !log [void@puppet181] Upgraded packages on bast181: libpng16-16t64 and pdns-recursor [21:00:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:00] RECOVERY - bast181 APT on bast181 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [21:01:08] !log [void@puppet181] Upgraded packages on bast161: libpng16-16t64 and pdns-recursor [21:01:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:20] !log [void@puppet181] Upgraded packages on cp161: libpng16-16 [21:01:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:34] !log [void@puppet181] Upgraded packages on cp201: libpng16-16 [21:01:35] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php MirahezeMagic:RenameDatabase --wiki=loginwiki --rename --old=conquerorsofthecraftwiki --new=alentiniszerwiki --user=Skye (END - exit=0) [21:01:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:46] !log [void@puppet181] Upgraded packages on db172: libpng16-16 [21:01:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:01:57] !log [void@puppet181] Upgraded packages on changeprop201: libpng16-16 [21:02:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:02:11] !log [void@puppet181] Upgraded packages on bots171: libpng16-16 [21:02:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:02:20] RECOVERY - bast161 APT on bast161 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [21:02:26] !log [void@puppet181] Upgraded packages on db151: libpng16-16 [21:02:27] RECOVERY - cp161 APT on cp161 is OK: APT OK: 118 packages available for upgrade (0 critical updates). [21:02:28] RECOVERY - db172 APT on db172 is OK: APT OK: 92 packages available for upgrade (0 critical updates). [21:02:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:02:39] RECOVERY - db151 APT on db151 is OK: APT OK: 127 packages available for upgrade (0 critical updates). [21:02:44] RECOVERY - changeprop201 APT on changeprop201 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [21:02:44] !log [void@puppet181] Upgraded packages on db201: libpng16-16t64 and pdns-recursor [21:02:45] RECOVERY - cp201 APT on cp201 is OK: APT OK: 79 packages available for upgrade (0 critical updates). [21:02:46] !log [skye@mwtask171] sudo -u www-data php /srv/mediawiki/1.44/maintenance/run.php CreateWiki:SetContainersAccess --wiki=alentiniszerwiki (END - exit=0) [21:02:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:02:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:02:57] !log [void@puppet181] Upgraded packages on db161: libpng16-16 [21:03:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:03:16] !log [void@puppet181] Upgraded packages on db192: libpng16-16t64 and pdns-recursor [21:03:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:03:29] !log [void@puppet181] Upgraded packages on cloud16: libpng16-16 [21:03:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:03:43] !log [void@puppet181] Upgraded packages on cloud17: libpng16-16 [21:03:46] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 185 packages available for upgrade (0 critical updates). [21:03:47] RECOVERY - db161 APT on db161 is OK: APT OK: 127 packages available for upgrade (0 critical updates). [21:03:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:03:55] RECOVERY - bots171 APT on bots171 is OK: APT OK: 115 packages available for upgrade (0 critical updates). [21:03:56] !log [void@puppet181] Upgraded packages on cloud15: libpng16-16 [21:04:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:04:07] !log [void@puppet181] Upgraded packages on kafka181: libpng16-16 [21:04:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:04:20] RECOVERY - kafka181 APT on kafka181 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [21:04:20] !log [void@puppet181] Upgraded packages on cp191: libpng16-16 [21:04:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:04:35] !log [void@puppet181] Upgraded packages on cp171: libpng16-16 [21:04:39] RECOVERY - db201 APT on db201 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [21:04:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:04:42] RECOVERY - cp191 APT on cp191 is OK: APT OK: 108 packages available for upgrade (0 critical updates). [21:04:48] !log [void@puppet181] Upgraded packages on eventgate181: libpng16-16 [21:04:51] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 185 packages available for upgrade (0 critical updates). [21:04:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:05:00] RECOVERY - db192 APT on db192 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [21:05:01] !log [void@puppet181] Upgraded packages on graylog161: libpng16-16 [21:05:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:05:15] !log [void@puppet181] Upgraded packages on db171: libpng16-16 [21:05:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:05:22] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 188 packages available for upgrade (0 critical updates). [21:05:23] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 114 packages available for upgrade (0 critical updates). [21:05:28] !log [void@puppet181] Upgraded packages on db182: libpng16-16 [21:05:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:05:40] !log [void@puppet181] Upgraded packages on cloud19: libpng16-16 [21:05:41] RECOVERY - cp171 APT on cp171 is OK: APT OK: 108 packages available for upgrade (0 critical updates). [21:05:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:05:54] !log [void@puppet181] Upgraded packages on db181: libpng16-16 [21:06:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:06:07] RECOVERY - db181 APT on db181 is OK: APT OK: 119 packages available for upgrade (0 critical updates). [21:06:09] !log [void@puppet181] Upgraded packages on cloud20: libpng16-16 [21:06:09] RECOVERY - db182 APT on db182 is OK: APT OK: 82 packages available for upgrade (0 critical updates). [21:06:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:06:24] !log [void@puppet181] Upgraded packages on cloud18: libpng16-16 [21:06:28] RECOVERY - cloud20 APT on cloud20 is OK: APT OK: 189 packages available for upgrade (0 critical updates). [21:06:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:06:35] !log [void@puppet181] Upgraded packages on mattermost1: libpng16-16 [21:06:39]