[00:00:54] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/3ed180d9bdd4ccbf9f2c324b0242936b9bc5d44f [00:00:54] 02statichelp/03main 07WikiTideBot 033ed180d Bot: Auto-update Tech namespace pages 2026-06-28 00:00:52 [01:04:05] PROBLEM - cp201 Disk Space on cp201 is WARNING: DISK WARNING - free space: / 44100MiB (9.7% inode=100%); [01:10:05] RECOVERY - cp201 Disk Space on cp201 is OK: DISK OK - free space: / 87449MiB (19.3% inode=100%); [04:15:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 247.33, 81.93, 30.85 [04:16:17] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 9 backends are down. mw161 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [04:16:17] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 9 backends are down. mw161 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [04:17:02] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:17:07] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.018 second response time [04:17:09] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:17:11] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:17:12] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:17:48] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:17:58] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.012 second response time [04:18:01] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.012 second response time [04:18:04] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:05] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:13] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:18:15] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:17] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:18] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:21] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:21] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:27] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:29] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [04:18:30] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:31] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:31] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:18:32] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10005 milliseconds with 0 bytes received [04:18:32] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:32] PROBLEM - cp171 HTTPS on cp171 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 [04:18:33] 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 10005 milliseconds with 0 bytes received [04:18:37] 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 10004 milliseconds with 0 bytes received [04:18:37] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:37] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.012 second response time [04:18:39] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:39] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:39] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:18:40] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:18:41] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [04:18:43] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:46] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [04:18:49] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 9 backends are down. mw161 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [04:18:50] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:18:52] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:54] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [04:18:54] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10005 milliseconds with 0 bytes received [04:19:01] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 91% [04:19:02] RECOVERY - mw172 MediaWiki Rendering on mw172 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.219 second response time [04:19:02] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:19:08] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 9 backends are down. mw161 mw172 mw181 mw153 mw163 mw191 mw193 mw201 mw203 [04:19:12] RECOVERY - mw201 HTTPS on mw201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.080 second response time [04:19:48] RECOVERY - mw193 HTTPS on mw193 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.096 second response time [04:19:58] RECOVERY - mw181 MediaWiki Rendering on mw181 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [04:20:02] RECOVERY - mw191 MediaWiki Rendering on mw191 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.205 second response time [04:20:04] RECOVERY - mw172 HTTPS on mw172 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.067 second response time [04:20:05] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.075 second response time [04:20:08] RECOVERY - mw153 MediaWiki Rendering on mw153 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.220 second response time [04:20:12] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.070 second response time [04:20:12] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.115 second response time [04:20:17] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [04:20:17] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 0.080 second response time [04:20:17] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [04:20:18] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [04:20:22] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.066 second response time [04:20:24] RECOVERY - mw181 HTTPS on mw181 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.075 second response time [04:20:26] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.200 second response time [04:20:26] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.266 second response time [04:20:27] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.069 second response time [04:20:29] RECOVERY - mw191 HTTPS on mw191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.085 second response time [04:20:30] RECOVERY - mw193 MediaWiki Rendering on mw193 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.202 second response time [04:20:30] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.075 second response time [04:20:31] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.073 second response time [04:20:31] RECOVERY - mw161 HTTPS on mw161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.068 second response time [04:20:33] RECOVERY - mw203 MediaWiki Rendering on mw203 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.325 second response time [04:20:34] RECOVERY - mw153 HTTPS on mw153 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.056 second response time [04:20:35] RECOVERY - mw203 HTTPS on mw203 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.079 second response time [04:20:37] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.082 second response time [04:20:38] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.198 second response time [04:20:38] RECOVERY - mw201 MediaWiki Rendering on mw201 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.253 second response time [04:20:38] RECOVERY - mw151 MediaWiki Rendering on mw151 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.185 second response time [04:20:40] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.195 second response time [04:20:41] RECOVERY - mw161 MediaWiki Rendering on mw161 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.220 second response time [04:20:47] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.251 second response time [04:20:47] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.193 second response time [04:20:49] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [04:20:51] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.080 second response time [04:20:52] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.074 second response time [04:20:54] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.067 second response time [04:20:56] RECOVERY - mw151 HTTPS on mw151 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.074 second response time [04:21:00] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.232 second response time [04:21:01] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 1% [04:21:05] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.213 second response time [04:21:06] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [04:21:07] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.243 second response time [04:59:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 2.06, 2.37, 11.53 [05:03:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 1.99, 2.13, 9.33 [10:37:38] [1/2] https://cdn.discordapp.com/attachments/808001911868489748/1520739949647761518/image.jpeg?ex=6a424af1&is=6a40f971&hm=c01ecf3f60c60f937f51759b5230cbf844d82c2ce4edd3bd7df3135d96115f1c& [10:37:38] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1520739950268645426/image.jpeg?ex=6a424af2&is=6a40f972&hm=b12a833fb63c9e57eb68ec98d08da3b07da039d200ee793972c8ab9f3e442bf5& [12:03:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 40.77, 20.69, 10.85 [12:19:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 3.69, 6.87, 11.05 [12:23:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 5.20, 5.75, 9.61 [13:03:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 18.28, 20.72, 11.57 [13:07:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 4.18, 11.12, 9.67 [13:09:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 2.93, 8.33, 8.82 [14:02:44] db161 back at it again with the good ol “bring down the farm” [14:03:17] I guess it recovered by itself tho [14:33:44] [02mediawiki-repos] 07SomeMWDev created 03T15137-remove-patches (+1 new commit) 13https://github.com/miraheze/mediawiki-repos/commit/94cff950187f [14:33:45] 02mediawiki-repos/03T15137-remove-patches 07SomeRandomDeveloper 0394cff95 T15137: Drop CommentStreams patches… [14:35:29] [02mediawiki-repos] 07SomeMWDev opened pull request #151: T15137: Drop CommentStreams patches (03main...03T15137-remove-patches) 13https://github.com/miraheze/mediawiki-repos/pull/151 [14:35:42] [02mediawiki-repos] 07SomeMWDev merged pull request #151: T15137: Drop CommentStreams patches (03main...03T15137-remove-patches) 13https://github.com/miraheze/mediawiki-repos/pull/151 [14:35:44] [02mediawiki-repos] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mediawiki-repos/commit/3dd5a4dd128cb75e1689dcc2bf07ecaec1beaed0 [14:35:45] 02mediawiki-repos/03main 07SomeRandomDeveloper 033dd5a4d T15137: Drop CommentStreams patches (#151)… [14:35:47] [02mediawiki-repos] 07SomeMWDev 04deleted 03T15137-remove-patches at 0394cff95 13https://api.github.com/repos/miraheze/mediawiki-repos/commit/94cff95 [14:37:02] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.33, 13.24, 12.43 [14:39:48] !log [somerandomdeveloper@test151] starting deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'CommentStreams'} to test151 [14:39:49] !log [somerandomdeveloper@test151] finished deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'CommentStreams'} to test151 - SUCCESS in 1s [14:39:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:39:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:40:14] !log [somerandomdeveloper@mwtask181] starting deploy of {'versions': '1.45', 'upgrade_extensions': 'CommentStreams'} to all [14:40:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:40:43] !log [somerandomdeveloper@mwtask181] finished deploy of {'versions': '1.45', 'upgrade_extensions': 'CommentStreams'} to all - SUCCESS in 28s [14:40:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [14:45:03] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 12.95, 13.47, 12.91 [15:15:56] [02ManageWiki] 07dependabot[bot] created 03dependabot/npm_and_yarn/js-yaml-4.3.0 (+1 new commit) 13https://github.com/miraheze/ManageWiki/commit/fe8209cd996b [15:15:56] 02ManageWiki/03dependabot/npm_and_yarn/js-yaml-4.3.0 07dependabot[bot] 03fe8209c Bump js-yaml from 4.1.1 to 4.3.0… [15:15:57] [02ManageWiki] 07dependabot[bot] added the label 'javascript' to pull request #793 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/ManageWiki/pull/793 [15:15:57] [02ManageWiki] 07dependabot[bot] added the label 'dependencies' to pull request #793 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/ManageWiki/pull/793 [15:15:59] [02ManageWiki] 07dependabot[bot] opened pull request #793: Bump js-yaml from 4.1.1 to 4.3.0 (03main...03dependabot/npm_and_yarn/js-yaml-4.3.0) 13https://github.com/miraheze/ManageWiki/pull/793 [15:16:01] [02ManageWiki] 07dependabot[bot] added the label 'dependencies' to pull request #793 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/ManageWiki/pull/793 [15:16:03] [02ManageWiki] 07dependabot[bot] added the label 'javascript' to pull request #793 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/ManageWiki/pull/793 [15:20:58] miraheze/ManageWiki - dependabot[bot] the build passed. [15:22:06] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 15.64, 13.81, 12.82 [15:24:02] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 13.08, 13.44, 12.80 [15:36:42] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 15.69, 14.40, 13.41 [15:44:27] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 12.17, 13.30, 13.36 [16:07:48] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.87, 13.66, 13.14 [16:09:44] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 12.86, 13.22, 13.04 [16:30:10] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.68, 13.73, 13.12 [16:32:06] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 12.84, 13.54, 13.14 [16:36:01] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.85, 14.18, 13.50 [16:41:50] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 8.13, 11.71, 12.83 [16:42:15] [02MatomoAnalytics] 07dependabot[bot] created 03dependabot/npm_and_yarn/js-yaml-4.3.0 (+1 new commit) 13https://github.com/miraheze/MatomoAnalytics/commit/04de5116e43c [16:42:15] 02MatomoAnalytics/03dependabot/npm_and_yarn/js-yaml-4.3.0 07dependabot[bot] 0304de511 Bump js-yaml from 4.1.1 to 4.3.0… [16:42:16] [02MatomoAnalytics] 07dependabot[bot] added the label 'dependencies' to pull request #199 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/MatomoAnalytics/pull/199 [16:42:16] [02MatomoAnalytics] 07dependabot[bot] added the label 'javascript' to pull request #199 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/MatomoAnalytics/pull/199 [16:42:18] [02MatomoAnalytics] 07dependabot[bot] opened pull request #199: Bump js-yaml from 4.1.1 to 4.3.0 (03main...03dependabot/npm_and_yarn/js-yaml-4.3.0) 13https://github.com/miraheze/MatomoAnalytics/pull/199 [16:42:20] [02MatomoAnalytics] 07dependabot[bot] added the label 'dependencies' to pull request #199 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/MatomoAnalytics/pull/199 [16:42:22] [02MatomoAnalytics] 07dependabot[bot] added the label 'javascript' to pull request #199 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/MatomoAnalytics/pull/199 [16:47:17] miraheze/MatomoAnalytics - dependabot[bot] the build passed. [17:03:15] [02CreateWiki] 07dependabot[bot] created 03dependabot/npm_and_yarn/js-yaml-4.3.0 (+1 new commit) 13https://github.com/miraheze/CreateWiki/commit/99db43deb750 [17:03:15] 02CreateWiki/03dependabot/npm_and_yarn/js-yaml-4.3.0 07dependabot[bot] 0399db43d Bump js-yaml from 4.1.1 to 4.3.0… [17:03:16] [02CreateWiki] 07dependabot[bot] opened pull request #827: Bump js-yaml from 4.1.1 to 4.3.0 (03main...03dependabot/npm_and_yarn/js-yaml-4.3.0) 13https://github.com/miraheze/CreateWiki/pull/827 [17:03:16] [02CreateWiki] 07dependabot[bot] added the label 'dependencies' to pull request #827 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/CreateWiki/pull/827 [17:03:18] [02CreateWiki] 07dependabot[bot] added the label 'javascript' to pull request #827 (Bump js-yaml from 4.1.1 to 4.3.0) 13https://github.com/miraheze/CreateWiki/pull/827 [17:10:21] miraheze/CreateWiki - dependabot[bot] the build passed. [17:14:26] !log [reception@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php CreateWiki:DeleteWikis --wiki=loginwiki --delete Reception123 (END - exit=33280) [17:14:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:14:52] !log [reception@mwtask171] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php CreateWiki:DeleteWikis --wiki=loginwiki --delete Reception123 (END - exit=33280) [17:14:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:25:35] !log [petramagna@test151] starting deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'PortableInfobox'} to test151 [17:25:36] !log [petramagna@test151] finished deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'PortableInfobox'} to test151 - SUCCESS in 1s [17:25:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:25:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:25:53] !log [petramagna@test151] starting deploy of {'versions': '1.46', 'upgrade_extensions': 'PortableInfobox'} to test151 [17:25:54] !log [petramagna@test151] finished deploy of {'versions': '1.46', 'upgrade_extensions': 'PortableInfobox'} to test151 - SUCCESS in 0s [17:25:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:26:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:26:37] !log [petramagna@test151] starting deploy of {'folders': '1.46/extensions/PortableInfobox', 'ignore_time': True} to test151 [17:26:38] !log [petramagna@test151] finished deploy of {'folders': '1.46/extensions/PortableInfobox', 'ignore_time': True} to test151 - SUCCESS in 0s [17:26:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:26:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:28:36] I think PI is borked on Beta. Enabling through ManageWiki doesn't add it to Special:Version and the extension tag is not registered. [17:55:55] [02mediawiki-repos] 07SomeMWDev created 03drop-T14969-patch (+1 new commit) 13https://github.com/miraheze/mediawiki-repos/commit/c46319e18eb7 [17:55:56] 02mediawiki-repos/03drop-T14969-patch 07SomeRandomDeveloper 03c46319e Drop patch for T14969 [17:56:06] [02mediawiki-repos] 07SomeMWDev opened pull request #152: Drop patch for T14969 (03main...03drop-T14969-patch) 13https://github.com/miraheze/mediawiki-repos/pull/152 [17:56:16] [02mediawiki-repos] 07SomeMWDev merged pull request #152: Drop patch for T14969 (03main...03drop-T14969-patch) 13https://github.com/miraheze/mediawiki-repos/pull/152 [17:56:18] [02mediawiki-repos] 07SomeMWDev pushed 1 new commit to 03main 13https://github.com/miraheze/mediawiki-repos/commit/ef15b31c9c45039afa8969ea42fcaaedad99e443 [17:56:20] [02mediawiki-repos] 07SomeMWDev 04deleted 03drop-T14969-patch at 03c46319e 13https://api.github.com/repos/miraheze/mediawiki-repos/commit/c46319e [17:56:21] 02mediawiki-repos/03main 07SomeRandomDeveloper 03ef15b31 Drop patch for T14969 (#152) [18:00:17] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/3796f31adb9412f5f1d6271a8867645e7922000e [18:00:17] 02ssl/03main 07WikiTideBot 033796f31 Bot: Auto-update domain lists [18:02:55] !log deployed patch for T15587 on beta [18:02:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:09:02] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 13.95, 12.57, 11.44 [18:11:02] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 12.18, 12.04, 11.36 [18:33:02] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.31, 13.59, 12.47 [18:37:02] PROBLEM - matomo151 Current Load on matomo151 is CRITICAL: LOAD CRITICAL - total load average: 16.48, 14.90, 13.23 [18:39:02] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 14.65, 14.48, 13.26 [18:47:03] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 11.87, 12.95, 13.11 [19:22:49] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 1 backends are down. mw163 [19:23:05] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:23:13] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Connection timed out after 10003 milliseconds [19:24:49] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [19:25:00] PROBLEM - mw163 Current Load on mw163 is CRITICAL: LOAD CRITICAL - total load average: 20.29, 28.58, 19.10 [19:25:02] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.237 second response time [19:25:09] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.276 second response time [19:26:53] PROBLEM - mw163 Current Load on mw163 is WARNING: LOAD WARNING - total load average: 10.06, 22.24, 17.90 [19:28:47] RECOVERY - mw163 Current Load on mw163 is OK: LOAD OK - total load average: 7.93, 17.84, 16.79 [19:30:14] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/72459352a5b796041f43b8783268b51414b4195a [19:30:14] 02ssl/03main 07WikiTideBot 037245935 Bot: Auto-update domain lists [19:30:35] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 8.53, 6.37, 4.21 [19:37:20] !log upgrade phorge on phorge171 [19:37:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:38:35] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 4.30, 6.99, 5.60 [19:40:35] RECOVERY - swiftproxy161 Current Load on swiftproxy161 is OK: LOAD OK - total load average: 2.42, 5.30, 5.14 [19:51:17] [02puppet] 07paladox created 03paladox-patch-2 (+1 new commit) 13https://github.com/miraheze/puppet/commit/c10a296b8953 [19:51:17] 02puppet/03paladox-patch-2 07paladox 03c10a296 matomo: Change ensure from 'present' to 'absent' for archiver 4 [19:51:24] [02puppet] 07paladox opened pull request #4880: matomo: Change ensure from 'present' to 'absent' for archiver 4 (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4880 [19:51:33] [02puppet] 07paladox merged pull request #4880: matomo: Change ensure from 'present' to 'absent' for archiver 4 (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4880 [19:51:35] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/96bf1fee02360494655cd7c093fb9383eba6ad02 [19:51:37] [02puppet] 07paladox 04deleted 03paladox-patch-2 at 03c10a296 13https://api.github.com/repos/miraheze/puppet/commit/c10a296 [19:51:39] 02puppet/03main 07paladox 0396bf1fe matomo: Change ensure from 'present' to 'absent' for archiver 4 (#4880) [19:57:27] PROBLEM - matomo151 Check unit status of matomo-archiver-4 on matomo151 is CRITICAL: CRITICAL: Status of the systemd unit matomo-archiver-4 [20:01:50] [02puppet] 07paladox created 03paladox-patch-2 (+1 new commit) 13https://github.com/miraheze/puppet/commit/11ad01692e9c [20:01:50] 02puppet/03paladox-patch-2 07paladox 0311ad016 matomo: Add support for removing queued tracking systemd timers easily [20:01:53] [02puppet] 07paladox opened pull request #4881: matomo: Add support for removing queued tracking systemd timers easily (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4881 [20:02:32] [02puppet] 07paladox merged pull request #4881: matomo: Add support for removing queued tracking systemd timers easily (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4881 [20:02:34] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/7269ea4851c47c1346f5332d4477a850f573ed2f [20:02:36] [02puppet] 07paladox 04deleted 03paladox-patch-2 at 0311ad016 13https://api.github.com/repos/miraheze/puppet/commit/11ad016 [20:02:37] 02puppet/03main 07paladox 037269ea4 matomo: Add support for removing queued tracking systemd timers easily (#4881) [20:07:19] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/d2997454b344741f035e068fe6d5e5d5dee5c570 [20:07:19] 02puppet/03main 07paladox 03d299745 Fix [20:07:27] PROBLEM - matomo151 Check unit status of matomo-archiver-4 on matomo151 is UNKNOWN: NRPE: Command 'check_Check unit status of matomo-archiver-4' not defined [20:08:31] [02puppet] 07paladox created 03paladox-patch-2 (+1 new commit) 13https://github.com/miraheze/puppet/commit/f054fb5a2df6 [20:08:31] 02puppet/03paladox-patch-2 07paladox 03f054fb5 matomo: purge 3rd queuedtracking systemd timer [20:08:35] [02puppet] 07paladox opened pull request #4882: matomo: purge 3rd queuedtracking systemd timer (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4882 [20:08:42] [02puppet] 07paladox merged pull request #4882: matomo: purge 3rd queuedtracking systemd timer (03main...03paladox-patch-2) 13https://github.com/miraheze/puppet/pull/4882 [20:08:42] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/b2f46184c297faca429c6413fbcc34074c0f8c4d [20:08:44] 02puppet/03main 07paladox 03b2f4618 matomo: purge 3rd queuedtracking systemd timer (#4882) [20:08:46] [02puppet] 07paladox 04deleted 03paladox-patch-2 at 03f054fb5 13https://api.github.com/repos/miraheze/puppet/commit/f054fb5 [20:12:13] PROBLEM - matomo151 Check unit status of matomo-queuedtracking-2 on matomo151 is UNKNOWN: NRPE: Command 'check_Check unit status of matomo-queuedtracking-2' not defined [20:58:28] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 9.21, 6.09, 3.99 [21:14:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 7.14, 7.80, 6.69 [21:16:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 8.48, 7.93, 6.86 [21:20:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 7.52, 7.93, 7.12 [21:22:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 8.38, 8.14, 7.30 [21:26:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 7.85, 7.98, 7.43 [21:28:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 8.85, 8.22, 7.58 [21:29:54] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/a52f5c52a57043590867e6c0c8b40ecd25cdf0c7 [21:29:54] 02puppet/03main 07paladox 03a52f5c5 Revert "matomo: purge 3rd queuedtracking systemd timer (#4882)"… [21:34:25] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 3.87, 7.10, 7.42 [21:38:22] RECOVERY - swiftproxy161 Current Load on swiftproxy161 is OK: LOAD OK - total load average: 3.13, 5.06, 6.50 [22:00:17] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/ee417d36c49a44f5b8457d5e0bca05f07660d3d8 [22:00:17] 02ssl/03main 07WikiTideBot 03ee417d3 Bot: Auto-update domain lists [22:35:32] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 11.46, 10.84, 7.97 [22:39:31] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 14.09, 11.58, 8.84 [22:41:31] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 10.68, 11.29, 9.07 [22:47:29] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 5.08, 9.74, 9.32 [23:00:17] [02ssl] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/ssl/commit/f8ed2cc3270e4ef049d4ffcf90eb58ba7462f8a9 [23:00:17] 02ssl/03main 07WikiTideBot 03f8ed2cc Bot: Auto-update domain lists [23:05:39] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is CRITICAL: LOAD CRITICAL - total load average: 8.27, 5.15, 3.49 [23:17:39] PROBLEM - swiftproxy161 Current Load on swiftproxy161 is WARNING: LOAD WARNING - total load average: 3.58, 7.06, 5.97 [23:19:39] RECOVERY - swiftproxy161 Current Load on swiftproxy161 is OK: LOAD OK - total load average: 3.50, 5.63, 5.57