[00:02:28] PROBLEM - graylog2 Puppet on graylog2 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 2 minutes ago with 6 failures. Failed resources (up to 3 shown) [00:32:27] RECOVERY - graylog2 Puppet on graylog2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:03: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 : 199s [02:05: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 : 39s [02:08:55] [02CreateWiki] 07Universal-Omega synchronize pull request 03#214: Create new invalid status for databases that already exist - 13https://git.io/J3Gub [02:08:57] [02CreateWiki] 07Universal-Omega synchronize pull request 03#214: Create new invalid status for databases that already exist - 13https://git.io/J3Gub [02:09:51] miraheze/CreateWiki - Universal-Omega the build passed. [02:09:52] miraheze/CreateWiki - Universal-Omega the build passed. [02:13:53] [02CreateWiki] 07Universal-Omega opened pull request 03#215: Use textarea type RequestWiki reason field - 13https://git.io/J36M3 [02:14:46] miraheze/CreateWiki - Universal-Omega the build passed. [02:15:28] [02CreateWiki] 07dmehus commented on pull request 03#215: Use textarea type RequestWiki reason field - 13https://git.io/J36ME [02:21:39] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type RequestWiki reason field - 13https://git.io/J36M3 [02:22:17] [02CreateWiki] 07Universal-Omega commented on pull request 03#215: Use textarea type RequestWiki reason field - 13https://git.io/J36yC [02:22:41] miraheze/CreateWiki - Universal-Omega the build passed. [02:37:19] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type RequestWiki reason field - 13https://git.io/J36M3 [02:38:16] miraheze/CreateWiki - Universal-Omega the build passed. [02:39:42] [02CreateWiki] 07Universal-Omega edited pull request 03#215: Use textarea type for RequestWiki reason field - 13https://git.io/J36M3 [02:47:16] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for RequestWiki reason field - 13https://git.io/J36M3 [02:47:36] [02CreateWiki] 07Universal-Omega edited pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [02:48:10] miraheze/CreateWiki - Universal-Omega the build passed. [02:50:44] [02CreateWiki] 07Universal-Omega edited pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [05:17:54] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-1 [+0/-0/±1] 13https://git.io/J3iOL [05:17:55] [02miraheze/mw-config] 07Reception123 03235f168 - remove webhook sitenotice [05:17:57] [02mw-config] 07Reception123 created branch 03Reception123-patch-1 - 13https://git.io/vbvb3 [05:17:58] [02mw-config] 07Reception123 opened pull request 03#3874: remove webhook sitenotice - 13https://git.io/J3iOt [05:18:57] miraheze/mw-config - Reception123 the build passed. [06:07:50] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [06:08:20] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [06:08:50] miraheze/CreateWiki - Universal-Omega the build passed. [06:09:20] miraheze/CreateWiki - Universal-Omega the build passed. [06:11:53] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [06:12:54] miraheze/CreateWiki - Universal-Omega the build passed. [06:36:47] [02mw-config] 07Universal-Omega opened pull request 03#3875: Update and elaborate help message for wgWordmark - 13https://git.io/J3izY [06:37:48] miraheze/mw-config - Universal-Omega the build passed. [06:38:02] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/J3iz4 [06:38:04] [02miraheze/mw-config] 07Universal-Omega 035035d9f - Update and elaborate help message for wgWordmark (#3875) [06:38:05] [02mw-config] 07Reception123 closed pull request 03#3875: Update and elaborate help message for wgWordmark - 13https://git.io/J3izY [06:38:07] [02mw-config] 07Reception123 synchronize pull request 03#3845: Merge 'master' into REL1_36 - 13https://git.io/JOKA0 [06:38:59] miraheze/mw-config - Reception123 the build passed. [07:22:01] @R4356th: you're one of very few but nothing will change without explicit community consensus. You might see a logo finally appear sometime soon on Modern Vector though. [07:22:13] * RhinosF1 personally only had it on today to find faults with it [07:29:04] 👍 [12:37:22] PROBLEM - wiki.mxlinuxusers.de - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.mxlinuxusers.de All nameservers failed to answer the query. [12:44:17] RECOVERY - wiki.mxlinuxusers.de - reverse DNS on sslhost is OK: rDNS OK - wiki.mxlinuxusers.de reverse DNS resolves to cp10.miraheze.org [14:02:48] "I'd just wait until 1.36": sorry for not recalling the reason sooner, but the actual reason why I am trying to fix FlaggedRevs now is that I can't run any bots because I have to patrol their edits afterwards [14:02:59] Which is rather inconvenient. [14:19:51] PROBLEM - bacula2 Disk Space on bacula2 is WARNING: DISK WARNING - free space: / 142043 MB (10% inode=99%); [16:26:51] @Lev, can't you add `autoreview` to your `bot` group? [16:27:27] well, `autoreview` and `autopatrol`, if `autopatrol` isn't in the group already [16:30:59] dmehus: what are you getting at on phab [16:31:08] The meta logo doesn't show on new vector [16:31:18] Yes we're keeping the current behaviour in 1.36 [16:31:47] Yes we know how to do that and the WMF control their own roll out [16:44:27] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 5.52, 4.74, 2.90 [16:46:27] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 1.10, 3.29, 2.59 [16:48:37] dmehus: the problem is that autoreview right is added for all groups that need it, but it does not work [16:55:07] RhinosF1, well, yeah, I mean, all we should need to do is make a separate honeycomb logo sized for New Vector; shouldn't be hard at all. What I'm getting at, though, is that I agree with Reception123 that we should keep Legacy Vector the default setting, and let wikis choose whether they want to make New Vector the default configuration for their wiki [16:55:41] dmehus: oh we plan to keep legacy the default [16:56:00] None of us like new vector and the usage stats at moment are super low [16:56:08] Will probably be an RfC eventually on it [16:56:37] RhinosF1, yeah, possibly, but no rush on the RfC as wikis can always change it to the new Vector [16:56:53] Yeah I don't intend to rush [16:57:49] * RhinosF1 wants to find more ways to break it first [16:57:59] @Lev, oh, do you need FlaggedRevs? Like, for what purpose? It really is duplicative to patrolled revisions; even Wikipedia doesn't use both FlaggedRevs and patrolled revisions on all pages. I'd personally would recommend just using patrolled revisions and, if you need a second one, ApprovedRevs. Also, RhinosF1 said there's a good possibility FlaggedRevs may be demised in a future MediaWiki release [16:58:28] It's being significantly simplified [16:58:36] I don't really wanna mess with it's config too much [16:59:05] Because that means I have work my head round how to fix it for 1.36 again [17:00:02] My changes are not affecting your changes in 1.36, btw. [17:03:09] dmehus: I use it mostly for making sure stable (reviewed) versions show first. If it is unfixable at the current stage, I'll disable it entirely on our wiki, but first I want to try to salvage it if possible. [17:03:47] We don't really have the resources to debug flagged revs [17:04:06] Maybe try ApprovedRevs ? [17:04:59] @Lev, yeah I'm not aware of that particular bug, but if it is indeed a bug, it's likely upstream, so I'd suggest filing a Phabricator task. And yeah, use ApprovedRevs...it's a much simpler extension. FlaggedRevs was never designed to operate on all revisions to pages; it's supposed to ONLY be set up in tandem with a protection level on wikis [17:05:28] s/Phabricator/Wikimedia Phabricator [17:05:28] dmehus meant to say: @Lev, yeah I'm not aware of that particular bug, but if it is indeed a bug, it's likely upstream, so I'd suggest filing a Wikimedia Phabricator task. And yeah, use ApprovedRevs...it's a much simpler extension. FlaggedRevs was never designed to operate on all revisions to pages; it's supposed to ONLY be set up in tandem with a protection level on wikis [17:06:05] I haven't asked to, I understand what a mess it is. I am aware of ApprovedRevs, however, as it is not used on any Wikimedia wiki, I will just drop FlaggedRevs instead if my patch will not fix the problems. [17:06:57] Try to just copy what Wikimedia do is not always a good idea [17:07:02] > FlaggedRevs was never designed to operate on all revisions to pages; it's supposed to ONLY be set up in tandem with a protection level on wikis This is incorrect, I am sorry. Most Wikimedia projects use it for all revisions instead of standard patrolling, only English Wikipedia does otherwise. [17:10:46] @Lev, actually they don't. FlaggedRevs is English Wikipedia's Pending Changes protection. Maybe some Wikimedia projects use it, I'm not sure, but I do know they also use patrolled revisions, which is technically superior and better designed [17:11:37] I meant projects using FlaggedRevs, of course. https://meta.wikimedia.org/wiki/Flagged_Revisions#Flagged_Revisions_on_Wikimedia_projects [17:11:38] [ Flagged Revisions - Meta ] - meta.wikimedia.org [17:12:19] > Try to just copy what Wikimedia do is not always a good idea [17:12:19] :thistbh: Yeah, I agree with that. You're also limiting yourself in terms of extensions, if you only use extensions used by Wikimedia; there's a lot of good extensions out there [17:12:24] @Lev ah okay [17:14:13] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [17:14:34] I get that. But, as I said, I am aware of ApprovedRevs and would still prefer going to standard MediaWiki patrolling if our FlaggedRevs config is unsalvageable. [17:15:13] miraheze/CreateWiki - Universal-Omega the build passed. [17:16:26] @Lev, ah, okay, that's cool :) [17:16:31] [02CreateWiki] 07Universal-Omega edited pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [17:40:47] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [17:41:29] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [17:41:49] miraheze/CreateWiki - Universal-Omega the build passed. [17:41:50] [02CreateWiki] 07dmehus commented on pull request 03#215: Use textarea type for reason field - 13https://git.io/J3Xhq [17:42:24] [02CreateWiki] 07Universal-Omega synchronize pull request 03#215: Use textarea type for reason field - 13https://git.io/J36M3 [17:42:36] The researcher that spammed me has agreed to suspend their research [17:42:37] miraheze/CreateWiki - Universal-Omega the build passed. [17:43:27] miraheze/CreateWiki - Universal-Omega the build passed. [17:46:32] RhinosF1, okay [17:47:04] dmehus: they don't seem to have actually done so yet [17:47:08] But let's see [17:56:41] [02CreateWiki] 07Universal-Omega synchronize pull request 03#210: [DNM] DB_MASTER -> DB_PRIMARY - 13https://git.io/JOcAE [17:57:04] [02CreateWiki] 07Universal-Omega edited pull request 03#210: DB_MASTER -> DB_PRIMARY - 13https://git.io/JOcAE [17:57:27] 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 : 231s [17:57:43] miraheze/CreateWiki - Universal-Omega the build passed. [18:03:25] PROBLEM - dbbackup2 Current Load on dbbackup2 is CRITICAL: CRITICAL - load average: 5.70, 4.26, 2.76 [18:05:25] PROBLEM - dbbackup2 Current Load on dbbackup2 is WARNING: WARNING - load average: 3.19, 3.78, 2.77 [18:09:26] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 2.53, 3.07, 2.72 [18:11:28] 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 : 46s [18:29:27] 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 : 295s [18:35:24] PROBLEM - dbbackup2 Current Load on dbbackup2 is CRITICAL: CRITICAL - load average: 6.06, 4.29, 3.06 [18:39:24] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 2.26, 3.37, 3.00 [18:39:55] !log INSERT INTO slot_roles (role_id, role_name) VALUES (1, 'main'); on wintergatancommunitywiki [18:40:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [18:45:27] 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 : 157s [18:49: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 [18:53:52] PROBLEM - wiki.kali-team.cn - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.kali-team.cn could not be found [19:00:50] RECOVERY - wiki.kali-team.cn - reverse DNS on sslhost is OK: rDNS OK - wiki.kali-team.cn reverse DNS resolves to cp11.miraheze.org [19:07:18] Reception123, what causes those problems where you have to insert values into the `slot_roles` table? [19:07:34] is it something to do with imports from Fandom, with different namespace IDs or something? [19:08:06] Content model changes [19:11:53] Reception123, oh do people change their namespace content model to something else not realizing it messes things up? If so, why can't they just change it back, or does it cause an error and break the wiki? [19:14:02] dmehus: it's a weird corruption issue [19:14:12] In theory it shouldn't happen [19:14:17] But it's been known too [19:25:27] 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 : 286s [19:27:07] there's an upstream task about it even [19:28:05] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-4 [+0/-0/±1] 13https://git.io/J31CA [19:28:07] [02miraheze/mw-config] 07Reception123 03726d3f3 - add T&S to higher password requirements [19:28:08] [02mw-config] 07Reception123 created branch 03Reception123-patch-4 - 13https://git.io/vbvb3 [19:28:10] [02mw-config] 07Reception123 opened pull request 03#3876: add T&S to higher password requirements - 13https://git.io/J31Cp [19:29:17] miraheze/mw-config - Reception123 the build passed. [19:29:38] [02mw-config] 07Reception123 closed pull request 03#3876: add T&S to higher password requirements - 13https://git.io/J31Cp [19:29:40] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/J31Wq [19:29:41] [02miraheze/mw-config] 07Reception123 03839aa59 - add T&S to higher password requirements (#3876) [19:29:43] [02mw-config] 07Reception123 synchronize pull request 03#3845: Merge 'master' into REL1_36 - 13https://git.io/JOKA0 [19:29:44] [02miraheze/mw-config] 07Reception123 deleted branch 03Reception123-patch-4 [19:29:46] [02mw-config] 07Reception123 deleted branch 03Reception123-patch-4 - 13https://git.io/vbvb3 [19:30:42] miraheze/mw-config - Reception123 the build passed. [19:39:10] PROBLEM - dbbackup2 Current Load on dbbackup2 is WARNING: WARNING - load average: 3.00, 3.67, 2.94 [19:40:39] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.24, 6.30, 5.01 [19:41:09] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 2.35, 3.12, 2.82 [19:41:27] 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 : 155s [19:41:54] PROBLEM - cloud4 Current Load on cloud4 is WARNING: WARNING - load average: 22.66, 19.84, 16.45 [19:43:27] 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 : 217s [19:44:39] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 4.54, 5.82, 5.14 [19:45:27] 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 : 69s [19:45:52] RECOVERY - cloud4 Current Load on cloud4 is OK: OK - load average: 12.17, 18.05, 16.73 [19:51:34] PROBLEM - mw11 Current Load on mw11 is CRITICAL: CRITICAL - load average: 8.09, 7.08, 5.94 [19:53:30] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 7.92, 7.06, 6.05 [19:57:24] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 4.65, 6.28, 6.01 [20:05:30] 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 : 235s [20:05:30] PROBLEM - cp10 Current Load on cp10 is WARNING: WARNING - load average: 3.73, 3.87, 2.61 [20:05:40] PROBLEM - cloud4 Current Load on cloud4 is WARNING: WARNING - load average: 21.48, 20.91, 18.62 [20:06:04] PROBLEM - wiki.jumpbound.com - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.jumpbound.com could not be found [20:06:05] PROBLEM - wiki.grottocenter.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.grottocenter.org could not be found [20:06:06] PROBLEM - wiki.umbrel.tech - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.umbrel.tech could not be found [20:07:10] PROBLEM - mw11 Current Load on mw11 is WARNING: WARNING - load average: 5.95, 6.92, 6.39 [20:07:30] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 4.63, 4.09, 2.83 [20:07:39] RECOVERY - cloud4 Current Load on cloud4 is OK: OK - load average: 18.11, 20.39, 18.73 [20:09:05] PROBLEM - dbbackup2 Current Load on dbbackup2 is CRITICAL: CRITICAL - load average: 5.88, 3.93, 2.69 [20:09:06] RECOVERY - mw11 Current Load on mw11 is OK: OK - load average: 3.31, 5.71, 6.01 [20:09:31] PROBLEM - cp10 Current Load on cp10 is WARNING: WARNING - load average: 2.91, 3.60, 2.80 [20:11:05] PROBLEM - dbbackup2 Current Load on dbbackup2 is WARNING: WARNING - load average: 3.66, 3.91, 2.85 [20:11:31] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 1.13, 2.98, 2.70 [20:12:46] RECOVERY - wiki.jumpbound.com - reverse DNS on sslhost is OK: rDNS OK - wiki.jumpbound.com reverse DNS resolves to cp10.miraheze.org [20:12:47] RECOVERY - wiki.grottocenter.org - reverse DNS on sslhost is OK: rDNS OK - wiki.grottocenter.org reverse DNS resolves to cp10.miraheze.org [20:12:50] RECOVERY - wiki.umbrel.tech - reverse DNS on sslhost is OK: rDNS OK - wiki.umbrel.tech reverse DNS resolves to cp10.miraheze.org [20:13:29] 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 : 99s [20:15:06] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 1.95, 3.03, 2.74 [20:16:13] RhinosF1, ack [20:26:16] PROBLEM - storytime.jdstroy.cf - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for storytime.jdstroy.cf could not be found [20:28:28] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/J31g0 [20:28:30] [02miraheze/puppet] 07Southparkfan 03738734f - Remove needrestart package temporarily [20:33:10] RECOVERY - storytime.jdstroy.cf - reverse DNS on sslhost is OK: rDNS OK - storytime.jdstroy.cf reverse DNS resolves to cp11.miraheze.org [20:37:27] 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 : 235s [20:42:59] PROBLEM - dbbackup2 Current Load on dbbackup2 is WARNING: WARNING - load average: 2.92, 3.49, 2.76 [20:44:59] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 2.53, 3.18, 2.74 [20:45:29] 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 : 10s [21:04:25] PROBLEM - cp10 Current Load on cp10 is CRITICAL: CRITICAL - load average: 3.04, 5.40, 3.12 [21:06:25] PROBLEM - cp10 Current Load on cp10 is WARNING: WARNING - load average: 0.91, 3.89, 2.85 [21:08:25] RECOVERY - cp10 Current Load on cp10 is OK: OK - load average: 0.93, 2.88, 2.60 [21:11:29] 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 : 237s [21:12:50] PROBLEM - dbbackup2 Current Load on dbbackup2 is WARNING: WARNING - load average: 3.61, 2.96, 2.14 [21:13:30] 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 : 81s [21:14:49] RECOVERY - dbbackup2 Current Load on dbbackup2 is OK: OK - load average: 2.41, 2.83, 2.20 [21:35:27] 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 : 207s [21:39: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 [21:41:52] PROBLEM - bacula2 Disk Space on bacula2 is CRITICAL: DISK CRITICAL - free space: / 76084 MB (5% inode=99%);