[00:04:01] PROBLEM - dbbackup1 APT on dbbackup1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:08:18] RECOVERY - dbbackup1 APT on dbbackup1 is OK: APT OK: 11 packages available for upgrade (0 critical updates). [00:08:36] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 7.45, 6.23, 5.10 [00:12:36] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 5.78, 6.22, 5.37 [00:21:53] RECOVERY - test3 Puppet on test3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:22:34] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.50, 7.17, 6.35 [00:23:31] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.72, 6.92, 5.84 [00:24:30] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 6.02, 6.79, 6.31 [00:25:28] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 4.94, 6.21, 5.71 [00:25:54] PROBLEM - test3 Puppet on test3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [00:38:04] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.65, 7.07, 6.37 [00:41:14] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.39, 7.25, 6.81 [00:45:51] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 5.64, 6.50, 6.42 [00:47:04] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 9.08, 7.97, 7.23 [00:49:00] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.37, 7.49, 7.13 [00:58:44] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.29, 6.11, 6.61 [01:01:47] PROBLEM - dbbackup1 APT on dbbackup1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [01:03:18] PROBLEM - dbbackup1 PowerDNS Recursor on dbbackup1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [01:03:30] PROBLEM - dbbackup1 Check MariaDB Replication c2 on dbbackup1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [01:04:03] PROBLEM - dbbackup1 Puppet on dbbackup1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [01:04:49] PROBLEM - dbbackup1 SSH on dbbackup1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:07:30] RECOVERY - dbbackup1 PowerDNS Recursor on dbbackup1 is OK: DNS OK: 1.931 second response time. miraheze.org returns 2607:5300:205:200::1c30,51.222.25.132 [01:07:46] PROBLEM - dbbackup1 Check MariaDB Replication c2 on dbbackup1 is UNKNOWN: NRPE: Unable to read output [01:08:04] RECOVERY - dbbackup1 Puppet on dbbackup1 is OK: OK: Puppet is currently enabled, last run 37 minutes ago with 0 failures [01:08:13] RECOVERY - dbbackup1 APT on dbbackup1 is OK: APT OK: 11 packages available for upgrade (0 critical updates). [01:08:49] RECOVERY - dbbackup1 SSH on dbbackup1 is OK: SSH OK - OpenSSH_7.9p1 Debian-10+deb10u2 (protocol 2.0) [01:10:18] PROBLEM - dbbackup1 MariaDB c2 on dbbackup1 is CRITICAL: Can't connect to MySQL server on 'dbbackup1.miraheze.org' (111) [01:11:39] PROBLEM - dbbackup1 Check MariaDB Replication c2 on dbbackup1 is CRITICAL: MariaDB replication - both - CRITICAL - Slave IO State not correct, slave stopped or replication broken! [01:12:13] RECOVERY - dbbackup1 MariaDB c2 on dbbackup1 is OK: Uptime: 282 Threads: 8 Questions: 12 Slow queries: 1 Opens: 16 Flush tables: 1 Open tables: 10 Queries per second avg: 0.042 [01:45:11] PROBLEM - ping6 on bacula2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 119.16 ms [01:49:51] RECOVERY - wiki.mlpwiki.net - reverse DNS on sslhost is OK: rDNS OK - wiki.mlpwiki.net reverse DNS resolves to cp11.miraheze.org [01:53:08] RECOVERY - ping6 on bacula2 is OK: PING OK - Packet loss = 0%, RTA = 89.95 ms [01:58:26] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is WARNING: MariaDB replication - both - WARNING - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 173s [02:02:25] RECOVERY - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s [02:12:26] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 233s [02:14:26] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is WARNING: MariaDB replication - both - WARNING - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 172s [02:16:25] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 291s [02:34:26] RECOVERY - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 44s [04:08:21] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.10, 6.66, 5.61 [04:10:22] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.04, 6.93, 5.83 [04:12:20] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 4.59, 5.91, 5.58 [04:20:20] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.83, 6.53, 5.93 [04:22:21] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 4.82, 6.05, 5.84 [04:22:26] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 323s [04:30:26] RECOVERY - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s [04:53:53] PROBLEM - wiki.mlpwiki.net - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.mlpwiki.net reverse DNS resolves to 192-185-16-85.unifiedlayer.com [06:17:20] RECOVERY - test3 APT on test3 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [06:23:35] RECOVERY - mw9 APT on mw9 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [06:23:56] RECOVERY - mw11 APT on mw11 is OK: APT OK: 25 packages available for upgrade (0 critical updates). [06:40:13] RECOVERY - mw10 APT on mw10 is OK: APT OK: 25 packages available for upgrade (0 critical updates). [06:44:04] RECOVERY - mw8 APT on mw8 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [06:45:59] RECOVERY - jobrunner3 APT on jobrunner3 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [07:00:34] RECOVERY - jobrunner4 APT on jobrunner4 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [07:37:37] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 10.51, 7.02, 3.25 [07:37:47] [02miraheze/mw-config] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-2 [+0/-0/±1] 13https://git.io/JYkHV [07:37:48] [02miraheze/mw-config] 07Universal-Omega 03e0b2a41 - Add "Memcached" to wgIncidentReportingServices [07:37:50] [02mw-config] 07Universal-Omega created branch 03Universal-Omega-patch-2 - 13https://git.io/vbvb3 [07:37:51] [02mw-config] 07Universal-Omega opened pull request 03#3807: Add "Memcached" to wgIncidentReportingServices - 13https://git.io/JYkHw [07:41:26] PROBLEM - cp10 Current Load on cp10 is WARNING: WARNING - load average: 0.48, 3.43, 2.61 [07:43:20] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 2.06, 2.95, 2.52 [07:59:15] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-1/±1] 13https://git.io/JYkda [07:59:16] [02miraheze/ssl] 07Reception123 03112d577 - rm wiki.ddr.red cert (no longer pointing to us) [08:02:01] RECOVERY - test3 Puppet on test3 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [08:28:43] [02mw-config] 07Reception123 closed pull request 03#3806: T4005: use firejail - 13https://git.io/JYT6i [08:28:45] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYkps [08:28:47] [02miraheze/mw-config] 07Universal-Omega 034b2d54b - T4005: use firejail (#3806) [08:28:48] [02mw-config] 07Reception123 deleted branch 03Universal-Omega-patch-1 - 13https://git.io/vbvb3 [08:28:50] [02miraheze/mw-config] 07Reception123 deleted branch 03Universal-Omega-patch-1 [08:29:49] miraheze/mw-config - Reception123 the build passed. [08:38:25] PROBLEM - cp11 Current Load on cp11 is CRITICAL: CRITICAL - load average: 1.01, 4.80, 3.38 [08:40:25] RECOVERY - cp11 Current Load on cp11 is OK: OK - load average: 0.57, 3.36, 3.02 [08:53:10] .tell JohnLewis Hi. Isn't it quite strange that the AI is giving the same score to https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17357#mw-section-request and https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17365#mw-section-request ? [08:53:10] Reception123: I'll pass that on when JohnLewis is around. [08:53:11] [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [08:53:12] [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [08:55:57] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 250s [08:56:47] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-2 [+0/-0/±1] 13https://git.io/JYIfu [08:56:48] [02miraheze/mw-config] 07Reception123 03275c4ee - make none of the above first createwiki purpose [08:56:50] [02mw-config] 07Reception123 created branch 03Reception123-patch-2 - 13https://git.io/vbvb3 [08:56:51] [02mw-config] 07Reception123 opened pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIfg [08:57:54] miraheze/mw-config - Reception123 the build passed. [08:58:15] [02mw-config] 07Reception123 edited pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIfg [08:58:21] [02mw-config] 07Universal-Omega commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIfN [08:58:24] PROBLEM - cp11 Current Load on cp11 is CRITICAL: CRITICAL - load average: 2.43, 6.23, 4.13 [08:59:01] [02mw-config] 07Reception123 commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIJL [09:01:06] [02mw-config] 07Universal-Omega commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIJg [09:01:49] [02mw-config] 07Universal-Omega edited a comment on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYIJg [09:04:22] PROBLEM - cp11 Current Load on cp11 is WARNING: WARNING - load average: 0.67, 3.01, 3.45 [09:06:21] RECOVERY - cp11 Current Load on cp11 is OK: OK - load average: 0.92, 2.37, 3.16 [09:08:44] [02mw-config] 07RhinosF1 commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYITm [09:11:32] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is WARNING: MariaDB replication - both - WARNING - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 146s [09:13:32] RECOVERY - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 78s [10:51:59] PROBLEM - cp11 Current Load on cp11 is CRITICAL: CRITICAL - load average: 1.91, 6.28, 3.82 [10:52:20] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 4.45, 3.64, 1.73 [10:53:30] JohnLewis: hi. Isn't it quite strange that the AI is giving the same score to https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17357#mw-section-request and https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17365#mw-section-request ? [10:53:30] [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [10:53:31] [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [10:53:50] (the message is going to appear again from MirahezeBot, I thought it would send it when you joined but apparently it sends only when there's activity) [10:54:07] . [10:54:07] JohnLewis: 2021-03-25 - 08:53:10UTC tell JohnLewis Hi. Isn't it quite strange that the AI is giving the same score to https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17357#mw-section-request and https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17365#mw-section-request ? [10:54:20] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 1.82, 2.90, 1.69 [10:54:49] It probably is, but also could not be a coincidence, if others aren't giving similar scores [10:55:58] RECOVERY - cp11 Current Load on cp11 is OK: OK - load average: 0.26, 3.06, 3.05 [10:58:58] JohnLewis: yeah, I've found other scores to be quite weird lately [10:59:14] and here it doesn't make much sense for a one character description to get the same score as a decent one [10:59:54] RECOVERY - wiki.mlpwiki.net - reverse DNS on sslhost is OK: rDNS OK - wiki.mlpwiki.net reverse DNS resolves to cp11.miraheze.org [11:00:37] More words, the better and more accurate a score will be - based on history, it defaults to 15 when theres insufficient length [11:01:50] hm, ok [11:03:20] !log reception@jobrunner3:~$ sudo -u www-data php /srv/mediawiki/w/maintenance/importDump.php --wiki gulpiewiki /home/reception/delbackups2/gulpiewiki.xml [11:03:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:06:44] JohnLewis: this is what I mean: https://meta.miraheze.org/wiki/Special:RequestWikiQueue/17368#mw-section-comments [11:06:45] [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org [11:07:00] it's quite weird that this request gets a 0.77 but the other one that was arguably more detailed got 0.15 [11:17:44] It depends on other requests [11:18:02] It might be more detailed, but if the words are mostly used in declined requests, that request will be declined [11:21:17] It's also a limited data set as well because of memory limitations, and it's not been updated since it was introduced as well, so probably the last 1000 requests have no weight on decisions. [11:26:26] oh, I thought we did want the latest requests to have weight considering the new canned response system [11:33:35] It has to be updated manually, and there is no code to give weights to canned responses [11:40:21] oh, I understood there was [11:40:27] what kind of manual update? [12:00:08] There’s a maintenance script in CW [12:41:42] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.99, 5.98, 5.05 [12:41:50] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.21, 6.13, 5.11 [12:43:41] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.72, 5.70, 5.05 [12:43:50] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 4.41, 5.45, 4.99 [12:54:42] PROBLEM - mw11 Check Gluster Clients on mw11 is CRITICAL: PROCS CRITICAL: 0 processes with args '/usr/sbin/glusterfs' [13:03:41] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.48, 6.88, 5.83 [13:05:40] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.64, 7.05, 6.05 [13:07:40] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 4.53, 6.26, 5.89 [13:07:58] 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): Exec[/mnt/mediawiki-static] [13:21:29] so would I run it just like that? [13:23:32] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 7.86, 6.88, 5.81 [13:25:32] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 4.80, 5.92, 5.58 [13:29:32] PROBLEM - mw8 Current Load on mw8 is CRITICAL: CRITICAL - load average: 8.52, 6.86, 5.98 [13:31:31] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 5.64, 6.41, 5.93 [13:32:45] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.58, 6.46, 5.60 [13:35:26] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.28, 7.37, 6.39 [13:35:28] PROBLEM - mw8 Current Load on mw8 is CRITICAL: CRITICAL - load average: 12.30, 8.75, 6.93 [13:37:23] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.51, 6.51, 6.18 [13:37:27] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 5.37, 7.31, 6.62 [13:37:44] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 7.23, 7.36, 6.43 [13:38:49] PROBLEM - mw11 Current Load on mw11 is CRITICAL: CRITICAL - load average: 8.42, 7.32, 6.18 [13:40:44] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 5.46, 6.48, 6.00 [13:41:24] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 5.30, 6.54, 6.51 [13:41:39] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 6.41, 6.67, 6.37 [13:53:58] Is there any procedure for requesting an unmaintained extension to be replaced with a new, largely rewritten version of the extension (in another codebase) maintained by the same group or org? [13:56:31] [02mw-config] 07dmehus commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYLIG [13:56:45] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 19.38, 21.23, 9.81 [13:57:06] PROBLEM - cloud4 Current Load on cloud4 is CRITICAL: CRITICAL - load average: 19.16, 25.18, 17.93 [13:57:28] [02mw-config] 07dmehus commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYLIw [13:59:06] RECOVERY - cloud4 Current Load on cloud4 is OK: OK - load average: 11.15, 20.14, 16.96 [14:10:51] PROBLEM - wiki.mlpwiki.net - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.mlpwiki.net reverse DNS resolves to 192-185-16-85.unifiedlayer.com [14:14:20] PROBLEM - cp10 Current Load on cp10 is WARNING: WARNING - load average: 0.61, 1.48, 3.77 [14:15:42] > Is there any procedure for requesting an unmaintained extension to be replaced with a new, largely rewritten version of the extension (in another codebase) maintained by the same group or org? [14:15:43] R4356th, not sure. Assuming we have the unmaintained extension installed, we'd probably just conduct a security review on the new, replacement extension, and once that passed, install it. If the functionality was identical or substantially identical, it could probably replace the unmaintained extension, yeah, and discussion about that would likely take place on the Phabricator task? [14:18:20] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 0.68, 1.08, 3.08 [14:27:35] 🤔 [14:39:37] > More words, the better and more accurate a score will be - based on history, it defaults to 15 when theres insufficient length [14:39:38] JohnLewis, can you clarify that a bit? Do you mean that so long as the minimum description length is met, the greater the number of words, the higher the CW AI score will be? [14:45:52] No, but it follows the more words there are the more accurate a score will be [15:08:32] [02mw-config] 07dmehus opened pull request 03#3809: Adding Business & Finance category - 13https://git.io/JYLlm [15:09:40] miraheze/mw-config - dmehus the build passed. [15:12:26] > No, but it follows the more words there are the more accurate a score will be [15:12:26] Well, yeah, but the issue is that many users add extraneous sentences to their description like about why they dislike Fandom so much or that they've been blocked on an another wiki or, worse, that users will be wise to the CW AI scoring and merely add extraneous words to get their wiki request to auto-approval [15:18:00] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.11, 6.84, 6.07 [15:21:54] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 6.00, 6.77, 6.24 [15:25:35] PROBLEM - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is WARNING: MariaDB replication - both - WARNING - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 197s [15:27:33] RECOVERY - dbbackup2 Check MariaDB Replication c3 on dbbackup2 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s [15:29:28] More words == more accurate, not higher score [15:36:27] JohnLewis, though yeah at least that it's more words == more accurate in theory, not necessarily in practice, but ack that it != higher score [15:37:13] In practice it is more accurate, as accurate as the data and previous results can possibly allow [15:37:49] the only harm in accuracy is because of humans making decisions that aren’t justifiable to an automatic algorithm [15:41:27] PROBLEM - services4 APT on services4 is CRITICAL: APT CRITICAL: 26 packages available for upgrade (3 critical updates). [15:43:04] PROBLEM - cp3 APT on cp3 is CRITICAL: APT CRITICAL: 2 packages available for upgrade (2 critical updates). [15:43:27] PROBLEM - services3 APT on services3 is CRITICAL: APT CRITICAL: 26 packages available for upgrade (3 critical updates). [15:45:46] [02mw-config] 07Universal-Omega closed pull request 03#3809: Adding Business & Finance category - 13https://git.io/JYLlm [15:45:47] [02miraheze/mw-config] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYL2S [15:45:49] [02miraheze/mw-config] 07dmehus 038771a6c - Adding Business & Finance category (#3809) [15:46:10] PROBLEM - cloud4 APT on cloud4 is CRITICAL: APT CRITICAL: 46 packages available for upgrade (2 critical updates). [15:46:51] [02mw-config] 07Universal-Omega closed pull request 03#3807: Add "Memcached" to wgIncidentReportingServices - 13https://git.io/JYkHw [15:46:53] [02miraheze/mw-config] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYLaJ [15:46:53] PROBLEM - graylog2 APT on graylog2 is CRITICAL: APT CRITICAL: 24 packages available for upgrade (2 critical updates). [15:46:54] [02miraheze/mw-config] 07Universal-Omega 03f9cf5d0 - Add "Memcached" to wgIncidentReportingServices (#3807) [15:46:56] [02mw-config] 07Universal-Omega deleted branch 03Universal-Omega-patch-2 - 13https://git.io/vbvb3 [15:46:57] [02miraheze/mw-config] 07Universal-Omega deleted branch 03Universal-Omega-patch-2 [15:46:59] miraheze/mw-config - Universal-Omega the build passed. [15:47:01] > In practice it is more accurate, as accurate as the data and previous results can possibly allow [15:47:01] Okay, fair enough [15:47:01] > the only harm in accuracy is because of humans making decisions that aren’t justifiable to an automatic algorithm [15:47:01] Right, but the concern is that until we can have the AI overcome humans creating wiki descriptions that extraneously long and irrelevant, I wouldn't feel comfortable with the CW AI auto-approving requests below a 0.95 score. [15:47:07] thanks, Universal_Omega [15:47:24] No problem dmehus! [15:47:59] miraheze/mw-config - Universal-Omega the build passed. [15:48:35] RECOVERY - graylog2 APT on graylog2 is OK: APT OK: 22 packages available for upgrade (0 critical updates). [15:48:41] RECOVERY - services3 APT on services3 is OK: APT OK: 23 packages available for upgrade (0 critical updates). [15:48:48] RECOVERY - cloud4 APT on cloud4 is OK: APT OK: 44 packages available for upgrade (0 critical updates). [15:49:05] RECOVERY - cp3 APT on cp3 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [15:49:30] RECOVERY - services4 APT on services4 is OK: APT OK: 23 packages available for upgrade (0 critical updates). [15:49:37] !log install security updates on all hosts [15:49:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:50:48] RECOVERY - mw11 Check Gluster Clients on mw11 is OK: PROCS OK: 1 process with args '/usr/sbin/glusterfs' [15:52:20] PROBLEM - mon2 APT on mon2 is CRITICAL: APT CRITICAL: 9 packages available for upgrade (3 critical updates). [15:53:16] AI is good at yes/no tasks, which is what creating a wiki should be. If people make it a complex task, you’ll never be able to make it an automatic method without creating such a complex model we can’t run on our current platform [15:53:44] You’d be entering neutral networking technology if it no longer becomes a yes/no task [15:54:46] RECOVERY - mon2 APT on mon2 is OK: APT OK: 6 packages available for upgrade (0 critical updates). [15:55:36] PROBLEM - mw9 Check Gluster Clients on mw9 is CRITICAL: PROCS CRITICAL: 0 processes with args '/usr/sbin/glusterfs' [15:56:34] !log upgrade grafana on mon2 [15:56:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:01:05] RECOVERY - mw9 Check Gluster Clients on mw9 is OK: PROCS OK: 1 process with args '/usr/sbin/glusterfs' [16:05:17] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 7.43, 6.84, 5.97 [16:05:23] RECOVERY - mw11 Puppet on mw11 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:05:40] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.30, 7.28, 6.50 [16:07:16] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 4.96, 6.18, 5.83 [16:07:40] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.83, 7.29, 6.59 [16:11:40] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.76, 6.48, 6.42 [16:12:02] [02mw-config] 07Reception123 commented on pull request 03#3808: make none of the above first createwiki purpose - 13https://git.io/JYL6o [16:19:55] JohnLewis: I assume you mean https://github.com/miraheze/CreateWiki/blob/master/maintenance/createPersistentModel.php [16:19:55] [ CreateWiki/createPersistentModel.php at master · miraheze/CreateWiki · GitHub ] - github.com [16:21:46] Would be nice if the new purpose stuff could be taken into account where it exists [16:23:08] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JYLXw [16:23:09] [02miraheze/ssl] 07Reception123 03aeabbc7 - add wiki.aridia.space cert [16:23:36] Yeah that’s the script [16:26:05] JohnLewis: I assume Owen would be best to look at whether the purpose stuff etc would be useful where it exists [16:26:18] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JYL1l [16:26:19] [02miraheze/ssl] 07Reception123 03fbb4f72 - add wiki.wilderyogi.eu cert [16:30:27] The model used currently is a one feature model [16:32:29] The purpose field also would likely add zero value [16:33:53] JohnLewis, I thought we were going to revise the current model, though? Though I do agree that purpose field could use some revisions. Basing it on the free form description field, which it can't interpret other than length, is a challenge [16:33:55] Okay [16:34:15] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 7.56, 6.98, 6.26 [16:34:17] dmehus: we can update the model for descriptions at any time [16:34:59] RhinosF1, yeah, that'd be good [16:35:34] ‘can’t interpret other than length’ what do you mean? [16:36:15] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 4.99, 6.24, 6.08 [16:36:26] JohnLewis, well how does it interpret the description field? [16:36:36] As words [16:37:41] JohnLewis, okay, well, either way, it needs some improvement, so it can eliminate extraneous information (i.e., information on why the user dislikes Fandom and is migrating to Miraheze) [16:38:04] That’s impossible using the models were able to run [16:38:15] oh :( [16:38:44] If every user complaining about Fandom gets their wikis accepted, complaining about Fandom increases the chances of future requests being accepted [16:42:32] JohnLewis, yeah... that's part of the problem, as subsequent revisions and added information do usually cause the wiki to be approved [16:43:44] It doesn’t matter how many versions it takes [16:48:26] It'll be based on the status as of when the model was created [16:48:35] As we don't keep a history anyway [17:00:06] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.75, 7.34, 6.85 [17:02:03] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.52, 7.61, 6.99 [17:07:56] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 5.69, 7.36, 7.20 [17:11:42] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 1.24, 4.18, 2.55 [17:13:42] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 0.35, 2.89, 2.27 [17:15:49] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 6.29, 6.35, 6.70 [17:20:51] [02puppet] 07Universal-Omega opened pull request 03#1722: Install ghostscript on all mediawiki servers - 13https://git.io/JYLb7 [17:22:24] [02puppet] 07Universal-Omega synchronize pull request 03#1722: Install ghostscript on all mediawiki servers - 13https://git.io/JYLb7 [17:26:16] [02puppet] 07Reception123 closed pull request 03#1722: Install ghostscript on all mediawiki servers - 13https://git.io/JYLb7 [17:26:18] [02miraheze/puppet] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JYLNd [17:26:19] [02miraheze/puppet] 07Universal-Omega 038b4c637 - Install ghostscript on all mediawiki servers (#1722) [17:31:46] [02miraheze/mw-config] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-1 [+0/-0/±1] 13https://git.io/JYLxO [17:31:48] [02miraheze/mw-config] 07Universal-Omega 030eb3d6c - Use firejail for PdfHandler [17:31:49] [02mw-config] 07Universal-Omega created branch 03Universal-Omega-patch-1 - 13https://git.io/vbvb3 [17:31:54] [02mw-config] 07Universal-Omega opened pull request 03#3810: Use firejail for PdfHandler - 13https://git.io/JYLxn [17:33:04] miraheze/mw-config - Universal-Omega the build passed. [17:55:30] The cvt-feed isn't relaying for some reason. [18:03:30] IRC RC feeds are backlogged due to the bluepageswiki import onto Gyannipedia wiki [18:04:00] Okay. [18:05:07] !log restart glusterd on gluster[34] [18:05:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:07:20] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYtfJ [18:07:22] [02miraheze/dns] 07paladox 03d80fc4d - Depool cp10/11 [18:07:40] does this chat work? [18:07:52] yes [18:13:25] !log reboot cp10 and cp11 [18:13:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:15:04] PROBLEM - cp12 Current Load on cp12 is WARNING: WARNING - load average: 1.69, 1.71, 1.28 [18:23:05] PROBLEM - cp12 Current Load on cp12 is CRITICAL: CRITICAL - load average: 2.52, 2.17, 1.68 [18:23:36] SPF|Cloud: ye, things got slow because net splits [18:29:05] PROBLEM - cp12 Current Load on cp12 is WARNING: WARNING - load average: 1.72, 1.94, 1.75 [18:35:06] PROBLEM - cp12 Current Load on cp12 is CRITICAL: CRITICAL - load average: 2.16, 2.23, 1.93 [18:36:59] paladox: is Grafana broken, or is is just me? Asking because "!log upgrade grafana on mon2"/ https://grafana.miraheze.org/explore has been loading for 20 minutes for me. [18:37:00] [ Grafana ] - grafana.miraheze.org [18:37:05] PROBLEM - cp12 Current Load on cp12 is WARNING: WARNING - load average: 1.43, 1.95, 1.87 [18:37:35] works for me [18:38:03] paladox: Hmm. Guess it's just me then. Thanks! [18:38:41] Mine is just stuck saying "Loading Grafana" [18:39:06] PROBLEM - cp12 Current Load on cp12 is CRITICAL: CRITICAL - load average: 2.35, 2.16, 1.96 [18:40:22] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.65, 7.01, 6.02 [18:41:07] PROBLEM - cp12 Current Load on cp12 is WARNING: WARNING - load average: 1.58, 1.91, 1.89 [18:42:19] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.82, 6.95, 6.12 [18:43:07] PROBLEM - cp12 Current Load on cp12 is CRITICAL: CRITICAL - load average: 2.66, 2.08, 1.94 [18:44:17] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 3.31, 5.60, 5.73 [18:45:31] [02miraheze/dns] 07paladox pushed 032 commits to 03master [+0/-0/±2] 13https://git.io/JYtIA [18:45:32] [02miraheze/dns] 07paladox 030fec253 - Revert "Depool cp10/11" [18:45:34] [02miraheze/dns] 07paladox 03fc3b92a - Depool ca [18:46:07] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYtLv [18:46:08] [02miraheze/dns] 07paladox 03c4bf03f - Revert "Depool ca" [18:46:09] oh phabricator is down [18:46:52] oh, it's not anymore, lol, nvm [18:47:00] We're rebooting a few things [18:47:07] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JYtLY [18:47:07] PROBLEM - cp12 Current Load on cp12 is WARNING: WARNING - load average: 1.06, 1.68, 1.82 [18:47:08] [02miraheze/dns] 07paladox 030f480b1 - depool ca [18:49:03] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 7.91, 6.35, 5.57 [18:49:07] RECOVERY - cp12 Current Load on cp12 is OK: OK - load average: 0.38, 1.20, 1.62 [18:50:18] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 9.62, 6.93, 6.17 [18:50:58] PROBLEM - mw9 Current Load on mw9 is CRITICAL: CRITICAL - load average: 8.26, 6.75, 5.79 [18:51:00] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.32, 6.79, 6.08 [18:52:16] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 6.17, 6.75, 6.21 [18:52:53] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 7.55, 6.93, 5.96 [18:52:59] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 5.09, 6.25, 5.97 [18:56:11] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 7.02, 6.97, 6.21 [18:56:46] PROBLEM - mw9 Current Load on mw9 is CRITICAL: CRITICAL - load average: 8.66, 7.33, 6.31 [18:57:04] !log sudo -u www-data php /srv/mediawiki/w/extensions/ManageWiki/maintenance/populateGroupPermissionsWithDefaults.php --wiki lshwiki --overwrite [18:57:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:57:55] !log cp12: apt-get dist-upgrade && reboot [18:57:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:58:06] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 5.33, 6.38, 6.09 [18:58:16] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 8.07, 7.27, 6.57 [18:58:41] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 6.96, 7.06, 6.33 [19:00:16] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.71, 7.11, 6.60 [19:00:38] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 6.10, 6.79, 6.32 [19:01:29] [02miraheze/dns] 07paladox pushed 032 commits to 03master [+0/-0/±2] 13https://git.io/JYtqY [19:01:31] [02miraheze/dns] 07paladox 03f00b664 - Revert "depool ca" [19:01:32] [02miraheze/dns] 07paladox 03cbcef5b - Depool sg [19:02:16] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.66, 6.53, 6.44 [19:03:53] PROBLEM - mw8 Current Load on mw8 is CRITICAL: CRITICAL - load average: 8.76, 7.76, 6.73 [19:04:32] PROBLEM - mw9 Current Load on mw9 is CRITICAL: CRITICAL - load average: 9.25, 8.45, 7.08 [19:05:48] PROBLEM - mw8 Current Load on mw8 is WARNING: WARNING - load average: 5.99, 7.10, 6.62 [19:06:28] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 5.77, 7.34, 6.84 [19:06:47] !log reboot cp3 [19:06:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:07:50] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 4.80, 6.30, 6.38 [19:08:40] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 5.70, 6.56, 6.60 [19:09:11] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.54, 6.95, 6.34 [19:09:30] PROBLEM - cp3 PowerDNS Recursor on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:09:52] PROBLEM - ping6 on cp3 is CRITICAL: PING CRITICAL - Packet loss = 100% [19:09:58] PROBLEM - cp3 Stunnel Http for mon2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:03] PROBLEM - cp3 Current Load on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:07] PROBLEM - cp3 APT on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:16] cp3 doesn't come back apparently [19:10:18] PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:28] PROBLEM - cp3 HTTPS on cp3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:10:30] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb [19:10:32] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:43] PROBLEM - dreamsit.com.br - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:10:51] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 2 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb [19:10:52] PROBLEM - cp3 Stunnel Http for mw11 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:01] PROBLEM - cp3 NTP time on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:09] PROBLEM - cp3 Stunnel Http for mw10 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:11] PROBLEM - cp3 Stunnel Http for mw9 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:23] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 6.33, 6.73, 6.35 [19:11:31] PROBLEM - cp3 Stunnel Http for test3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:38] PROBLEM - cp3 Stunnel Http for mw8 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:51] PROBLEM - Host cp3 is DOWN: PING CRITICAL - Packet loss = 100% [19:14:08] afk [19:15:01] PROBLEM - mw10 Current Load on mw10 is CRITICAL: CRITICAL - load average: 9.19, 7.33, 6.74 [19:15:05] PROBLEM - mw9 Current Load on mw9 is WARNING: WARNING - load average: 7.74, 6.70, 6.55 [19:17:03] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 6.67, 7.17, 6.77 [19:17:05] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 6.41, 6.67, 6.56 [19:19:36] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 6.35, 7.19, 6.75 [19:21:00] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 5.58, 6.40, 6.56 [19:21:39] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 4.97, 6.47, 6.54 [19:25:48] !log depool and repool mw 8,9,10,11 and also dist-upgrade [19:25:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:27:10] PROBLEM - mw10 Current Load on mw10 is WARNING: WARNING - load average: 7.32, 7.09, 6.78 [19:29:26] PROBLEM - mw10 Current Load on mw10 is CRITICAL: connect to address 51.195.236.254 port 5666: Connection refusedconnect to host 51.195.236.254 port 5666: Connection refused [19:29:53] PROBLEM - cp12 Varnish Backends on cp12 is CRITICAL: 1 backends are down. mw10 [19:30:04] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.42, 6.80, 6.59 [19:31:16] PROBLEM - cp11 Varnish Backends on cp11 is CRITICAL: 1 backends are down. mw11 [19:31:17] PROBLEM - mw9 Current Load on mw9 is CRITICAL: CRITICAL - load average: 10.45, 5.43, 2.20 [19:31:26] RECOVERY - mw10 Current Load on mw10 is OK: OK - load average: 3.50, 1.46, 0.54 [19:31:57] PROBLEM - mw8 Current Load on mw8 is CRITICAL: CRITICAL - load average: 8.88, 5.17, 2.18 [19:32:09] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 1.10, 0.30, 0.10 [19:33:00] !log jobrunner[34]: reboot [19:33:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:33:20] RECOVERY - cp11 Varnish Backends on cp11 is OK: All 7 backends are healthy [19:33:39] !log gluster[34]: reboot [19:34:15] RECOVERY - mw8 Current Load on mw8 is OK: OK - load average: 4.62, 5.05, 2.58 [19:34:16] !log gluster[34]: dist-upgrade [19:34:17] RECOVERY - cp12 Varnish Backends on cp12 is OK: All 7 backends are healthy [19:34:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:34:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:35:48] RECOVERY - mw9 Current Load on mw9 is OK: OK - load average: 5.40, 5.30, 2.99 [19:37:06] !log phab2: dist-upgrade & reboot [19:37:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:37:44] !log ldap2: reboot [19:37:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:38:16] !log mail2: dist-upgrade & reboot [19:38:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:40:02] !log services[34]: dist-upgrade & reboot [19:40:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:44:12] !log graylog2: dist-upgrade & reboot [19:44:17] !log puppet2: dist-upgrade & reboot [19:44:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:44:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [19:46:17]