[02:17:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 5 backends are down. mw161 mw181 mw182 mw153 mw183 [02:19:05] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 2 backends are down. mw153 mw154 [02:21:05] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [02:21:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [02:57:44] [02dns] 07BlankEclair opened pull request 03#615: T12577: Update _atproto.pizzatower.wiki. - 13https://github.com/miraheze/dns/pull/615 [02:58:13] [02dns] 07Universal-Omega closed pull request 03#615: T12577: Update _atproto.pizzatower.wiki. - 13https://github.com/miraheze/dns/pull/615 [02:58:15] [02dns] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/dns/compare/0a85d0f9d0cb...9e68fb66a42f [02:58:16] [02dns] 07BlankEclair 039e68fb6 - T12577: Update _atproto.pizzatower.wiki. (#615) [03:20:39] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [03:49:35] RECOVERY - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [05:21:47] [02test_docs] 07Universal-Omega created branch 03master - 13https://github.com/miraheze/test_docs [05:21:48] [02test_docs] 07Universal-Omega pushed 031 commit to 03master [+1/-0/±0] 13https://github.com/miraheze/test_docs/commit/dcdbdcde16a2 [05:21:50] [02test_docs] 07Universal-Omega 03dcdbdcd - Create README.md [05:35:21] [02test_docs] 07Universal-Omega pushed 031 commit to 03master [+411/-0/±0] 13https://github.com/miraheze/test_docs/compare/dcdbdcde16a2...a0db24aadfa9 [05:35:21] [02test_docs] 07universalomega 03a0db24a - Auto-update Tech namespace pages 2024-09-13 05:33:52.412098 [05:49:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 4 backends are down. mw151 mw152 mw182 mw164 [05:51:05] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 3 backends are down. mw161 mw162 mw183 [05:53:05] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [05:53:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [06:45:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 21767MiB (9% inode=99%); [06:46:55] PROBLEM - os161 Disk Space on os161 is WARNING: DISK WARNING - free space: / 21801MiB (9% inode=99%); [06:49:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 1 backends are down. mw154 [06:51:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [06:53:29] RECOVERY - os151 Disk Space on os151 is OK: DISK OK - free space: / 26330MiB (11% inode=99%); [06:54:55] RECOVERY - os161 Disk Space on os161 is OK: DISK OK - free space: / 26411MiB (11% inode=99%); [07:20:40] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [07:21:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 24111MiB (10% inode=99%); [07:23:29] RECOVERY - os151 Disk Space on os151 is OK: DISK OK - free space: / 25417MiB (11% inode=99%); [07:35:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 24266MiB (10% inode=99%); [07:38:55] PROBLEM - os161 Disk Space on os161 is WARNING: DISK WARNING - free space: / 24167MiB (10% inode=99%); [07:40:55] RECOVERY - os161 Disk Space on os161 is OK: DISK OK - free space: / 25290MiB (11% inode=99%); [07:41:29] RECOVERY - os151 Disk Space on os151 is OK: DISK OK - free space: / 25051MiB (11% inode=99%); [07:46:12] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 4 backends are down. mw171 mw182 mw154 mw173 [07:46:18] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 5 backends are down. mw151 mw161 mw163 mw164 mw174 [07:48:55] PROBLEM - os161 Disk Space on os161 is WARNING: DISK WARNING - free space: / 24050MiB (10% inode=99%); [07:49:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 23923MiB (10% inode=99%); [07:49:39] RECOVERY - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [07:52:55] RECOVERY - os161 Disk Space on os161 is OK: DISK OK - free space: / 24763MiB (11% inode=99%); [07:53:29] RECOVERY - os151 Disk Space on os151 is OK: DISK OK - free space: / 24539MiB (11% inode=99%); [07:54:06] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [07:54:14] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [07:57:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 23903MiB (10% inode=99%); [07:58:01] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 3 backends are down. mw174 mw183 mw184 [07:58:55] PROBLEM - os161 Disk Space on os161 is WARNING: DISK WARNING - free space: / 23994MiB (10% inode=99%); [08:00:10] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 4 backends are down. mw152 mw172 mw182 mw153 [08:06:49] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:08:46] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.388 second response time [08:09:31] PROBLEM - mw164 HTTPS on mw164 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:11:26] RECOVERY - mw164 HTTPS on mw164 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.072 second response time [08:12:00] [Grafana] FIRING: Some MediaWiki Appservers are running out of PHP-FPM workers. https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [08:14:38] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.009 second response time [08:14:56] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:14:58] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:16:38] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 3.299 second response time [08:16:52] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.082 second response time [08:16:53] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.405 second response time [08:17:39] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:38] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4010 bytes in 0.067 second response time [08:20:47] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [08:21:41] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [08:21:59] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [08:32:30] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 2 backends are down. mw152 mw162 [08:34:28] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [08:51:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 7 backends are down. mw162 mw171 mw172 mw181 mw182 mw174 mw183 [08:52:12] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 6 backends are down. mw161 mw162 mw171 mw181 mw174 mw183 [09:06:34] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:08:30] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.420 second response time [09:08:38] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [09:08:55] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:09:10] are the servers having a seizure [09:09:13] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:09:49] mayhaps [09:10:50] nooo the last bastion has fallen [09:10:54] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.432 second response time [09:11:04] \:D [09:11:11] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.403 second response time [09:12:41] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.440 second response time [09:13:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [09:13:54] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [09:17:00] [Grafana] RESOLVED: PHP-FPM Worker Usage High https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [09:18:48] RECOVERY - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [09:25:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 7 backends are down. mw161 mw162 mw171 mw181 mw182 mw163 mw183 [09:25:43] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 6 backends are down. mw161 mw162 mw182 mw163 mw164 mw183 [09:27:41] and there it goes again [09:29:39] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [09:29:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [09:37:31] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 3 backends are down. mw182 mw173 mw174 [09:37:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 2 backends are down. mw181 mw182 [09:40:02] PROBLEM - mw154 MediaWiki Rendering on mw154 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:40:31] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:42:01] RECOVERY - mw154 MediaWiki Rendering on mw154 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.383 second response time [09:42:26] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.093 second response time [09:42:40] PROBLEM - mw174 MediaWiki Rendering on mw174 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [09:42:53] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [09:43:51] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:44:07] PROBLEM - mw164 HTTPS on mw164 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:44:39] RECOVERY - mw174 MediaWiki Rendering on mw174 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.340 second response time [09:45:31] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:45:49] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.118 second response time [09:46:13] RECOVERY - mw164 HTTPS on mw164 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 6.231 second response time [09:46:48] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 5.378 second response time [09:47:00] [Grafana] FIRING: Some MediaWiki Appservers are running out of PHP-FPM workers. https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [09:47:27] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.322 second response time [09:47:41] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:48:51] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:49:43] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10001 milliseconds with 0 bytes received [09:49:48] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 8.859 second response time [09:50:49] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.520 second response time [09:53:25] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [09:53:26] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10001 milliseconds with 0 bytes received [09:55:21] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.075 second response time [09:55:26] RECOVERY - cp37 HTTPS on cp37 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4010 bytes in 5.171 second response time [09:55:38] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 3814 bytes in 0.086 second response time [09:55:55] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:56:43] PROBLEM - mw174 MediaWiki Rendering on mw174 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.015 second response time [09:56:52] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [09:57:50] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.328 second response time [09:57:53] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.035 second response time [09:58:43] RECOVERY - mw174 MediaWiki Rendering on mw174 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 1.233 second response time [09:59:51] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.515 second response time [10:00:55] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.369 second response time [10:03:10] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [10:03:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [10:07:00] [Grafana] RESOLVED: PHP-FPM Worker Usage High https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [10:11:05] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 4 backends are down. mw162 mw172 mw181 mw154 [10:11:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 4 backends are down. mw151 mw172 mw182 mw174 [10:15:05] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [10:17:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [10:20:39] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [10:23:05] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 8 backends are down. mw151 mw152 mw171 mw172 mw153 mw154 mw163 mw184 [10:23:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 6 backends are down. mw151 mw152 mw182 mw153 mw163 mw183 [10:26:18] PROBLEM - mw184 MediaWiki Rendering on mw184 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:27:05] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [10:28:15] RECOVERY - mw184 MediaWiki Rendering on mw184 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.384 second response time [10:31:05] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 3 backends are down. mw152 mw161 mw163 [10:33:55] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.015 second response time [10:37:00] [Grafana] FIRING: Some MediaWiki Appservers are running out of PHP-FPM workers. https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [10:39:48] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 7.706 second response time [10:46:23] PROBLEM - mw184 MediaWiki Rendering on mw184 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.022 second response time [10:47:26] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:48:20] RECOVERY - mw184 MediaWiki Rendering on mw184 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.425 second response time [10:49:34] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 9.530 second response time [10:49:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [10:53:05] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [11:01:41] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 3 backends are down. mw162 mw153 mw183 [11:04:45] !log deployed an ASN challenge [11:04:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:05:41] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [11:07:00] [Grafana] RESOLVED: PHP-FPM Worker Usage High https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [11:18:38] RECOVERY - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [12:09:29] PROBLEM - os151 Disk Space on os151 is CRITICAL: DISK CRITICAL - free space: / 12176MiB (5% inode=99%); [12:22:27] PROBLEM - ping6 on ns2 is CRITICAL: PING CRITICAL - Packet loss = 16%, RTA = 134.85 ms [12:23:29] PROBLEM - os151 Disk Space on os151 is WARNING: DISK WARNING - free space: / 16493MiB (7% inode=99%); [12:24:29] RECOVERY - ping6 on ns2 is OK: PING OK - Packet loss = 0%, RTA = 134.34 ms [13:02:53] PROBLEM - neurologiahpm.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'neurologiahpm.com' expires in 15 day(s) (Sun 29 Sep 2024 12:37:53 PM GMT +0000). [13:03:04] [02ssl] 07WikiTideSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/cfb774dafd7b...85ea04f02716 [13:03:05] [02ssl] 07WikiTideSSLBot 0385ea04f - Bot: Update SSL cert for neurologiahpm.com [13:32:16] RECOVERY - neurologiahpm.com - LetsEncrypt on sslhost is OK: OK - Certificate 'neurologiahpm.com' will expire on Thu 12 Dec 2024 12:04:28 PM GMT +0000. [15:16:41] PROBLEM - ping6 on ns2 is CRITICAL: PING CRITICAL - Packet loss = 16%, RTA = 134.34 ms [15:18:44] RECOVERY - ping6 on ns2 is OK: PING OK - Packet loss = 0%, RTA = 134.39 ms [16:36:14] !log [agent@mwtask181] starting deploy of {'l10n': True, 'force': True, 'versions': '1.42'} to all [16:36:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:47:13] !log [agent@mwtask181] finished deploy of {'l10n': True, 'force': True, 'versions': '1.42'} to all - SUCCESS in 659s [16:47:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:50:39] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [17:19:38] RECOVERY - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [17:49:14] [02CreateWiki] 07AgentIsai created branch 03raidarr-ideas - 13https://github.com/miraheze/CreateWiki [17:49:17] [02CreateWiki] 07AgentIsai created branch 03raidarr-ideas 13https://github.com/miraheze/CreateWiki/commit/8430ea765fae84ea4a5b20accb1cb172fbfb39cb [17:49:36] [02CreateWiki] 07AgentIsai pushed 031 commit to 03raidarr-ideas [+0/-0/±5] 13https://github.com/miraheze/CreateWiki/compare/8430ea765fae...0f55c1321b87 [17:49:39] [02CreateWiki] 07AgentIsai 030f55c13 - Implement some ideas from Raidarr [17:52:50] [02CreateWiki] 07AgentIsai opened pull request 03#548: Changes to CreateWiki workflow - 13https://github.com/miraheze/CreateWiki/pull/548 [17:52:58] [02CreateWiki] 07coderabbitai[bot] commented on pull request 03#548: Changes to CreateWiki workflow - 13https://github.com/miraheze/CreateWiki/pull/548#issuecomment-2349667353 [17:56:20] miraheze/CreateWiki - AgentIsai the build has errored. [18:02:06] [02CreateWiki] 07AgentIsai pushed 031 commit to 03raidarr-ideas [+0/-0/±2] 13https://github.com/miraheze/CreateWiki/compare/0f55c1321b87...a62f0fd8c954 [18:02:09] [02CreateWiki] 07AgentIsai 03a62f0fd - Correct syntax + i18n [18:02:12] [02CreateWiki] 07AgentIsai synchronize pull request 03#548: Changes to CreateWiki workflow - 13https://github.com/miraheze/CreateWiki/pull/548 [18:05:50] miraheze/CreateWiki - AgentIsai the build has errored. [18:12:43] [02CreateWiki] 07AgentIsai pushed 031 commit to 03raidarr-ideas [+0/-0/±1] 13https://github.com/miraheze/CreateWiki/compare/a62f0fd8c954...63b6293a65b1 [18:12:46] [02CreateWiki] 07AgentIsai 0363b6293 - Fix parameters [18:12:47] [02CreateWiki] 07AgentIsai synchronize pull request 03#548: Changes to CreateWiki workflow - 13https://github.com/miraheze/CreateWiki/pull/548 [18:16:01] miraheze/CreateWiki - AgentIsai the build has errored. [18:22:53] [02CreateWiki] 07AgentIsai pushed 031 commit to 03raidarr-ideas [+0/-0/±1] 13https://github.com/miraheze/CreateWiki/compare/63b6293a65b1...ffa0ce826a13 [18:22:54] [02CreateWiki] 07AgentIsai 03ffa0ce8 - Fix Message declaration [18:22:57] [02CreateWiki] 07AgentIsai synchronize pull request 03#548: Changes to CreateWiki workflow - 13https://github.com/miraheze/CreateWiki/pull/548 [18:27:15] miraheze/CreateWiki - AgentIsai the build has errored. [18:28:49] !log [agent@test151] starting deploy of {'folders': '1.42/extensions/CreateWiki'} to test151 [18:28:51] !log [agent@test151] finished deploy of {'folders': '1.42/extensions/CreateWiki'} to test151 - SUCCESS in 0s [18:28:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:28:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:02:51] !log [agent@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/maintenance/setContainersAccess.php --wiki=deltacablewiki (END - exit=256) [19:02:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:02:57] !log [agent@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/maintenance/setContainerAccess.php --wiki=deltacablewiki (END - exit=256) [19:03:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:03:14] !log [agent@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/extensions/CreateWiki/maintenance/setContainerAccess.php --wiki=deltacablewiki (END - exit=256) [19:03:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:03:22] !log [agent@mwtask181] sudo -u www-data php /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/extensions/CreateWiki/maintenance/setContainersAccess.php --wiki=deltacablewiki (END - exit=0) [19:03:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:03:53] !log [agent@mwtask181] sudo -u www-data /usr/local/bin/foreachwikiindblist /srv/mediawiki/cache/databases.json /srv/mediawiki/1.42/maintenance/run.php /srv/mediawiki/1.42/extensions/CreateWiki/maintenance/setContainersAccess.php (START) [19:03:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:33:55] [02test_docs] 07Universal-Omega pushed 032 commits to 03master [+0/-0/±820] 13https://github.com/miraheze/test_docs/compare/a0db24aadfa9...6e6773f7e5f8 [19:33:56] [02test_docs] 07universalomega 037518287 - Auto-update Tech namespace pages 2024-09-13 17:15:27.392589 [19:33:59] [02test_docs] 07universalomega 036e6773f - Auto-update Tech namespace pages 2024-09-13 19:33:28.156790 [19:48:47] PROBLEM - mwtask161 APT on mwtask161 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:48:53] PROBLEM - mw183 APT on mw183 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:48:56] PROBLEM - db172 APT on db172 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (2 critical updates). [19:49:11] PROBLEM - swiftac171 APT on swiftac171 is CRITICAL: APT CRITICAL: 57 packages available for upgrade (2 critical updates). [19:49:13] PROBLEM - ldap171 APT on ldap171 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (2 critical updates). [19:49:13] PROBLEM - swiftobject151 APT on swiftobject151 is CRITICAL: APT CRITICAL: 70 packages available for upgrade (2 critical updates). [19:49:44] PROBLEM - swiftobject161 APT on swiftobject161 is CRITICAL: APT CRITICAL: 70 packages available for upgrade (2 critical updates). [19:50:41] PROBLEM - mwtask151 APT on mwtask151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:50:47] PROBLEM - db181 APT on db181 is CRITICAL: APT CRITICAL: 76 packages available for upgrade (2 critical updates). [19:51:13] PROBLEM - cp36 APT on cp36 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (2 critical updates). [19:52:41] PROBLEM - eventgate181 APT on eventgate181 is CRITICAL: APT CRITICAL: 60 packages available for upgrade (2 critical updates). [19:53:16] PROBLEM - swiftobject171 APT on swiftobject171 is CRITICAL: APT CRITICAL: 70 packages available for upgrade (2 critical updates). [19:54:50] PROBLEM - ns1 APT on ns1 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:54:53] PROBLEM - jobchron171 APT on jobchron171 is CRITICAL: APT CRITICAL: 77 packages available for upgrade (2 critical updates). [19:55:01] PROBLEM - bots171 APT on bots171 is CRITICAL: APT CRITICAL: 83 packages available for upgrade (2 critical updates). [19:55:06] PROBLEM - mw152 APT on mw152 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:55:43] PROBLEM - swiftproxy161 APT on swiftproxy161 is CRITICAL: APT CRITICAL: 57 packages available for upgrade (2 critical updates). [19:55:53] PROBLEM - test151 APT on test151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:56:29] PROBLEM - mw181 APT on mw181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:57:28] PROBLEM - rdb151 APT on rdb151 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (2 critical updates). [19:57:30] PROBLEM - swiftproxy171 APT on swiftproxy171 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (2 critical updates). [19:57:46] PROBLEM - graphite151 APT on graphite151 is CRITICAL: APT CRITICAL: 60 packages available for upgrade (2 critical updates). [19:57:49] PROBLEM - cloud18 APT on cloud18 is CRITICAL: APT CRITICAL: 119 packages available for upgrade (2 critical updates). [19:57:54] PROBLEM - reports171 APT on reports171 is CRITICAL: APT CRITICAL: 79 packages available for upgrade (2 critical updates). [19:57:57] PROBLEM - kafka181 APT on kafka181 is CRITICAL: APT CRITICAL: 53 packages available for upgrade (2 critical updates). [19:58:10] PROBLEM - bast181 APT on bast181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:58:41] PROBLEM - matomo151 APT on matomo151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:59:03] PROBLEM - mw182 APT on mw182 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [19:59:11] [02test_docs] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±10] 13https://github.com/miraheze/test_docs/compare/6e6773f7e5f8...2b5f66fc6ffb [19:59:12] [02test_docs] 07universalomega 032b5f66f - Auto-update Tech namespace pages 2024-09-13 19:58:50.735918 [20:00:01] PROBLEM - db171 APT on db171 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (2 critical updates). [20:00:03] PROBLEM - os161 APT on os161 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (2 critical updates). [20:00:12] PROBLEM - swiftobject181 APT on swiftobject181 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (2 critical updates). [20:00:21] PROBLEM - db161 APT on db161 is CRITICAL: APT CRITICAL: 75 packages available for upgrade (2 critical updates). [20:00:58] PROBLEM - mem161 APT on mem161 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:01:03] PROBLEM - graylog161 APT on graylog161 is CRITICAL: APT CRITICAL: 71 packages available for upgrade (2 critical updates). [20:01:13] PROBLEM - cp37 APT on cp37 is CRITICAL: APT CRITICAL: 67 packages available for upgrade (2 critical updates). [20:01:14] PROBLEM - phorge171 APT on phorge171 is CRITICAL: APT CRITICAL: 69 packages available for upgrade (2 critical updates). [20:01:18] PROBLEM - bast161 APT on bast161 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:01:37] PROBLEM - puppet181 APT on puppet181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:02:23] PROBLEM - cloud16 APT on cloud16 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:02:36] PROBLEM - cloud17 APT on cloud17 is CRITICAL: APT CRITICAL: 118 packages available for upgrade (2 critical updates). [20:03:35] PROBLEM - mw163 APT on mw163 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:04:13] PROBLEM - db182 APT on db182 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:04:26] PROBLEM - mw154 APT on mw154 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:04:37] PROBLEM - mem151 APT on mem151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:04:52] PROBLEM - mwtask181 APT on mwtask181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:05:02] PROBLEM - os151 APT on os151 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (2 critical updates). [20:05:27] PROBLEM - mw151 APT on mw151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:06:11] PROBLEM - mw164 APT on mw164 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:06:57] PROBLEM - cloud15 APT on cloud15 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:09:02] PROBLEM - mw184 APT on mw184 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:09:11] PROBLEM - mw162 APT on mw162 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:09:57] PROBLEM - mwtask171 APT on mwtask171 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:10:42] PROBLEM - os162 APT on os162 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (2 critical updates). [20:11:05] PROBLEM - mw161 APT on mw161 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:13:35] !log DELETED and DROPPED - https://issue-tracker.miraheze.org/P514 https://issue-tracker.miraheze.org/P515 https://issue-tracker.miraheze.org/P516 https://issue-tracker.miraheze.org/P517 https://issue-tracker.miraheze.org/P518 [20:13:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:13:41] PROBLEM - mw174 APT on mw174 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:14:38] PROBLEM - mw173 APT on mw173 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:14:45] PROBLEM - mattermost1 APT on mattermost1 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:14:53] PROBLEM - ns2 APT on ns2 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:16:54] PROBLEM - prometheus151 APT on prometheus151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:17:00] PROBLEM - mw171 APT on mw171 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:17:05] PROBLEM - mw153 APT on mw153 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:18:47] PROBLEM - mon181 APT on mon181 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:19:05] PROBLEM - db151 APT on db151 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:19:29] PROBLEM - mw172 APT on mw172 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [20:32:47] [02test_docs] 07Universal-Omega pushed 031 commit to 03master [+0/-27/±1] 13https://github.com/miraheze/test_docs/compare/2b5f66fc6ffb...c460b462e4ac [20:32:50] [02test_docs] 07universalomega 03c460b46 - Auto-update Tech namespace pages 2024-09-13 20:32:26.156492 [20:48:33] !log [void@puppet181] Upgraded packages git, and git-man on bots171 [20:48:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:48:46] !log [void@puppet181] Upgraded packages git, and git-man on cp36 [20:48:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:49:00] !log [void@puppet181] Upgraded packages git, and git-man on db151 [20:49:04] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:49:05] RECOVERY - db151 APT on db151 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:49:11] RECOVERY - cp36 APT on cp36 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [20:49:13] !log [void@puppet181] Upgraded packages git, and git-man on db161 [20:49:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:49:27] !log [void@puppet181] Upgraded packages git, and git-man on cloud15 [20:49:31] RECOVERY - bots171 APT on bots171 is OK: APT OK: 81 packages available for upgrade (0 critical updates). [20:49:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:49:40] !log [void@puppet181] Upgraded packages git, and git-man on matomo151 [20:49:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:49:54] !log [void@puppet181] Upgraded packages git, and git-man on jobchron171 [20:49:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:08] !log [void@puppet181] Upgraded packages git, and git-man on db171 [20:50:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:20] RECOVERY - db161 APT on db161 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [20:50:22] !log [void@puppet181] Upgraded packages git, and git-man on cloud16 [20:50:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:36] !log [void@puppet181] Upgraded packages git, and git-man on cp37 [20:50:37] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [20:50:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:50:42] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:50:48] RECOVERY - matomo151 APT on matomo151 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:50:52] !log [void@puppet181] Upgraded packages git, and git-man on eventgate181 [20:50:56] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:50:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:06] !log [void@puppet181] Upgraded packages git, and git-man on graylog161 [20:51:11] RECOVERY - cp37 APT on cp37 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [20:51:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:16] RECOVERY - jobchron171 APT on jobchron171 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [20:51:20] !log [void@puppet181] Upgraded packages git, and git-man on graphite151 [20:51:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:36] !log [void@puppet181] Upgraded packages git, and git-man on cloud17 [20:51:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:45] RECOVERY - graphite151 APT on graphite151 is OK: APT OK: 58 packages available for upgrade (0 critical updates). [20:51:50] !log [void@puppet181] Upgraded packages git, and git-man on db172 [20:51:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:51:59] RECOVERY - db171 APT on db171 is OK: APT OK: 73 packages available for upgrade (0 critical updates). [20:52:04] !log [void@puppet181] Upgraded packages git, and git-man on bast161 [20:52:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:18] !log [void@puppet181] Upgraded packages git, and git-man on mem151 [20:52:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:33] !log [void@puppet181] Upgraded packages git, and git-man on db181 [20:52:34] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 116 packages available for upgrade (0 critical updates). [20:52:37] RECOVERY - mem151 APT on mem151 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:52:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:39] RECOVERY - eventgate181 APT on eventgate181 is OK: APT OK: 58 packages available for upgrade (0 critical updates). [20:52:47] !log [void@puppet181] Upgraded packages git, and git-man on ldap171 [20:52:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:52:56] RECOVERY - db172 APT on db172 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [20:53:00] RECOVERY - db181 APT on db181 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [20:53:03] !log [void@puppet181] Upgraded packages git, and git-man on cloud18 [20:53:03] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 69 packages available for upgrade (0 critical updates). [20:53:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:53:10] RECOVERY - ldap171 APT on ldap171 is OK: APT OK: 65 packages available for upgrade (0 critical updates). [20:53:16] !log [void@puppet181] Upgraded packages git, and git-man on mattermost1 [20:53:17] RECOVERY - bast161 APT on bast161 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:53:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:53:30] !log [void@puppet181] Upgraded packages git, and git-man on mem161 [20:53:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:53:46] !log [void@puppet181] Upgraded packages git, and git-man on db182 [20:53:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:54:01] !log [void@puppet181] Upgraded packages git, and git-man on kafka181 [20:54:04] RECOVERY - kafka181 APT on kafka181 is OK: APT OK: 51 packages available for upgrade (0 critical updates). [20:54:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:54:20] !log [void@puppet181] Upgraded packages git, and git-man on bast181 [20:54:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:54:25] RECOVERY - db182 APT on db182 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:54:35] !log [void@puppet181] Upgraded packages git, and git-man on mw151 [20:54:38] RECOVERY - cloud18 APT on cloud18 is OK: APT OK: 117 packages available for upgrade (0 critical updates). [20:54:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:54:44] RECOVERY - mattermost1 APT on mattermost1 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:54:50] !log [void@puppet181] Upgraded packages git, and git-man on mw161 [20:54:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:54:57] RECOVERY - mem161 APT on mem161 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:55:05] RECOVERY - mw161 APT on mw161 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:55:05] !log [void@puppet181] Upgraded packages git, and git-man on mw162 [20:55:09] RECOVERY - mw162 APT on mw162 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:55:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:55:20] !log [void@puppet181] Upgraded packages git, and git-man on mw152 [20:55:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:55:35] !log [void@puppet181] Upgraded packages git, and git-man on mw172 [20:55:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:55:50] RECOVERY - mw151 APT on mw151 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:55:50] !log [void@puppet181] Upgraded packages git, and git-man on mw171 [20:55:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:05] !log [void@puppet181] Upgraded packages git, and git-man on mw153 [20:56:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:11] RECOVERY - bast181 APT on bast181 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:56:21] !log [void@puppet181] Upgraded packages git, and git-man on mw163 [20:56:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:36] !log [void@puppet181] Upgraded packages git, and git-man on mw164 [20:56:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:52] !log [void@puppet181] Upgraded packages git, and git-man on mw173 [20:56:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:56:59] RECOVERY - mw171 APT on mw171 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:03] RECOVERY - mw153 APT on mw153 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:05] RECOVERY - mw152 APT on mw152 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:08] !log [void@puppet181] Upgraded packages git, and git-man on mw174 [20:57:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:57:24] !log [void@puppet181] Upgraded packages git, and git-man on mw182 [20:57:29] RECOVERY - mw172 APT on mw172 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:57:35] RECOVERY - mw163 APT on mw163 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:38] !log [void@puppet181] Upgraded packages git, and git-man on mwtask171 [20:57:40] RECOVERY - mw174 APT on mw174 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:57:54] !log [void@puppet181] Upgraded packages git, and git-man on mw181 [20:57:56] RECOVERY - mwtask171 APT on mwtask171 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:57:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:58:10] RECOVERY - mw164 APT on mw164 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:58:10] !log [void@puppet181] Upgraded packages git, and git-man on mw183 [20:58:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:58:27] !log [void@puppet181] Upgraded packages git, and git-man on mw184 [20:58:28] RECOVERY - mw181 APT on mw181 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:58:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [20:58:37] RECOVERY - mw173 APT on mw173 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:58:41] RECOVERY - mwtask151 APT on mwtask151 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [20:58:42]