[00:00:25] <MH-Discord>	 <Lake> oh yeah, just to alert SPF: Universal Omega is on vacation, they'll reply you in a few days
[00:11:16] <icinga-miraheze>	 PROBLEM - cloud3 Puppet on cloud3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:11:33] <icinga-miraheze>	 PROBLEM - ping4 on cloud3 is CRITICAL: PING CRITICAL - Packet loss = 60%, RTA = 257.04 ms
[00:13:13] <icinga-miraheze>	 RECOVERY - cloud3 Puppet on cloud3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[00:13:34] <icinga-miraheze>	 RECOVERY - ping4 on cloud3 is OK: PING OK - Packet loss = 0%, RTA = 0.30 ms
[00:40:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJcv
[00:40:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot 032fdb47b - BOT: Updating services config for wikis
[01:43:59] <icinga-miraheze>	 PROBLEM - ns1 Current Load on ns1 is CRITICAL: CRITICAL - load average: 1.71, 2.31, 1.15
[01:45:54] <icinga-miraheze>	 RECOVERY - ns1 Current Load on ns1 is OK: OK - load average: 0.04, 1.04, 0.89
[02:13:17] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is CRITICAL: CRITICAL - NGINX Error Rate is 60%
[02:15:14] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 16%
[02:40:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJWw
[02:40:19] <Not>	 [02miraheze/services] 07MirahezeSSLBot 038313a8d - BOT: Updating services config for wikis
[05:05:11] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJR1
[05:05:12] <Not>	 [02miraheze/services] 07MirahezeSSLBot 0364e947e - BOT: Updating services config for wikis
[05:41:35] <Not>	 [02miraheze/mediawiki] 07Reception123 pushed 031 commit to 03REL1_34 [+1/-0/±1] 13https://git.io/JUJEc
[05:41:37] <Not>	 [02miraheze/mediawiki] 07Reception123 03cf5521c - Install Medik skin
[05:47:08] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-3 [+0/-0/±4] 13https://git.io/JUJE2
[05:47:10] <Not>	 [02miraheze/mw-config] 07Reception123 036f5c533 - add Medik skin T5888
[05:47:11] <Not>	 [02mw-config] 07Reception123 created branch 03Reception123-patch-3 - 13https://git.io/vbvb3
[05:47:25] <Not>	 [02mw-config] 07Reception123 opened pull request 03#3210: add Medik skin T5888 - 13https://git.io/JUJEw
[05:51:18] <Not>	 [02mw-config] 07Reception123 synchronize pull request 03#3210: add Medik skin T5888 - 13https://git.io/JUJEw
[05:51:20] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-3 [+0/-0/±1] 13https://git.io/JUJEy
[05:51:21] <Not>	 [02miraheze/mw-config] 07Reception123 03b5b901a - Update ManageWikiExtensions.php
[06:14:39] <icinga-miraheze>	 RECOVERY - test2 Puppet on test2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[06:17:05] <Not>	 [02mw-config] 07Reception123 closed pull request 03#3210: add Medik skin T5888 - 13https://git.io/JUJEw
[06:17:07] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±4] 13https://git.io/JUJzJ
[06:17:08] <Not>	 [02miraheze/mw-config] 07Reception123 03f81cff5 - add Medik skin T5888 (#3210) * add Medik skin T5888 * Update ManageWikiExtensions.php
[06:17:10] <Not>	 [02miraheze/mw-config] 07Reception123 deleted branch 03Reception123-patch-3
[06:17:11] <Not>	 [02mw-config] 07Reception123 deleted branch 03Reception123-patch-3 - 13https://git.io/vbvb3
[06:20:50] <icinga-miraheze>	 PROBLEM - indiancannabis.wiki - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'indiancannabis.wiki' expires in 15 day(s) (Thu 10 Sep 2020 06:12:07 GMT +0000).
[06:23:09] <Reception123>	 !log sudo -u www-data php /srv/mediawiki/w/maintenance/mergeMessageFileList.php --output /srv/mediawiki/config/ExtensionMessageFiles.php --wiki loginwiki on mw* and jbr*
[06:23:12] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[06:23:29] <Reception123>	 !log sudo -u www-data php /srv/mediawiki/w/maintenance/rebuildLocalisationCache.php --wiki loginwiki on mw* and jbr*
[06:23:34] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[06:26:41] <icinga-miraheze>	 PROBLEM - test2 Puppet on test2 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]
[06:26:45] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJzZ
[06:26:46] <Not>	 [02miraheze/ssl] 07MirahezeSSLBot 03115f19d - Bot: Update SSL cert for indiancannabis.wiki
[06:29:37] <Not>	 [02mw-config] 07Universal-Omega opened pull request 03#3211: add Medik settings (T5888) - 13https://git.io/JUJzW
[06:30:39] <Not>	 [02mw-config] 07Reception123 reviewed pull request 03#3211 commit - 13https://git.io/JUJzB
[06:33:20] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 22.78, 21.38, 18.07
[06:34:44] <icinga-miraheze>	 RECOVERY - indiancannabis.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'indiancannabis.wiki' will expire on Mon 23 Nov 2020 05:26:38 GMT +0000.
[06:37:16] <Not>	 [02mw-config] 07Universal-Omega synchronize pull request 03#3211: add Medik settings (T5888) - 13https://git.io/JUJzW
[06:38:59] <Not>	 [02mw-config] 07Reception123 commented on pull request 03#3211: add Medik settings (T5888) - 13https://git.io/JUJzA
[06:40:59] <icinga-miraheze>	 PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[06:41:00] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 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]
[06:41:12] <icinga-miraheze>	 PROBLEM - mw7 Puppet on mw7 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]
[06:41:31] <icinga-miraheze>	 PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[06:44:58] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures
[06:45:09] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.54, 18.74, 18.77
[06:45:11] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJgs
[06:45:13] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03e47d784 - BOT: Updating services config for wikis
[06:45:30] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures
[06:46:59] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[06:47:09] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[06:48:31] <Not>	 [02mw-config] 07Universal-Omega synchronize pull request 03#3211: add Medik settings (T5888) - 13https://git.io/JUJzW
[07:01:29] <Not>	 [02mw-config] 07Reception123 closed pull request 03#3211: add Medik settings (T5888) - 13https://git.io/JUJzW
[07:01:30] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJ2U
[07:01:32] <Not>	 [02miraheze/mw-config] 07Universal-Omega 035119acd - add Medik settings (T5888) (#3211) * add Medik settings (T5888) * Update LocalSettings.php * Fix tabbing for Medik settings per T5888
[07:06:40] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUJ24
[07:06:42] <Not>	 [02miraheze/mw-config] 07Reception123 03cd461ae - add Medik to default skins T5888
[08:59:10] <icinga-miraheze>	 PROBLEM - mw7 Puppet on mw7 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]
[09:07:09] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[09:49:25] <Reception123>	 !log MariaDB [metawiki]> DELETE FROM ipblocks WHERE ipb_address OR ipb_user = "RF1_Bot"; (security verification completed)
[09:49:28] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[09:49:33] <Reception123>	 !log also done on testwiki/loginwiki/quircwiki
[09:49:36] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[11:45:12] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUUuh
[11:45:13] <Not>	 [02miraheze/services] 07MirahezeSSLBot 034400604 - BOT: Updating services config for wikis
[11:52:52] <Reception123>	 !log added discord webhook for horriblevyonderswiki
[11:52:56] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[12:14:07] <Reception123>	 !log add discord webhook for marvelousvyonderswiki
[12:14:10] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[12:15:14] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 40%
[12:17:14] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 3%
[12:20:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUUga
[12:20:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot 036cd9364 - BOT: Updating services config for wikis
[12:22:22] <icinga-miraheze>	 PROBLEM - cloud1 Puppet on cloud1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:25] <icinga-miraheze>	 PROBLEM - jobrunner2 Puppet on jobrunner2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:27] <icinga-miraheze>	 PROBLEM - cp9 Puppet on cp9 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:32] <icinga-miraheze>	 PROBLEM - puppet2 Puppet on puppet2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:33] <icinga-miraheze>	 PROBLEM - cloud2 Puppet on cloud2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:34] <icinga-miraheze>	 PROBLEM - phab1 Puppet on phab1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:35] <icinga-miraheze>	 PROBLEM - db11 Puppet on db11 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:39] <icinga-miraheze>	 PROBLEM - rdb2 Puppet on rdb2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:52] <icinga-miraheze>	 PROBLEM - rdb1 Puppet on rdb1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:55] <icinga-miraheze>	 PROBLEM - db13 Puppet on db13 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:58] <icinga-miraheze>	 PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:22:59] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:00] <icinga-miraheze>	 PROBLEM - gluster1 Puppet on gluster1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:05] <icinga-miraheze>	 PROBLEM - db7 Puppet on db7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:09] <icinga-miraheze>	 PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:16] <icinga-miraheze>	 PROBLEM - cp6 Puppet on cp6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:18] <icinga-miraheze>	 PROBLEM - mon1 Puppet on mon1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:20] <icinga-miraheze>	 PROBLEM - bacula2 Puppet on bacula2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:27] <icinga-miraheze>	 PROBLEM - db12 Puppet on db12 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:31] <icinga-miraheze>	 PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:46] <icinga-miraheze>	 PROBLEM - services2 Puppet on services2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:46] <icinga-miraheze>	 PROBLEM - cloud3 Puppet on cloud3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:46] <icinga-miraheze>	 PROBLEM - gluster2 Puppet on gluster2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:47] <icinga-miraheze>	 PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:47] <icinga-miraheze>	 PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:49] <icinga-miraheze>	 PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:52] <icinga-miraheze>	 PROBLEM - cp7 Puppet on cp7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:53] <icinga-miraheze>	 PROBLEM - ldap1 Puppet on ldap1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:55] <icinga-miraheze>	 PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:55] <icinga-miraheze>	 PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:24:00] <icinga-miraheze>	 PROBLEM - mail1 Puppet on mail1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:24:05] <icinga-miraheze>	 PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:31:46] <icinga-miraheze>	 RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures
[12:31:46] <icinga-miraheze>	 RECOVERY - cloud3 Puppet on cloud3 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures
[12:31:48] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures
[12:31:49] <icinga-miraheze>	 RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures
[12:31:53] <icinga-miraheze>	 RECOVERY - ldap1 Puppet on ldap1 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures
[12:31:55] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures
[12:31:55] <icinga-miraheze>	 RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures
[12:32:00] <icinga-miraheze>	 RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures
[12:32:23] <icinga-miraheze>	 RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures
[12:32:31] <icinga-miraheze>	 RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:33] <icinga-miraheze>	 RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:34] <icinga-miraheze>	 RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:35] <icinga-miraheze>	 RECOVERY - db11 Puppet on db11 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:38] <icinga-miraheze>	 RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:51] <icinga-miraheze>	 RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:58] <icinga-miraheze>	 RECOVERY - db13 Puppet on db13 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:01] <icinga-miraheze>	 RECOVERY - gluster1 Puppet on gluster1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:05] <icinga-miraheze>	 RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:16] <icinga-miraheze>	 RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:18] <icinga-miraheze>	 RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:21] <icinga-miraheze>	 RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:27] <icinga-miraheze>	 RECOVERY - db12 Puppet on db12 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:45] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures
[12:33:45] <icinga-miraheze>	 RECOVERY - gluster2 Puppet on gluster2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:52] <icinga-miraheze>	 RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:27] <icinga-miraheze>	 RECOVERY - cp9 Puppet on cp9 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:35:30] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures
[12:36:04] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures
[12:36:25] <icinga-miraheze>	 RECOVERY - jobrunner2 Puppet on jobrunner2 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures
[12:36:59] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:36:59] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:37:09] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:46:03] <avengium>	 hi, is Void here :D
[12:46:25] <avengium>	 is a question, i wanted to ask void something
[12:49:17] <MH-Discord>	 <Lake> he's asleep, I think
[12:51:08] <avengium>	 ok, thanks
[12:53:04] <Reception123>	 oh, looks like I'm too late, maybe I could've answered
[12:56:28] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 38.31, 27.76, 19.27
[13:27:47] <icinga-miraheze>	 PROBLEM - phab1 Current Load on phab1 is WARNING: WARNING - load average: 3.54, 2.57, 1.20
[13:29:41] <icinga-miraheze>	 RECOVERY - phab1 Current Load on phab1 is OK: OK - load average: 0.89, 1.86, 1.09
[13:41:01] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[13:46:59] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[14:31:16] <icinga-miraheze>	 PROBLEM - mon1 Current Load on mon1 is CRITICAL: CRITICAL - load average: 2.95, 5.20, 3.66
[14:31:18] <icinga-miraheze>	 PROBLEM - mw6 Current Load on mw6 is WARNING: WARNING - load average: 7.47, 6.04, 4.61
[14:31:37] <icinga-miraheze>	 PROBLEM - cp7 Current Load on cp7 is CRITICAL: CRITICAL - load average: 18.95, 12.50, 7.73
[14:33:14] <icinga-miraheze>	 RECOVERY - mw6 Current Load on mw6 is OK: OK - load average: 4.10, 5.40, 4.56
[14:35:10] <icinga-miraheze>	 PROBLEM - mon1 Current Load on mon1 is WARNING: WARNING - load average: 1.90, 3.42, 3.28
[14:35:36] <icinga-miraheze>	 PROBLEM - cp7 Current Load on cp7 is WARNING: WARNING - load average: 2.89, 7.65, 6.88
[14:37:07] <icinga-miraheze>	 RECOVERY - mon1 Current Load on mon1 is OK: OK - load average: 1.98, 2.95, 3.12
[14:37:38] <icinga-miraheze>	 RECOVERY - cp7 Current Load on cp7 is OK: OK - load average: 4.46, 6.51, 6.54
[14:54:26] <MH-Discord>	 <MrJaroslavik (OFF)> Hello
[14:56:17] <MH-Discord>	 <MrJaroslavik (OFF)> How is generated "Possible harrasment/vandalism" notice in -cvt-feed? Based on gfilters or anything in SigmaBotMH's code?
[14:56:41] <Reception123>	 I think it would be something in the code
[14:56:51] <Reception123>	 Zppix: ^
[15:17:16] <MH-Discord>	 <RhinosF1> @Reception123; word based
[15:17:24] <Reception123>	 ah
[15:17:29] <Reception123>	 ^ @MrJaroslavik (OFF)
[15:18:17] <MH-Discord>	 <MrJaroslavik (OFF)> Ok
[15:18:46] <MH-Discord>	 <MrJaroslavik (OFF)> I cannot get access, right? Or anyone can copy paste it?
[15:21:48] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 4 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[15:24:18] <icinga-miraheze>	 PROBLEM - mon1 Current Load on mon1 is CRITICAL: CRITICAL - load average: 2.97, 4.39, 3.32
[15:25:15] <icinga-miraheze>	 PROBLEM - cp7 Current Load on cp7 is WARNING: WARNING - load average: 5.13, 7.47, 5.91
[15:25:34] <Reception123>	 @MrJaroslavik (OFF) I think if bot owners want they could share it with you 
[15:25:42] <Reception123>	 since you are GS I wouldn't see any issue with that personally
[15:25:53] <Reception123>	 maybe it could be added to cvtwiki
[15:26:15] <icinga-miraheze>	 PROBLEM - mon1 Current Load on mon1 is WARNING: WARNING - load average: 2.16, 3.66, 3.17
[15:27:14] <icinga-miraheze>	 RECOVERY - cp7 Current Load on cp7 is OK: OK - load average: 2.53, 5.79, 5.49
[15:27:45] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[15:28:12] <icinga-miraheze>	 RECOVERY - mon1 Current Load on mon1 is OK: OK - load average: 1.65, 3.00, 2.99
[15:28:16] <MH-Discord>	 <MrJaroslavik (ON)> Ok
[15:28:30] <MH-Discord>	 <MrJaroslavik (ON)> @Reception123 Reception321 is yours?
[15:28:46] <Reception123>	 @MrJaroslavik (ON) yes, my new testing account
[15:28:55] <Reception123>	 since my old one was tested on with scripts and is no longer usable
[15:28:56] <MH-Discord>	 <MrJaroslavik (ON)> Huh
[15:29:41] <Reception123>	 15:27  User account Reception321 talk contribs block was created by Reception123 talk contribs block ‎(new test account)
[15:29:43] <Reception123>	 it does say I created it :P
[15:30:24] <MH-Discord>	 <MrJaroslavik (ON)> https://cdn.discordapp.com/attachments/435711390544560128/747840305272848545/IMG_20200825_173011.jpg
[15:30:29] <MH-Discord>	 <MrJaroslavik (ON)> Not here
[15:30:30] <MH-Discord>	 <MrJaroslavik (ON)> 😆
[15:30:42] <Reception123>	 ah :D
[15:54:14] <MH-Discord>	 <RhinosF1> @Reception123: you do have shell access to the bot server. It's in /srv/sigmabot/scripts I believe
[15:55:43] <Reception123>	 well yes but technically you are one of the main maintainers so your approval would be nice
[15:58:26] <MH-Discord>	 <Doug> > <Reception123> well yes but technically you are one of the main maintainers so your approval would be nice ^ ❤️  this. @Reception123 is so respectful to the bot's primary maintainers.
[16:00:05] <MH-Discord>	 <Reception123> 🙂 well even though I am technically a maintainer I don't actively do stuff so I think it would be fair to ask the main maintainers before divulging the code
[16:02:16] <icinga-miraheze>	 RECOVERY - db7 Check MariaDB Replication on db7 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s
[16:03:18] <MH-Discord>	 <RhinosF1> @Reception123: I've no issue with it being public. It's litterally just words. You can guess from enough messages some of them.
[16:03:30] <MH-Discord>	 <RhinosF1> My only issue is how nightmarish the code is anyway
[16:04:19] <Reception123>	 ah
[16:24:28] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 20.69, 20.65, 23.68
[16:34:28] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 14.27, 16.46, 20.22
[17:40:59] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 4 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[17:41:04] <Not>	 [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JUUDE
[17:41:05] <Not>	 [02miraheze/ssl] 07Reception123 034e16100 - add wiki.redeemer.live cert
[17:46:59] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[17:47:36] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 19.03, 20.80, 19.22
[17:49:35] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 12.74, 17.35, 18.12
[17:59:16] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 23.30, 19.96, 18.63
[18:01:10] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 27.42, 21.81, 19.42
[18:03:04] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 18.90, 20.50, 19.22
[18:05:00] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.94, 18.71, 18.69
[18:18:21] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.26, 19.97, 18.76
[18:20:17] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 18.74, 19.29, 18.64
[18:21:54] <MH-Discord>	 <MrJaroslavik (ON)> Is Extension:Scribunto installed?
[18:23:56] <icinga-miraheze>	 PROBLEM - db7 Check MariaDB Replication on db7 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 182s
[18:24:05] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.07, 22.04, 19.87
[18:25:56] <icinga-miraheze>	 RECOVERY - db7 Check MariaDB Replication on db7 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s
[18:28:36] <MH-Discord>	 <Doug> > Is Extension:Scribunto installed? @MrJaroslavik (ON) I believe so. I think it's core, no?
[18:29:48] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 13.40, 20.62, 20.48
[18:31:42] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 18.13, 20.04, 20.28
[18:40:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUUSZ
[18:40:19] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03d4f50a5 - BOT: Updating services config for wikis
[19:00:51] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.33, 22.37, 20.04
[19:02:45] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.39, 22.33, 20.33
[19:06:34] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 13.74, 19.15, 19.53
[19:07:58] <icinga-miraheze>	 PROBLEM - db7 Check MariaDB Replication on db7 is CRITICAL: MariaDB replication - both - CRITICAL - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 193s
[19:53:34] <icinga-miraheze>	 PROBLEM - ns1 APT on ns1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[19:53:40] <icinga-miraheze>	 PROBLEM - ns1 Current Load on ns1 is CRITICAL: CRITICAL - load average: 3.18, 2.78, 1.33
[19:55:32] <icinga-miraheze>	 RECOVERY - ns1 APT on ns1 is OK: APT OK: 1 packages available for upgrade (0 critical updates).
[19:55:43] <icinga-miraheze>	 RECOVERY - ns1 Current Load on ns1 is OK: OK - load average: 0.38, 1.50, 1.15
[19:58:54] <MH-Discord>	 <RhinosF1> @Doug: if it's an extension then it's not core
[19:59:11] <MH-Discord>	 <RhinosF1> And i believe it's in ManageWiki
[20:07:10] <icinga-miraheze>	 PROBLEM - jobrunner1 Puppet on jobrunner1 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]
[20:08:38] <icinga-miraheze>	 PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[20:11:15] <MH-Discord>	 <Doug> > @Doug: if it's an extension then it's not core @RhinosF1 yeah, probably bad terminology, meant more like a "core" extension that installed by default on all wikis
[20:11:33] <MH-Discord>	 <Doug> > And i believe it's in ManageWiki yeah, pretty sure I've seen it in there as well
[20:13:34] <MH-Discord>	 <RhinosF1> It can't be both
[20:13:42] <MH-Discord>	 <RhinosF1> Or hang on
[20:13:48] <MH-Discord>	 <RhinosF1> You mean a default extension
[20:13:55] <MH-Discord>	 <RhinosF1> Not a global one or core feature
[20:14:07] <MH-Discord>	 <RhinosF1> I can't remember tbh but not that much is default
[20:16:59] <icinga-miraheze>	 PROBLEM - mw4 Puppet on mw4 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]
[20:18:46] <icinga-miraheze>	 PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[20:18:55] <icinga-miraheze>	 PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[20:20:08] <MH-Discord>	 <Doug> > You mean a default extension @RhinosF1 yeah, either a default extension or a mandatory extension
[20:20:26] <MH-Discord>	 <Doug> There's three classifications, I think, of extensions on [[Extensions]], right?
[20:20:41] <MH-Discord>	 <Doug> It's probably mandatory because of the Scribunto content model, no?
[20:21:24] <MH-Discord>	 <RhinosF1> Content models can be added by extensions
[20:21:31] <MH-Discord>	 <Doug> yeah
[20:21:47] <MH-Discord>	 <RhinosF1> So that's not a reason
[20:22:00] <MH-Discord>	 <Doug> but I haven't seen a Miraheze wiki without a Scribunto content model Module namespace
[20:22:09] <MH-Discord>	 <RhinosF1> But tbh disabling them extensions is fun
[20:22:13] <MH-Discord>	 <RhinosF1> Try a new wiki
[20:22:20] <MH-Discord>	 <RhinosF1> Or check the config files
[20:22:43] <MH-Discord>	 <Doug> yeah
[20:26:36] <icinga-miraheze>	 PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is CRITICAL: CRITICAL - NGINX Error Rate is 77%
[20:28:36] <icinga-miraheze>	 PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is WARNING: WARNING - NGINX Error Rate is 46%
[20:30:36] <icinga-miraheze>	 RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 15%
[20:35:02] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures
[20:35:09] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures
[20:36:37] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:36:48] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:36:54] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[21:07:43] <icinga-miraheze>	 PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is WARNING: WARNING - NGINX Error Rate is 51%
[21:11:43] <icinga-miraheze>	 RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 13%
[21:59:42] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 29.35, 21.85, 15.80
[22:13:42] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 17.92, 22.06, 20.98
[22:17:42] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 24.04, 24.25, 22.24
[22:19:42] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 15.64, 21.16, 21.37
[22:19:57] <icinga-miraheze>	 RECOVERY - db7 Check MariaDB Replication on db7 is OK: MariaDB replication - both - OK - Slave_IO_Running state : Yes, Slave_SQL_Running state : Yes, Seconds_Behind_Master : 0s
[22:27:42] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 11.23, 17.45, 19.90
[23:36:48] <icinga-miraheze>	 PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is CRITICAL: CRITICAL - NGINX Error Rate is 74%
[23:38:48] <icinga-miraheze>	 RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 15%