[00:00:54] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/a50ff9d9e69ec751d7f7e004bc4456ddf5123b34 [00:00:55] 02statichelp/03main 07WikiTideBot 03a50ff9d Bot: Auto-update Tech namespace pages 2026-04-11 00:00:52 [00:02:51] PROBLEM - puppet181 Check unit status of listdomains_github_push on puppet181 is CRITICAL: CRITICAL: Status of the systemd unit listdomains_github_push [00:30:51] RECOVERY - puppet181 Check unit status of listdomains_github_push on puppet181 is OK: OK: Status of the systemd unit listdomains_github_push [03:30:26] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:30:27] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:30:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:30:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:32:29] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:32:30] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:32:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:32:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:33:37] PROBLEM - test151 MediaWiki Rendering on test151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 6646 bytes in 0.198 second response time [03:34:33] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:34:34] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:34:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:34:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:35:37] RECOVERY - test151 MediaWiki Rendering on test151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.345 second response time [03:35:44] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:35:45] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:35:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:35:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:38:48] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:38:49] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:38:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:38:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:40:15] !log [pixldev@test151] starting deploy of {'config': True} to test151 [03:40:16] !log [pixldev@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [03:40:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:40:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [06:25:35] !log [petramagna@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php importDump --wiki=dlsitewiki --username-prefix=mgp -- dump1.xml (START) [06:25:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [06:26:02] Doing this import as the wiki bureaucrat [06:40:48] !log [petramagna@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php importDump --wiki=dlsitewiki --username-prefix=mgp -- dump1.xml (END - exit=0) [06:40:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [06:54:52] !log [petramagna@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php importDump --wiki=dlsitewiki --username-prefix=mgp -- dump2.xml (START) [06:54:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [07:05:54] !log [petramagna@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php importDump --wiki=dlsitewiki --username-prefix=mgp -- dump2.xml (END - exit=0) [07:05:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:57:17] PROBLEM - cp191 Puppet on cp191 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [16:25:16] RECOVERY - cp191 Puppet on cp191 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:12:39] PROBLEM - bast161 Current Load on bast161 is CRITICAL: LOAD CRITICAL - total load average: 4.77, 2.51, 1.09 [17:13:14] PROBLEM - bast161 APT on bast161 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [17:15:14] RECOVERY - bast161 APT on bast161 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [17:16:39] RECOVERY - bast161 Current Load on bast161 is OK: LOAD OK - total load average: 1.01, 2.82, 1.65 [18:41:48] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:41:51] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [18:41:52] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [18:41:57] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 14 backends are down. mw161 mw162 mw171 mw172 mw182 mw153 mw163 mw173 mw183 mw191 mw193 mw201 mw202 mw203 [18:42:00] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:42:01] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:42:02] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:42:06] PROBLEM - db161 SSH on db161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:42:11] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:42:16] 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 10002 milliseconds with 0 bytes received [18:42:23] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:42:39] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [18:42:43] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 14 backends are down. mw161 mw162 mw171 mw172 mw182 mw153 mw163 mw173 mw183 mw191 mw193 mw201 mw202 mw203 [18:42:49] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 14 backends are down. mw161 mw162 mw171 mw172 mw182 mw153 mw163 mw173 mw183 mw191 mw193 mw201 mw202 mw203 [18:42:59] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:42:59] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [18:43:02] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:43:10] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 296.92, 153.82, 62.37 [18:43:11] 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 10005 milliseconds with 0 bytes received [18:43:17] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [18:43:17] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 14 backends are down. mw161 mw162 mw171 mw172 mw182 mw153 mw163 mw173 mw183 mw191 mw193 mw201 mw202 mw203 [18:43:18] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 89% [18:43:24] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:43:31] 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 [18:43:31] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.013 second response time [18:43:36] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [18:43:47] PROBLEM - db161 PowerDNS Recursor on db161 is CRITICAL: CRITICAL - Plugin timed out while executing system call [18:43:49] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:43:51] 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 10006 milliseconds with 0 bytes received [18:44:02] 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 10002 milliseconds with 0 bytes received [18:44:07] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10002 milliseconds with 0 bytes received [18:44:07] RECOVERY - db161 SSH on db161 is OK: SSH OK - OpenSSH_10.0p2 (protocol 2.0) [18:44:08] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.717 second response time [18:44:11] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.053 second response time [18:44:25] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.166 second response time [18:44:39] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 3.521 second response time [18:44:57] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.236 second response time [18:44:59] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.075 second response time [18:45:00] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.182 second response time [18:45:08] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [18:45:17] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [18:45:17] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.204 second response time [18:45:18] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 15% [18:45:25] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.072 second response time [18:45:29] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [18:45:31] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.178 second response time [18:45:36] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.066 second response time [18:45:44] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [18:45:44] RECOVERY - db161 PowerDNS Recursor on db161 is OK: DNS OK: 0.062 seconds response time. db161.fsslc.wtnet returns 10.0.16.128 [18:45:46] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.197 second response time [18:45:46] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.081 second response time [18:45:49] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.235 second response time [18:45:50] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.077 second response time [18:45:57] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.068 second response time [18:45:57] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [18:46:01] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.065 second response time [18:46:01] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.066 second response time [18:46:02] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.068 second response time [18:46:02] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.074 second response time [18:46:43] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [18:46:49] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [18:56:44] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (3 critical updates). [18:56:55] PROBLEM - mem191 APT on mem191 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [18:57:20] PROBLEM - mw192 APT on mw192 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [18:58:03] PROBLEM - os162 APT on os162 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [18:58:22] PROBLEM - graylog161 APT on graylog161 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (3 critical updates). [18:58:24] PROBLEM - cp161 APT on cp161 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [18:58:34] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [18:58:35] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [18:59:43] PROBLEM - db181 APT on db181 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:00:32] PROBLEM - os202 APT on os202 is CRITICAL: APT CRITICAL: 66 packages available for upgrade (3 critical updates). [19:02:02] PROBLEM - os191 APT on os191 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:02:17] PROBLEM - ns2 APT on ns2 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:02:30] PROBLEM - cloud18 APT on cloud18 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:02:36] PROBLEM - reports171 APT on reports171 is CRITICAL: APT CRITICAL: 66 packages available for upgrade (3 critical updates). [19:02:46] PROBLEM - db151 APT on db151 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:03:00] PROBLEM - eventgate182 APT on eventgate182 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:03:07] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:03:46] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (3 critical updates). [19:04:11] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (5 critical updates). [19:04:14] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (3 critical updates). [19:04:19] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:04:23] PROBLEM - cloud20 APT on cloud20 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:04:24] PROBLEM - mw201 APT on mw201 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:04:32] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (5 critical updates). [19:04:32] PROBLEM - db192 APT on db192 is CRITICAL: APT CRITICAL: 87 packages available for upgrade (3 critical updates). [19:04:42] PROBLEM - os161 APT on os161 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:05:05] PROBLEM - mon181 APT on mon181 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (3 critical updates). [19:05:36] PROBLEM - bast181 APT on bast181 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (3 critical updates). [19:06:14] PROBLEM - ldap171 APT on ldap171 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:06:46] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:06:51] PROBLEM - cloud16 APT on cloud16 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:07:21] PROBLEM - mattermost2 APT on mattermost2 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:07:24] PROBLEM - swiftobject211 APT on swiftobject211 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:07:26] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:07:37] PROBLEM - prometheus151 APT on prometheus151 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (3 critical updates). [19:07:48] PROBLEM - cloud17 APT on cloud17 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:08:03] PROBLEM - mem201 APT on mem201 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:09:00] PROBLEM - matomo151 APT on matomo151 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:09:31] PROBLEM - cp201 APT on cp201 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:09:41] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:10:30] PROBLEM - changeprop202 APT on changeprop202 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:11:00] PROBLEM - mw202 APT on mw202 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:11:12] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:11:12] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:11:29] PROBLEM - mw203 APT on mw203 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:11:30] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:11:36] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:11:39] PROBLEM - db172 APT on db172 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:11:52] PROBLEM - cp171 APT on cp171 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:12:25] PROBLEM - rdb191 APT on rdb191 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:12:28] PROBLEM - bast161 APT on bast161 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (3 critical updates). [19:12:42] PROBLEM - puppet181 APT on puppet181 is CRITICAL: APT CRITICAL: 70 packages available for upgrade (3 critical updates). [19:13:16] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (5 critical updates). [19:13:20] PROBLEM - swiftobject191 APT on swiftobject191 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (3 critical updates). [19:13:41] PROBLEM - llm191 APT on llm191 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (3 critical updates). [19:13:55] PROBLEM - swiftobject201 APT on swiftobject201 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (3 critical updates). [19:14:19] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 1.17, 1.44, 11.70 [19:14:21] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:14:41] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (5 critical updates). [19:14:44] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (5 critical updates). [19:14:46] PROBLEM - phorge171 APT on phorge171 is CRITICAL: APT CRITICAL: 66 packages available for upgrade (3 critical updates). [19:14:54] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:15:15] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:15:57] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 68 packages available for upgrade (3 critical updates). [19:16:47] PROBLEM - db161 APT on db161 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:17:36] PROBLEM - ns1 APT on ns1 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:18:19] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 1.07, 1.17, 9.24 [19:18:36] PROBLEM - os201 APT on os201 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:18:38] PROBLEM - mem151 APT on mem151 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:18:54] PROBLEM - os151 APT on os151 is CRITICAL: APT CRITICAL: 64 packages available for upgrade (3 critical updates). [19:19:02] PROBLEM - mw193 APT on mw193 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:19:10] PROBLEM - cloud15 APT on cloud15 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:20:33] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:20:38] PROBLEM - db171 APT on db171 is CRITICAL: APT CRITICAL: 74 packages available for upgrade (3 critical updates). [19:20:51] PROBLEM - cloud21 APT on cloud21 is CRITICAL: APT CRITICAL: 93 packages available for upgrade (3 critical updates). [19:21:57] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:22:20] PROBLEM - db201 APT on db201 is CRITICAL: APT CRITICAL: 87 packages available for upgrade (3 critical updates). [19:23:08] PROBLEM - kafka182 APT on kafka182 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (3 critical updates). [19:23:15] PROBLEM - mw191 APT on mw191 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (5 critical updates). [19:23:19] PROBLEM - db182 APT on db182 is CRITICAL: APT CRITICAL: 80 packages available for upgrade (3 critical updates). [19:24:53] PROBLEM - cloud19 APT on cloud19 is CRITICAL: APT CRITICAL: 94 packages available for upgrade (3 critical updates). [19:25:48] PROBLEM - cp191 APT on cp191 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [19:26:04] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 65 packages available for upgrade (3 critical updates). [22:03:54] !log [void@puppet181] Upgraded packages on bots171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:03:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:04:07] !log [void@puppet181] Upgraded packages on cp161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:04:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:04:21] !log [void@puppet181] Upgraded packages on bast161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:04:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:04:24] RECOVERY - cp161 APT on cp161 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:04:33] !log [void@puppet181] Upgraded packages on cloud21: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:04:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:04:40] RECOVERY - bots171 APT on bots171 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:04:48] !log [void@puppet181] Upgraded packages on changeprop202: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:04:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:04:51] RECOVERY - cloud21 APT on cloud21 is OK: APT OK: 90 packages available for upgrade (0 critical updates). [22:05:03] !log [void@puppet181] Upgraded packages on cp171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:05:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:05:17] !log [void@puppet181] Upgraded packages on db161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:05:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:05:31] !log [void@puppet181] Upgraded packages on db171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:05:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:05:44] RECOVERY - db161 APT on db161 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [22:05:44] !log [void@puppet181] Upgraded packages on cloud15: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:05:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:05:59] !log [void@puppet181] Upgraded packages on db181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:06:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:06:09] RECOVERY - cp171 APT on cp171 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:06:14] !log [void@puppet181] Upgraded packages on db151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:06:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:06:17] RECOVERY - bast161 APT on bast161 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [22:06:25] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:06:27] !log [void@puppet181] Upgraded packages on db172: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:06:28] RECOVERY - changeprop202 APT on changeprop202 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:06:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:06:41] !log [void@puppet181] Upgraded packages on cloud19: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:06:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:06:52] RECOVERY - cloud19 APT on cloud19 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:06:54] RECOVERY - db151 APT on db151 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [22:06:56] !log [void@puppet181] Upgraded packages on cloud20: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:06:56] RECOVERY - db171 APT on db171 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [22:06:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:07:09] !log [void@puppet181] Upgraded packages on cloud16: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:07:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:07:14] RECOVERY - cloud20 APT on cloud20 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:07:20] RECOVERY - db172 APT on db172 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [22:07:25] !log [void@puppet181] Upgraded packages on graylog161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:07:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:07:41] RECOVERY - db181 APT on db181 is OK: APT OK: 71 packages available for upgrade (0 critical updates). [22:07:41] !log [void@puppet181] Upgraded packages on cp191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:07:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:07:55] !log [void@puppet181] Upgraded packages on cloud17: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:07:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:08:14] !log [void@puppet181] Upgraded packages on db192: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:08:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:08:21] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [22:08:29] !log [void@puppet181] Upgraded packages on bast181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:08:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:08:40] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:08:48] !log [void@puppet181] Upgraded packages on db201: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:08:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:08:52] RECOVERY - db201 APT on db201 is OK: APT OK: 84 packages available for upgrade (0 critical updates). [22:08:56] RECOVERY - cp191 APT on cp191 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:09:03] !log [void@puppet181] Upgraded packages on db182: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:09:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:09:11] RECOVERY - db192 APT on db192 is OK: APT OK: 84 packages available for upgrade (0 critical updates). [22:09:17] RECOVERY - db182 APT on db182 is OK: APT OK: 77 packages available for upgrade (0 critical updates). [22:09:19] !log [void@puppet181] Upgraded packages on cloud18: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:09:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:09:34] !log [void@puppet181] Upgraded packages on eventgate182: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:09:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:09:46] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:09:50] !log [void@puppet181] Upgraded packages on cp201: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:09:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:10:01] !log [void@puppet181] Upgraded packages on mattermost2: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:10:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:10:10] RECOVERY - bast181 APT on bast181 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [22:10:15] !log [void@puppet181] Upgraded packages on matomo151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:10:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:10:28] RECOVERY - cloud18 APT on cloud18 is OK: APT OK: 91 packages available for upgrade (0 critical updates). [22:10:31] !log [void@puppet181] Upgraded packages on mem161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:10:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:10:50] !log [void@puppet181] Upgraded packages on kafka182: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:10:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:10:59] RECOVERY - eventgate182 APT on eventgate182 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:11:00] RECOVERY - matomo151 APT on matomo151 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:11:04] !log [void@puppet181] Upgraded packages on mem151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:11:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:11:20] !log [void@puppet181] Upgraded packages on mem201: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:11:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:11:23] RECOVERY - cp201 APT on cp201 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:11:33] RECOVERY - kafka182 APT on kafka182 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [22:11:35] !log [void@puppet181] Upgraded packages on llm191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:11:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:11:40] RECOVERY - llm191 APT on llm191 is OK: APT OK: 64 packages available for upgrade (0 critical updates). [22:11:45] RECOVERY - mattermost2 APT on mattermost2 is OK: APT OK: 62 packages available for upgrade (0 critical updates). [22:11:51] !log [void@puppet181] Upgraded packages on mem191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:11:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:12:08] !log [void@puppet181] Upgraded packages on mw151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:12:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:12:17] RECOVERY - mem161 APT on mem161 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:12:25] !log [void@puppet181] Upgraded packages on mw152: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:12:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:12:33] RECOVERY - mw151 APT on mw151 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:12:35] RECOVERY - mem151 APT on mem151 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:12:42] !log [void@puppet181] Upgraded packages on mw163: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:12:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:12:52] RECOVERY - mem191 APT on mem191 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:12:56] RECOVERY - mem201 APT on mem201 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:12:57] !log [void@puppet181] Upgraded packages on mon181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:12:59] RECOVERY - mon181 APT on mon181 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [22:13:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:13:14] !log [void@puppet181] Upgraded packages on mw153: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:13:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:13:31] !log [void@puppet181] Upgraded packages on mw173: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:13:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:13:49] !log [void@puppet181] Upgraded packages on mw172: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:13:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:13:57] RECOVERY - mw153 APT on mw153 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:14:06] !log [void@puppet181] Upgraded packages on mw171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:14:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:14:16] RECOVERY - mw152 APT on mw152 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:14:24] !log [void@puppet181] Upgraded packages on mw161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:14:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:14:29] RECOVERY - mw163 APT on mw163 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:14:33] RECOVERY - mw171 APT on mw171 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:14:42] !log [void@puppet181] Upgraded packages on mw162: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:14:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:14:52] RECOVERY - mw173 APT on mw173 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:14:56] RECOVERY - mw172 APT on mw172 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:15:00] !log [void@puppet181] Upgraded packages on mw191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:15:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:15:17] !log [void@puppet181] Upgraded packages on mw182: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:15:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:15:28] RECOVERY - mw161 APT on mw161 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:15:36] !log [void@puppet181] Upgraded packages on mw192: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:15:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:15:53] !log [void@puppet181] Upgraded packages on mw193: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:15:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:16:12] !log [void@puppet181] Upgraded packages on mw181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:16:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:16:31] !log [void@puppet181] Upgraded packages on mw183: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:16:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:16:37] RECOVERY - mw162 APT on mw162 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:16:46] !log [void@puppet181] Upgraded packages on ldap171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:16:46] RECOVERY - mw182 APT on mw182 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:16:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:16:56] RECOVERY - mw191 APT on mw191 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:16:58] RECOVERY - mw193 APT on mw193 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:17:04] !log [void@puppet181] Upgraded packages on mw201: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:17:04] RECOVERY - mw181 APT on mw181 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:17:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:17:17] RECOVERY - mw192 APT on mw192 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:17:22] !log [void@puppet181] Upgraded packages on mw202: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:17:23] RECOVERY - mw183 APT on mw183 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:17:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:17:38] !log [void@puppet181] Upgraded packages on mwtask161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:17:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:17:55] !log [void@puppet181] Upgraded packages on mwtask151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:17:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:18:10] RECOVERY - ldap171 APT on ldap171 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:18:13] !log [void@puppet181] Upgraded packages on mw203: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:18:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:18:30] !log [void@puppet181] Upgraded packages on mwtask171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:18:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:18:40] RECOVERY - mwtask161 APT on mwtask161 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [22:18:45] !log [void@puppet181] Upgraded packages on os161: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:18:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:18:58] RECOVERY - mw202 APT on mw202 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:19:00] !log [void@puppet181] Upgraded packages on ns1: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:19:00] RECOVERY - mw201 APT on mw201 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:19:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:19:07] RECOVERY - mwtask151 APT on mwtask151 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [22:19:15] RECOVERY - mwtask171 APT on mwtask171 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [22:19:16] !log [void@puppet181] Upgraded packages on os151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:19:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:19:27] RECOVERY - mw203 APT on mw203 is OK: APT OK: 66 packages available for upgrade (0 critical updates). [22:19:30] !log [void@puppet181] Upgraded packages on phorge171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:19:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:19:34] RECOVERY - ns1 APT on ns1 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:19:44] !log [void@puppet181] Upgraded packages on prometheus151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:19:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:20:04] !log [void@puppet181] Upgraded packages on mwtask181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-dev, libgdk-pixbuf-2.0-0, libgdk-pixbuf2.0-bin, and gir1.2-gdkpixbuf-2.0 [22:20:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:20:12] RECOVERY - os151 APT on os151 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:20:17] RECOVERY - mwtask181 APT on mwtask181 is OK: APT OK: 70 packages available for upgrade (0 critical updates). [22:20:19] !log [void@puppet181] Upgraded packages on puppet181: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:20:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:20:36] !log [void@puppet181] Upgraded packages on os162: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:20:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:20:40] RECOVERY - os161 APT on os161 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:20:41] RECOVERY - phorge171 APT on phorge171 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [22:20:43] RECOVERY - puppet181 APT on puppet181 is OK: APT OK: 67 packages available for upgrade (0 critical updates). [22:20:51] !log [void@puppet181] Upgraded packages on reports171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:20:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:21:07] !log [void@puppet181] Upgraded packages on os201: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:21:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:21:23] !log [void@puppet181] Upgraded packages on os191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:21:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:21:34] RECOVERY - prometheus151 APT on prometheus151 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [22:21:46] !log [void@puppet181] Upgraded packages on os202: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:21:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:22:03] RECOVERY - os162 APT on os162 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:22:04] !log [void@puppet181] Upgraded packages on rdb191: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:22:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:22:19] !log [void@puppet181] Upgraded packages on swiftobject151: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:22:19] RECOVERY - os191 APT on os191 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:22:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:22:22] RECOVERY - rdb191 APT on rdb191 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:22:29] RECOVERY - os202 APT on os202 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [22:22:34] RECOVERY - os201 APT on os201 is OK: APT OK: 61 packages available for upgrade (0 critical updates). [22:22:34] !log [void@puppet181] Upgraded packages on swiftac171: libgdk-pixbuf2.0-common, libgdk-pixbuf-2.0-0, and libgdk-pixbuf2.0-bin [22:22:36] RECOVERY - reports171 APT on reports171 is OK: APT OK: 63 packages available for upgrade (0 critical updates). [22:22:36]