[00:01:14] [02statichelp] 07WikiTideBot pushed 1 new commit to 03main 13https://github.com/miraheze/statichelp/commit/b4289c60bb50c3e0736b7624ed43b9ff0bce761c [00:01:14] 02statichelp/03main 07WikiTideBot 03b4289c6 Bot: Auto-update Tech namespace pages 2026-06-26 00:01:11 [00:08:17] !log [somerandomdeveloper@mwtask181] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php SemanticMediaWiki:setupStore --wiki=bluepageswiki (END - exit=0) [00:08:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:12:52] !log [somerandomdeveloper@test151] starting deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'SemanticMediaWiki'} to test151 [00:12:53] !log [somerandomdeveloper@test151] finished deploy of {'versions': ['1.45', '1.46'], 'upgrade_extensions': 'SemanticMediaWiki'} to test151 - SUCCESS in 1s [00:12:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:12:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:13:23] !log [somerandomdeveloper@test151] sudo -u www-data php /srv/mediawiki/1.46/maintenance/run.php SemanticMediaWiki:setupStore --wiki=smwtestwikibeta (END - exit=0) [00:13:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:19:17] !log [somerandomdeveloper@test151] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.46/maintenance/run.php MirahezeMagic:GenerateExtensionDatabaseList metawiki --directory=/tmp (START) [00:19:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:19:20] !log [somerandomdeveloper@test151] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.46/maintenance/run.php MirahezeMagic:GenerateExtensionDatabaseList metawiki --directory=/tmp (END - exit=256) [00:19:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:19:44] oh ffs it's the --extension bug again [00:19:52] which actually makes this easier ig [00:20:30] !log [somerandomdeveloper@test151] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.46/maintenance/run.php SemanticMediaWiki:setupStore (START) [00:20:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:20:45] !log [somerandomdeveloper@test151] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.46/maintenance/run.php SemanticMediaWiki:setupStore (END - exit=0) [00:20:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:22:03] !log [somerandomdeveloper@mwtask181] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.45/maintenance/run.php SemanticMediaWiki:setupStore (START) [00:22:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:50] ^ Note that this recreates the example SMW pages/properties on the few wikis that deleted them, but there's not really a way to work around that, and in the end it's trivial to delete them again [00:37:19] !log [somerandomdeveloper@mwtask181] sudo -u www-data /usr/local/bin/foreachwikiindblist /tmp/semanticmediawiki.php /srv/mediawiki/1.45/maintenance/run.php SemanticMediaWiki:setupStore (END - exit=0) [00:37:22] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:44:34] [02puppet] 07SomeMWDev created 03T15525 (+1 new commit) 13https://github.com/miraheze/puppet/commit/fcef90b98d60 [00:44:34] 02puppet/03T15525 07SomeRandomDeveloper 03fcef90b prometheus: Remove old SMW job aliases… [00:44:47] [02puppet] 07SomeMWDev opened pull request #4879: prometheus: Remove old SMW job aliases (03main...03T15525) 13https://github.com/miraheze/puppet/pull/4879 [00:46:40] [02puppet] 07SomeMWDev pushed 1 new commit to 03T15525 13https://github.com/miraheze/puppet/commit/b7f9421ceb198303930f480700d2bf9cedae0b0a [00:46:40] 02puppet/03T15525 07SomeRandomDeveloper 03b7f9421 changeprop202: Remove old SMW job aliases [00:46:55] [02puppet] 07SomeMWDev retitled PR #4879: "prometheus: Remove old SMW job aliases" ➜ "Remove old SMW job aliases" 13https://github.com/miraheze/puppet/pull/4879 [01:16:17] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 21.53, 19.40, 17.09 [01:18:17] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 16.97, 18.48, 17.04 [01:28:43] !log sudo salt-ssh -E 'mw(153|152|183|193)' cmd.run 'rm /srv/mediawiki/cache/metawiki.php' [01:28:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:28:46] !log sudo salt-ssh -E 'mw(153|152|183|193)' cmd.run 'rm /srv/mediawiki/cache/config-metawiki.php' [01:28:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:44:20] [02mw-config] 07YTFGolf left a file comment in pull request #6443 0360baaf9: db has been renamed to `psaltictheorywiki` 13https://github.com/miraheze/mw-config/pull/6443#discussion_r3478698162 [01:44:48] [02mw-config] 07YTFGolf left a file comment in pull request #6443 0360baaf9: this should be after the `],` line immediately below 13https://github.com/miraheze/mw-config/pull/6443#discussion_r3478699451 [03:06:17] [02mw-config] 07frm5993 left a file comment in pull request #6443 03deb54cd: i see, thanks 13https://github.com/miraheze/mw-config/pull/6443#discussion_r3478901771 [04:05:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 20.17, 11.17, 7.92 [04:21:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 3.99, 10.29, 11.23 [04:25:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 4.84, 7.49, 9.87 [06:21:09] Whole farm is down? [06:21:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 77.65, 48.36, 20.62 [06:21:48] dbs seem fine. db161 is at 98% RAM usage but seems to do okay. [06:23:07] Temporary hiccup it seems [06:33:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 2.43, 6.66, 10.85 [06:35:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 2.89, 5.38, 9.86 [06:54:25] it still brought the whole farm down though? [06:54:43] not the first time a temporary hiccup has been bad enough to do that [06:55:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 27.17, 14.83, 9.39 [06:56:16] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 1 backends are down. mw193 [06:56:17] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 1 backends are down. mw193 [06:56:17] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 1 backends are down. mw193 [06:56:41] Oh it was indeed db161 that brought the farm down [06:56:58] I was on Grafana but it probably didn't update frequently enough. [06:57:19] [1/2] And I think it's causing problems again [06:57:20] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1519959730238521483/image.png?ex=6a3f744f&is=6a3e22cf&hm=b672cf73fd0f9c8c83ec82e0d2e03adcaf1ae3cf81f6e3278ebe049c546fb5f4& [06:58:16] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [06:58:17] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [06:58:17] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [06:59:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 2.91, 9.04, 8.37 [07:37:11] The little DB that could bring down Miraheze [07:39:21] https://cdn.discordapp.com/attachments/808001911868489748/1519970307115450419/voice-message.ogg?ex=6a3f7e28&is=6a3e2ca8&hm=fd797e35065aab8f9bdb2505ea94ecbbe4ed79a224ff38dc1b766801b47a0eba& [08:32:34] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:32:39] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [08:32:44] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:32:44] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [08:32:46] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.013 second response time [08:32:49] PROBLEM - db161 PowerDNS Recursor on db161 is CRITICAL: CRITICAL - Plugin timed out while executing system call [08:32:49] PROBLEM - cp161 Varnish Backends on cp161 is CRITICAL: 5 backends are down. mw151 mw172 mw181 mw163 mw191 [08:32:52] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.010 second response time [08:32:54] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:01] PROBLEM - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is CRITICAL: CRITICAL - NGINX Error Rate is 83% [08:33:04] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [08:33:08] PROBLEM - cp201 HTTPS on cp201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:14] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:33:17] PROBLEM - cp171 HTTPS on cp171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:22] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:25] PROBLEM - cp191 HTTPS on cp191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:26] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:28] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:33:31] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [08:33:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 195.96, 102.64, 42.53 [08:34:05] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:34:16] PROBLEM - cp171 Varnish Backends on cp171 is CRITICAL: 7 backends are down. mw161 mw172 mw181 mw153 mw163 mw201 mw203 [08:34:17] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 5857 bytes in 0.011 second response time [08:34:17] PROBLEM - cp201 Varnish Backends on cp201 is CRITICAL: 7 backends are down. mw161 mw172 mw181 mw153 mw163 mw193 mw203 [08:34:17] PROBLEM - cp191 Varnish Backends on cp191 is CRITICAL: 8 backends are down. mw161 mw172 mw181 mw153 mw163 mw193 mw201 mw203 [08:34:23] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:34:29] PROBLEM - cp161 HTTPS on cp161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:35:46] @Infrastructure Specialists I'm going to depool db161 because it's not responsive for several minutes straight [08:35:59] 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 10001 milliseconds with 0 bytes received [08:36:03] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:36:07] RECOVERY - mw152 HTTPS on mw152 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.292 second response time [08:36:19] RECOVERY - mw171 MediaWiki Rendering on mw171 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 2.470 second response time [08:36:24] RECOVERY - mw202 HTTPS on mw202 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.763 second response time [08:36:32] RECOVERY - cp161 HTTPS on cp161 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1518 bytes in 4.045 second response time [08:36:32] RECOVERY - mw171 HTTPS on mw171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.050 second response time [08:36:47] RECOVERY - mw173 MediaWiki Rendering on mw173 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 7.486 second response time [08:36:52] !log [petramagna@mwtask181] starting deploy of {'config': True, 'force': True} to all [08:36:52] RECOVERY - db161 PowerDNS Recursor on db161 is OK: DNS OK: 0.209 seconds response time. db161.fsslc.wtnet returns 10.0.16.128 [08:37:05] RECOVERY - cp201 HTTPS on cp201 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.635 second response time [08:37:10] !log [petramagna@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 18s [08:37:14] RECOVERY - mw192 MediaWiki Rendering on mw192 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 4.592 second response time [08:37:17] RECOVERY - cp171 HTTPS on cp171 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.079 second response time [08:37:18] RECOVERY - mw182 HTTPS on mw182 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.318 second response time [08:37:18] RECOVERY - cp191 HTTPS on cp191 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 1463 bytes in 0.308 second response time [08:37:24] RECOVERY - mw183 HTTPS on mw183 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 2.614 second response time [08:37:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:37:26] RECOVERY - mw173 HTTPS on mw173 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.072 second response time [08:37:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:37:31] RECOVERY - mw202 MediaWiki Rendering on mw202 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.273 second response time [08:37:55] RECOVERY - mw163 HTTPS on mw163 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.077 second response time [08:38:00] RECOVERY - mw163 MediaWiki Rendering on mw163 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.221 second response time [08:38:16] RECOVERY - cp171 Varnish Backends on cp171 is OK: All 31 backends are healthy [08:38:17] RECOVERY - cp201 Varnish Backends on cp201 is OK: All 31 backends are healthy [08:38:17] RECOVERY - cp191 Varnish Backends on cp191 is OK: All 31 backends are healthy [08:38:43] RECOVERY - mw192 HTTPS on mw192 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.084 second response time [08:38:43] RECOVERY - mw162 MediaWiki Rendering on mw162 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.219 second response time [08:38:49] RECOVERY - cp161 Varnish Backends on cp161 is OK: All 31 backends are healthy [08:38:54] RECOVERY - mw162 HTTPS on mw162 is OK: HTTP OK: HTTP/2 410 - Status line output matched "HTTP/2 410" - 340 bytes in 0.088 second response time [08:38:55] RECOVERY - mw183 MediaWiki Rendering on mw183 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.265 second response time [08:39:00] RECOVERY - mw152 MediaWiki Rendering on mw152 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.208 second response time [08:39:01] RECOVERY - cp161 HTTP 4xx/5xx ERROR Rate on cp161 is OK: OK - NGINX Error Rate is 20% [08:39:05] RECOVERY - mw182 MediaWiki Rendering on mw182 is OK: HTTP OK: HTTP/1.1 200 OK - 8191 bytes in 0.264 second response time [08:42:17] [1/2] Still under extremely high load despite being depooled. At least RAM usage is down. [08:42:17] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1519986144031412264/image.png?ex=6a3f8ce8&is=6a3e3b68&hm=a4225cd94df0e7df2b7f39da947c954f8ce7c8461e5bc70d584743d170f284d1& [08:44:26] The wikis under the most bot activity on CF are all not on db161. [08:45:39] !log [petramagna@mwtask181] starting deploy of {'config': True} to all [08:45:40] !log [petramagna@mwtask181] DEPLOY ABORTED: Canary check failed for publictestwiki.com@localhost [08:45:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:45:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:45:47] !log [petramagna@mwtask181] starting deploy of {'config': True, 'force': True} to all [08:45:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:46:07] !log [petramagna@mwtask181] finished deploy of {'config': True, 'force': True} to all - SUCCESS in 19s [08:46:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [08:46:11] Repooling db161 since load has gone down and no infra is around to see what caused it in the first place [09:11:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 2.85, 2.92, 11.14 [09:13:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 3.87, 3.05, 10.17 [10:09:02] Weird, I wonder what's causing the load issue? [10:17:34] We can wait for infra to ssh into a db server and find out since we dump the proclist automatically now. [12:05:28] RECOVERY - test151 Check unit status of mediawiki_job_manage-inactive-wikis on test151 is OK: OK: Status of the systemd unit mediawiki_job_manage-inactive-wikis [12:35:35] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 30.64, 15.57, 8.27 [12:41:35] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 7.28, 10.85, 8.80 [12:43:35] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 4.14, 8.61, 8.23 [13:04:04] !log [somerandomdeveloper@mwtask181] starting deploy of {'versions': '1.45', 'upgrade_extensions': 'PageForms'} to all [13:04:07] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:04:33] !log [somerandomdeveloper@mwtask181] finished deploy of {'versions': '1.45', 'upgrade_extensions': 'PageForms'} to all - SUCCESS in 29s [13:04:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:47:56] [02puppet] 07paladox pushed 1 new commit to 03main 13https://github.com/miraheze/puppet/commit/594b86a657ec0da0e0254dc0364fa8daf9e673a0 [13:47:57] 02puppet/03main 07SomeRandomDeveloper 03594b86a Remove old SMW job aliases (#4879)… [13:47:57] [02puppet] 07paladox merged 07SomeMWDev's pull request #4879: Remove old SMW job aliases (03main...03T15525) 13https://github.com/miraheze/puppet/pull/4879 [13:47:58] [02puppet] 07paladox 04deleted 03T15525 at 03b7f9421 13https://api.github.com/repos/miraheze/puppet/commit/b7f9421 [19:42:17] [02.github] 07dependabot[bot] created 03dependabot/github_actions/actions/cache-6.1.0 (+1 new commit) 13https://github.com/miraheze/.github/commit/e953a1c95577 [19:42:17] 02.github/03dependabot/github_actions/actions/cache-6.1.0 07dependabot[bot] 03e953a1c Bump actions/cache from 5.0.5 to 6.1.0… [19:42:18] [02.github] 07dependabot[bot] added the label 'dependencies' to pull request #99 (Bump actions/cache from 5.0.5 to 6.1.0) 13https://github.com/miraheze/.github/pull/99 [19:42:19] [02.github] 07dependabot[bot] added the label 'github_actions' to pull request #99 (Bump actions/cache from 5.0.5 to 6.1.0) 13https://github.com/miraheze/.github/pull/99 [19:42:20] [02.github] 07dependabot[bot] opened pull request #99: Bump actions/cache from 5.0.5 to 6.1.0 (03main...03dependabot/github_actions/actions/cache-6.1.0) 13https://github.com/miraheze/.github/pull/99 [19:42:22] [02.github] 07dependabot[bot] added the label 'dependencies' to pull request #99 (Bump actions/cache from 5.0.5 to 6.1.0) 13https://github.com/miraheze/.github/pull/99 [19:42:24] [02.github] 07dependabot[bot] added the label 'github_actions' to pull request #99 (Bump actions/cache from 5.0.5 to 6.1.0) 13https://github.com/miraheze/.github/pull/99 [19:42:26] [02.github] 07dependabot[bot] closed pull request #98: Bump actions/cache from 5.0.5 to 6.0.0 (03main...03dependabot/github_actions/actions/cache-6.0.0) 13https://github.com/miraheze/.github/pull/98 [19:42:28] [02.github] 07dependabot[bot] 04deleted 03dependabot/github_actions/actions/cache-6.0.0 at 03607275c 13https://api.github.com/repos/miraheze/.github/commit/607275c [19:43:25] [02.github] 07dependabot[bot] commented on pull request #98: Superseded by #99. 13https://github.com/miraheze/.github/pull/98#issuecomment-4812897287 [23:10:30] PROBLEM - db161 Current Load on db161 is CRITICAL: LOAD CRITICAL - total load average: 51.89, 24.62, 11.55 [23:25:44] The load is high but the farm is just slightly slower without going down. [23:53:57] PROBLEM - db161 Current Load on db161 is WARNING: LOAD WARNING - total load average: 4.58, 4.39, 11.40 [23:57:54] RECOVERY - db161 Current Load on db161 is OK: LOAD OK - total load average: 4.77, 4.74, 9.95