[00:34:58] <icinga-miraheze>	 PROBLEM - jobrunner3 Current Load on jobrunner3 is WARNING: WARNING - load average: 5.43, 4.99, 3.93
[00:35:34] <Zppix>	 Hmmm
[00:35:54] * Zppix pats jbr
[00:37:05] <icinga-miraheze>	 PROBLEM - jobrunner4 Current Load on jobrunner4 is CRITICAL: CRITICAL - load average: 6.41, 5.20, 3.77
[00:39:00] <icinga-miraheze>	 PROBLEM - jobrunner3 Current Load on jobrunner3 is CRITICAL: CRITICAL - load average: 6.95, 5.80, 4.49
[00:59:05] <icinga-miraheze>	 PROBLEM - jobrunner4 Current Load on jobrunner4 is WARNING: WARNING - load average: 3.70, 5.23, 5.52
[01:05:04] <icinga-miraheze>	 RECOVERY - jobrunner4 Current Load on jobrunner4 is OK: OK - load average: 3.06, 4.01, 4.88
[01:10:58] <icinga-miraheze>	 PROBLEM - jobrunner3 Current Load on jobrunner3 is WARNING: WARNING - load average: 4.00, 5.12, 5.97
[01:18:58] <icinga-miraheze>	 RECOVERY - jobrunner3 Current Load on jobrunner3 is OK: OK - load average: 2.81, 3.49, 4.84
[06:02:48] <icinga-miraheze>	 RECOVERY - rdb4 APT on rdb4 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:05:22] <icinga-miraheze>	 RECOVERY - services4 APT on services4 is OK: APT OK: 27 packages available for upgrade (0 critical updates).
[06:06:22] <icinga-miraheze>	 RECOVERY - ldap2 APT on ldap2 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:08:47] <icinga-miraheze>	 RECOVERY - bacula2 APT on bacula2 is OK: APT OK: 1 packages available for upgrade (0 critical updates).
[06:10:37] <icinga-miraheze>	 RECOVERY - db11 APT on db11 is OK: APT OK: 65 packages available for upgrade (0 critical updates).
[06:11:31] <icinga-miraheze>	 RECOVERY - jobrunner3 APT on jobrunner3 is OK: APT OK: 32 packages available for upgrade (0 critical updates).
[06:13:10] <icinga-miraheze>	 RECOVERY - db12 APT on db12 is OK: APT OK: 65 packages available for upgrade (0 critical updates).
[06:14:22] <icinga-miraheze>	 RECOVERY - mw9 APT on mw9 is OK: APT OK: 1 packages available for upgrade (0 critical updates).
[06:14:34] <icinga-miraheze>	 RECOVERY - services3 APT on services3 is OK: APT OK: 27 packages available for upgrade (0 critical updates).
[06:14:36] <icinga-miraheze>	 RECOVERY - cp10 APT on cp10 is OK: APT OK: 25 packages available for upgrade (0 critical updates).
[06:16:04] <icinga-miraheze>	 RECOVERY - cloud4 APT on cloud4 is OK: APT OK: 35 packages available for upgrade (0 critical updates).
[06:17:47] <icinga-miraheze>	 RECOVERY - puppet3 APT on puppet3 is OK: APT OK: 30 packages available for upgrade (0 critical updates).
[06:18:11] <icinga-miraheze>	 RECOVERY - mw10 APT on mw10 is OK: APT OK: 29 packages available for upgrade (0 critical updates).
[06:19:29] <icinga-miraheze>	 RECOVERY - test3 APT on test3 is OK: APT OK: 29 packages available for upgrade (0 critical updates).
[06:19:48] <icinga-miraheze>	 RECOVERY - graylog2 APT on graylog2 is OK: APT OK: 26 packages available for upgrade (0 critical updates).
[06:22:58] <icinga-miraheze>	 RECOVERY - mail2 APT on mail2 is OK: APT OK: 31 packages available for upgrade (0 critical updates).
[06:26:51] <icinga-miraheze>	 RECOVERY - ns2 APT on ns2 is OK: APT OK: 25 packages available for upgrade (0 critical updates).
[06:29:45] <icinga-miraheze>	 RECOVERY - ns1 APT on ns1 is OK: APT OK: 22 packages available for upgrade (0 critical updates).
[06:30:10] <icinga-miraheze>	 RECOVERY - cp12 APT on cp12 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:34:44] <icinga-miraheze>	 RECOVERY - cloud5 APT on cloud5 is OK: APT OK: 35 packages available for upgrade (0 critical updates).
[06:40:37] <icinga-miraheze>	 RECOVERY - phab2 APT on phab2 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:41:01] <icinga-miraheze>	 RECOVERY - gluster3 APT on gluster3 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:42:34] <icinga-miraheze>	 RECOVERY - cloud3 APT on cloud3 is OK: APT OK: 97 packages available for upgrade (0 critical updates).
[06:42:53] <icinga-miraheze>	 RECOVERY - cp3 APT on cp3 is OK: APT OK: 26 packages available for upgrade (0 critical updates).
[06:44:12] <icinga-miraheze>	 RECOVERY - rdb3 APT on rdb3 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[06:44:22] <icinga-miraheze>	 RECOVERY - mw11 APT on mw11 is OK: APT OK: 29 packages available for upgrade (0 critical updates).
[06:45:09] <icinga-miraheze>	 RECOVERY - jobrunner4 APT on jobrunner4 is OK: APT OK: 30 packages available for upgrade (0 critical updates).
[06:45:25] <icinga-miraheze>	 RECOVERY - mon2 APT on mon2 is OK: APT OK: 25 packages available for upgrade (0 critical updates).
[06:49:26] <icinga-miraheze>	 RECOVERY - db13 APT on db13 is OK: APT OK: 27 packages available for upgrade (0 critical updates).
[06:49:32] <icinga-miraheze>	 RECOVERY - cp11 APT on cp11 is OK: APT OK: 25 packages available for upgrade (0 critical updates).
[06:52:35] <icinga-miraheze>	 RECOVERY - mw8 APT on mw8 is OK: APT OK: 29 packages available for upgrade (0 critical updates).
[06:54:40] <icinga-miraheze>	 RECOVERY - gluster4 APT on gluster4 is OK: APT OK: 24 packages available for upgrade (0 critical updates).
[07:32:06] <icinga-miraheze>	 PROBLEM - ping4 on cp3 is CRITICAL: PING CRITICAL - Packet loss = 0%, RTA = 337.46 ms
[07:34:09] <icinga-miraheze>	 PROBLEM - ping4 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 257.84 ms
[07:58:21] <icinga-miraheze>	 PROBLEM - cp3 Current Load on cp3 is WARNING: WARNING - load average: 1.41, 1.95, 1.30
[08:00:19] <icinga-miraheze>	 PROBLEM - cp3 Current Load on cp3 is CRITICAL: CRITICAL - load average: 3.77, 2.40, 1.52
[08:02:17] <icinga-miraheze>	 PROBLEM - cp3 Current Load on cp3 is WARNING: WARNING - load average: 1.11, 1.78, 1.39
[08:04:15] <icinga-miraheze>	 RECOVERY - cp3 Current Load on cp3 is OK: OK - load average: 0.98, 1.50, 1.34
[08:38:02] <icinga-miraheze>	 RECOVERY - ping4 on cp3 is OK: PING OK - Packet loss = 0%, RTA = 248.83 ms
[08:44:16] <icinga-miraheze>	 PROBLEM - ping4 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 257.97 ms
[08:56:49] <icinga-miraheze>	 RECOVERY - ping6 on dbbackup2 is OK: PING OK - Packet loss = 0%, RTA = 99.96 ms
[09:00:55] <icinga-miraheze>	 PROBLEM - ping6 on dbbackup2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 100.69 ms
[09:31:42] <Not-7024>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtKYU
[09:31:44] <Not-7024>	 [02miraheze/puppet] 07paladox 0359f83bd - Set higher ping for dbbackup2
[09:37:42] <icinga-miraheze>	 RECOVERY - ping6 on dbbackup2 is OK: PING OK - Packet loss = 0%, RTA = 99.97 ms
[09:43:52] <icinga-miraheze>	 PROBLEM - ping6 on dbbackup2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 100.26 ms
[09:50:32] <icinga-miraheze>	 RECOVERY - ping6 on dbbackup2 is OK: PING OK - Packet loss = 0%, RTA = 100.55 ms
[10:35:57] <MH-Discord>	 <Reception123> @RhinosF1 please do set priorities for tasks https://phabricator.miraheze.org/T6837, there's no need to leave them untriaged
[10:35:58] <MirahezeBot>	 [ ⚓ T6837 Deal with rDNS alerts ] - phabricator.miraheze.org
[15:32:13] <Not-7024>	 [02landing] 07phtlay opened pull request 03#62: Fix typo in English message - 13https://git.io/JtKgK
[15:33:15] <miraheze-github>	 miraheze/landing - phtlay the build passed.
[15:34:57] <Not-7024>	 [02landing] 07dmehus commented on pull request 03#62: Fix typo in English message - 13https://git.io/JtKgy
[15:38:46] <Not-7024>	 [02miraheze/landing] 07Universal-Omega pushed 032 commits to 03master [+0/-0/±2] 13https://git.io/JtKgN
[15:38:47] <Not-7024>	 [02miraheze/landing] 07phtlay 03593b8d2 - Fix typo in English message
[15:38:49] <Not-7024>	 [02miraheze/landing] 07Universal-Omega 03bc76b7b - Merge pull request #62 from phtlay/master
[15:38:50] <Not-7024>	 [02landing] 07Universal-Omega closed pull request 03#62: Fix typo in English message - 13https://git.io/JtKgK
[15:39:52] <miraheze-github>	 miraheze/landing - Universal-Omega the build passed.
[16:42:17] <JohnLewis>	 SPF|Cloud: fyi https://phabricator.miraheze.org/T4019#134828
[16:42:18] <MirahezeBot>	 [ ⚓ T4019 Encrypt Redis traffic ] - phabricator.miraheze.org
[16:59:23] <paladox>	 we can build php-redis JohnLewis 
[17:05:44] <paladox>	 -rwxr-xr-x 1 root root 3.6M Feb 11 17:04 redis.so
[17:05:48] <paladox>	 very easy to build it
[17:05:50] <JohnLewis>	 paladox: I'm aware we can, but there's no pressing need to require it to be built. Alternatively, you can pin the bullseye repo
[17:06:13] <paladox>	 oh yeh, but wouldn't that version be built against a newer php version?
[17:06:30] <JohnLewis>	 But it goes against our desire to minimise many repos, local software etc.
[17:25:11] <paladox>	 sure i guess.
[17:25:12] <paladox>	 well bullseye i guess gets released in the summer
[17:56:08] <Not-7024>	 [02miraheze/WikiDiscover] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtK6O
[17:56:10] <Not-7024>	 [02miraheze/WikiDiscover] 07translatewiki 03855bdbb - Localisation updates from https://translatewiki.net.
[17:56:11] <MirahezeBot>	 [ Main page - translatewiki.net ] - translatewiki.net
[17:56:11] <Not-7024>	 [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtK63
[17:56:13] <Not-7024>	 [02miraheze/MirahezeMagic] 07translatewiki 03f8afb43 - Localisation updates from https://translatewiki.net.
[17:56:14] <MirahezeBot>	 [ Main page - translatewiki.net ] - translatewiki.net
[17:56:14] <Not-7024>	 [02miraheze/DataDump] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtK6s
[17:56:16] <Not-7024>	 [02miraheze/DataDump] 07translatewiki 03bc73461 - Localisation updates from https://translatewiki.net.
[17:56:17] <MirahezeBot>	 [ Main page - translatewiki.net ] - translatewiki.net
[17:57:07] <miraheze-github>	 miraheze/MirahezeMagic - translatewiki the build passed.
[17:57:08] <miraheze-github_>	 miraheze/DataDump - translatewiki the build passed.
[17:57:15] <miraheze-github_>	 miraheze/WikiDiscover - translatewiki the build passed.
[18:17:51] <icinga-miraheze>	 PROBLEM - wiki.finnsoftware.net - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.finnsoftware.net reverse DNS resolves to cdn-185-199-108-153.github.com
[18:26:04] <Not-7024>	 [02miraheze/ssl] 07Reception123 pushed 035 commits to 03master [+0/-5/±4] 13https://git.io/JtKi7
[18:26:05] <Not-7024>	 [02miraheze/ssl] 07Reception123 0320718b3 - remove data.maantietaja.org No longer pointing
[18:26:07] <Not-7024>	 [02miraheze/ssl] 07Reception123 035d3dc45 - remove evenair.tk No longer pointing
[18:26:08] <Not-7024>	 [02miraheze/ssl] 07Reception123 03ab2cb67 - remove www.museummiddelland.nl No longer pointing
[18:26:10] <Not-7024>	 [02miraheze/ssl] ... and 2 more commits.
[18:30:59] <Reception123>	 JohnLewis: are you able to access https://phabricator.miraheze.org/T6837#134791 these links?
[18:31:00] <MirahezeBot>	 [ ⚓ T6837 Deal with rDNS alerts ] - phabricator.miraheze.org
[18:31:09] <Reception123>	 Rhinos says he can access them but for me it gives the exception I listed below
[18:31:19] <Reception123>	 and yes, I am logged in ;)
[18:31:21] * dmehus is looking
[18:31:28] <Reception123>	 dmehus: you won't be, you're  not a syasdmin!
[18:31:51] <dmehus>	 Reception123, guest account :)
[18:32:34] <JohnLewis>	 Reception123: they work for me
[18:32:44] <dmehus>	 they work for me as well
[18:33:13] <dmehus>	 *assuming you meant the icinga links, not the wikis
[18:34:07] <Reception123>	 JohnLewis: really, that's odd, I'm getting that exception
[18:34:23] <Reception123>	 why is my account being discriminated against :'(
[18:34:28] <JohnLewis>	 Reception123: what's the full exception? Surely it doesn't go straight into the stack trace
[18:34:56] <Reception123>	 this is everything https://usercontent.irccloud-cdn.com/file/djlE8Vwf/image.png
[18:35:13] <JohnLewis>	 hhm
[18:35:59] <icinga-miraheze>	 PROBLEM - mw10 Puppet on mw10 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:36:01] <paladox>	 oh
[18:36:01] <Reception123>	 JohnLewis: I can see other errors though, like test3 puppet not working
[18:36:04] <paladox>	 let me fix it
[18:36:09] <icinga-miraheze>	 PROBLEM - mw9 Puppet on mw9 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:36:23] <icinga-miraheze>	 PROBLEM - jobrunner3 Puppet on jobrunner3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:36:25] <icinga-miraheze>	 PROBLEM - mw8 Puppet on mw8 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:36:29] <paladox>	 wait
[18:36:55] <Reception123>	 ^ fixing that (the cert thing)
[18:37:03] <icinga-miraheze>	 PROBLEM - mw11 Puppet on mw11 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:37:05] <paladox>	 hmm
[18:37:12] <paladox>	 Reception123 did you log out and back in?
[18:37:23] <icinga-miraheze>	 PROBLEM - jobrunner4 Puppet on jobrunner4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:37:38] <Reception123>	 paladox: I can try that, but I did check this morning, was logged out in the meantime and logged in again
[18:37:40] <Reception123>	 but I'll try again
[18:37:46] <paladox>	 oh
[18:38:00] <paladox>	 trying again wouldn't make a difference only if you were logged in already
[18:38:01] <Reception123>	 paladox: same thing :(
[18:38:16] <Reception123>	 I can see other errors but not the cert ones 
[18:38:49] <paladox>	 https://github.com/miraheze/puppet/commit/e6e9b611e424659c16cbca6e2b2c55fed3377751#diff-4364f2310d3cf97d4c6c401c24d64109b572f5f2bec995f21971ab941b00f926
[18:38:50] <MirahezeBot>	 [ restructure icinga group roles · miraheze/puppet@e6e9b61 · GitHub ] - github.com
[18:39:06] <paladox>	 i think sre-mediawiki is conflicting
[18:39:07] <icinga-miraheze>	 PROBLEM - cp11 Puppet on cp11 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl]
[18:40:28] <Reception123>	 yeah I did imagine it was something like that
[18:41:52] <JohnLewis>	 paladox: I added myself to sre-mediawiki and I can still view them
[18:42:04] <paladox>	 JohnLewis you logged out and back in?
[18:42:25] <JohnLewis>	 nope, but now I have, I can reproduce
[18:44:06] <JohnLewis>	 Though why is Rhinos able to view them, considering memberships are the same, baring Reception123 should have admin on top - technically Rhinos shouldn't be able to view sslhost if only sre-mediawiki is applying and not sre-mediawiki-view
[18:44:28] <Reception123>	 but dmehus can view them as a 'guest'
[18:44:44] <JohnLewis>	 guest has view for all
[18:45:14] <JohnLewis>	 Which should also be applying here as well via sre-mediawiki-view
[18:46:47] <Reception123>	 hmm
[18:47:06] <dmehus>	 yeah, I imagine it's sort of like wiki permissions that the lower level view rights should apply to the higher order groups
[18:47:41] <icinga-miraheze>	 PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl],File[www.museummiddelland.nl_private]
[18:48:02] <dmehus>	 and why is RhinosF1 on Phabricator but not IRC? If one is active on Phabricator, it holds they should be in #miraheze-sre to communicate with colleagues on issues
[18:51:17] <Not-7024>	 [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtKXc
[18:51:18] <Not-7024>	 [02miraheze/ssl] 07Reception123 03d72bc63 - fix
[18:54:04] <icinga-miraheze>	 PROBLEM - mon2 Puppet on mon2 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 3 minutes ago with 0 failures
[18:55:28] <icinga-miraheze>	 PROBLEM - cp12 Puppet on cp12 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl],File[www.museummiddelland.nl_private]
[18:56:07] <icinga-miraheze>	 PROBLEM - cp10 Puppet on cp10 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): File[www.museummiddelland.nl],File[www.museummiddelland.nl_private]
[19:04:04] <icinga-miraheze>	 RECOVERY - mw9 Puppet on mw9 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures
[19:04:11] <icinga-miraheze>	 RECOVERY - mw8 Puppet on mw8 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures
[19:04:11] <icinga-miraheze>	 RECOVERY - jobrunner4 Puppet on jobrunner4 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures
[19:04:14] <icinga-miraheze>	 RECOVERY - jobrunner3 Puppet on jobrunner3 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures
[19:04:56] <icinga-miraheze>	 RECOVERY - mw11 Puppet on mw11 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[19:05:30] <icinga-miraheze>	 RECOVERY - mw10 Puppet on mw10 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[19:06:30] <icinga-miraheze>	 RECOVERY - cp11 Puppet on cp11 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[19:08:33] <Reception123>	 paladox: after you figure out my issue, do you think you could have a look at https://phabricator.miraheze.org/T6843 ? I'm not sure how the file would've "disappeared" like that
[19:08:34] <MirahezeBot>	 [ ⚓ T6843 Uploaded image is missing (returns 404 Not Found) ] - phabricator.miraheze.org
[19:09:01] <Not-7024>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JtK1C
[19:09:02] <Not-7024>	 [02miraheze/puppet] 07paladox 03bcec70a - icingaweb2: Work around an issue with groups
[19:09:04] <Not-7024>	 [02puppet] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbiAS
[19:09:05] <Not-7024>	 [02puppet] 07paladox opened pull request 03#1643: icingaweb2: Work around an issue with groups - 13https://git.io/JtK1l
[19:09:27] <Not-7024>	 [02puppet] 07paladox edited pull request 03#1643: icingaweb2: Work around an issue with groups - 13https://git.io/JtK1l
[19:10:51] <Not-7024>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JtK12
[19:10:52] <Not-7024>	 [02miraheze/puppet] 07paladox 03a7347a4 - Update roles.ini.erb
[19:10:54] <Not-7024>	 [02puppet] 07paladox synchronize pull request 03#1643: icingaweb2: Work around an issue with groups - 13https://git.io/JtK1l
[19:12:34] <dmehus>	 Reception123, did it get missed in the migration possibly? Did we verify the file sizes copied to the new server matched exactly the file sizes from the old server?
[19:13:19] <Reception123>	 that's why I'm asking paladox, I don't know the answer to that question :D
[19:15:31] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[19:23:35] <icinga-miraheze>	 RECOVERY - cp12 Puppet on cp12 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures
[19:23:51] <icinga-miraheze>	 RECOVERY - cp10 Puppet on cp10 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[19:27:16] <dmehus>	 Reception123, yeah...
[19:29:52] <dmehus>	 JohnLewis, if you get a chance, mind taking look at `polskajestwiki`? I had Zppix run an SQL SELECT query to confirm the date of last RC edit/log entry, which was October 11, 2020. Wiki is still showing as 'active'. How come it never went inactive and closed on December 11, 2020?
[19:31:59] <dmehus>	 JohnLewis, Disregard ^. I figured it out. Some edits were bot edits on February 13th
[19:32:10] <dmehus>	 https://polskajest.miraheze.org/wiki/Specjalna:Ostatnie_zmiany?reviewStatus=manual;auto&limit=50&days=180&enhanced=1&urlversion=2
[19:32:12] <MirahezeBot>	 [ Ostatnie zmiany – PJJLNA ] - polskajest.miraheze.org
[19:39:48] <Not-7024>	 [02puppet] 07JohnFLewis closed pull request 03#1643: icingaweb2: Work around an issue with groups - 13https://git.io/JtK1l
[19:40:19] <JohnLewis>	 paladox: ^ I'll talk to Reception about that as from messages, seems we need to make a decision about level of access
[19:40:37] <paladox>	 ok
[19:40:46] <paladox>	 see your dms
[19:50:23] <Not-7024>	 [02miraheze/puppet] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtKD5
[19:50:24] <Not-7024>	 [02miraheze/puppet] 07JohnFLewis 032948dab - give sre-mediawiki basic monitoring permissions globally with icinga
[20:53:28] <icinga-miraheze>	 PROBLEM - cp12 Current Load on cp12 is CRITICAL: CRITICAL - load average: 2.27, 1.75, 1.23
[20:55:25] <icinga-miraheze>	 RECOVERY - cp12 Current Load on cp12 is OK: OK - load average: 0.93, 1.48, 1.20