[01:02:28] <paladox>	 !log upgrade grafana - mon1
[01:02:31] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[03:16:56] <icinga-miraheze>	 PROBLEM - gluster2 Disk Space on gluster2 is WARNING: DISK WARNING - free space: / 48986 MB (10% inode=81%);
[03:40:16] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUN31
[03:40:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03b3a7565 - BOT: Updating services config for wikis
[05:10:33] <Not>	 [02miraheze/mediawiki] 07Reception123 pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JUNCa
[05:10:35] <Not>	 [02miraheze/mediawiki] 07Reception123 03347e162 - Update Cargo
[05:19:48] <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]
[05:20:30] <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]
[05:20:37] <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]
[05:20:49] <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]
[05:21:07] <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]
[05:22:29] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures
[05:22:36] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures
[05:22:47] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures
[05:23:07] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures
[05:23:49] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[08:22:50] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 49%
[08:24:46] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 36%
[09:10:01] <MirahezeBot>	 Hello aoam! If you have any questions, feel free to ask and someone should answer soon.
[09:10:35] <aoam>	 Hello, is it possible to migrate our self hosted wiki on miraheze? 
[09:15:35] <aoam>	 I mean not manually
[09:20:48] <Reception123>	 aoam: yes :)
[09:20:56] <Reception123>	 you would need an XML dump that we can import
[10:13:27] <MH-Discord>	 <Avengium (Ángel)> Hi, i was going to edit Gazetteer_of_wikis and i noticed that some wikis were not following alphabetical order. Is ok if i move the place in list of some wikis to follow the alphabetical order?
[10:16:12] <avengium>	 Hi
[10:17:04] <avengium>	 Reception123 , in Gazetteer of wikis, Is ok if i move the place in list of some wikis to follow the alphabetical order?
[10:33:24] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 49%
[10:39:24] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 39%
[10:58:39] <JohnLewis>	 !log restarted Parsoid on services[12]
[10:58:42] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[10:59:41] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 43%
[11:01:35] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 29%
[11:04:52] <avengium>	 Zppix , are you busy?
[11:12:15] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 43%
[11:14:10] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 35%
[11:32:17] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 44%
[11:34:11] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 34%
[12:12:29] <Reception123>	 !log added tuscriaturaswiki discord webhook
[12:12:32] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[12:20:02] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 43%
[12:21:56] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 36%
[12:22:30] <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:22:32] <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:22:33] <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:34] <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:22:37] <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:39] <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:39] <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:40] <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:43] <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:22:47] <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:22:53] <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:58] <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:23:01] <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:05] <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:07] <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:23:11] <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:12] <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:23:13] <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:14] <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:17] <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:21] <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:23:22] <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:23] <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:25] <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:31] <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:23:31] <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:32] <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:37] <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:49] <icinga-miraheze>	 PROBLEM - graylog1 Puppet on graylog1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:51] <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 - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:23:54] <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:24:07] <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:29:44] <Not>	 [02miraheze/mediawiki] 07Reception123 pushed 031 commit to 03REL1_34 [+1/-0/±1] 13https://git.io/JUNxg
[12:29:45] <Not>	 [02miraheze/mediawiki] 07Reception123 031a78034 - Install TranslationNotifications ext.
[12:31:49] <icinga-miraheze>	 RECOVERY - graylog1 Puppet on graylog1 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures
[12:31:52] <icinga-miraheze>	 RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures
[12:31:56] <icinga-miraheze>	 RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures
[12:32:28] <icinga-miraheze>	 RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures
[12:32:33] <icinga-miraheze>	 RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures
[12:32:33] <icinga-miraheze>	 RECOVERY - ldap1 Puppet on ldap1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures
[12:32:40] <icinga-miraheze>	 RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:32:40] <icinga-miraheze>	 RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures
[12:32:41] <icinga-miraheze>	 RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures
[12:32:44] <icinga-miraheze>	 RECOVERY - gluster1 Puppet on gluster1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures
[12:32:54] <icinga-miraheze>	 RECOVERY - db11 Puppet on db11 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:04] <icinga-miraheze>	 RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:08] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:08] <icinga-miraheze>	 RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:10] <Not>	 [02mw-config] 07Reception123 closed pull request 03#3279: Translate: Switch to loading extension.json - 13https://git.io/JUFUp
[12:33:12] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JUNxh
[12:33:12] <icinga-miraheze>	 RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:13] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:13] <Not>	 [02miraheze/mw-config] 07paladox 03dcd90bd - Translate: Switch to loading extension.json (#3279) * Translate: Switch to loading extension.json * Update LocalExtensions.php
[12:33:14] <icinga-miraheze>	 RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:15] <Not>	 [02mw-config] 07Reception123 deleted branch 03paladox-patch-1 - 13https://git.io/vbvb3
[12:33:16] <Not>	 [02miraheze/mw-config] 07Reception123 deleted branch 03paladox-patch-1
[12:33:19] <icinga-miraheze>	 RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:20] <icinga-miraheze>	 RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:21] <icinga-miraheze>	 RECOVERY - cloud3 Puppet on cloud3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:21] <icinga-miraheze>	 RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:29] <icinga-miraheze>	 RECOVERY - db13 Puppet on db13 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:29] <icinga-miraheze>	 RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:30] <icinga-miraheze>	 RECOVERY - db12 Puppet on db12 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:33:37] <icinga-miraheze>	 RECOVERY - gluster2 Puppet on gluster2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:07] <icinga-miraheze>	 RECOVERY - cp9 Puppet on cp9 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:35:11] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures
[12:36:13] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 44%
[12:36:37] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures
[12:37:00] <icinga-miraheze>	 RECOVERY - jobrunner2 Puppet on jobrunner2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:38:06] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 36%
[12:39:20] <Not>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03Reception123-patch-1 [+0/-0/±4] 13https://git.io/JUNpV
[12:39:22] <Not>	 [02miraheze/mw-config] 07Reception123 03bbab891 - add TranslationNotifications per T6259
[12:39:23] <Not>	 [02mw-config] 07Reception123 created branch 03Reception123-patch-1 - 13https://git.io/vbvb3
[12:39:32] <Not>	 [02mw-config] 07Reception123 opened pull request 03#3280: add TranslationNotifications per T6259 - 13https://git.io/JUNpr
[12:42:52] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures
[12:43:58] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:45:18] <Reception123>	 !log sudo /usr/bin/tar --exclude /mnt/mediawiki-static/allthetropeswiki/archive --exclude /mnt/mediawiki-static/allthetropeswiki/deleted --exclude /mnt/mediawiki-static/allthetropeswiki/lockdir --exclude /mnt/mediawiki-static/allthetropeswiki/temp --exclude /mnt/mediawiki-static/allthetropeswiki/thumb -zcvf /mnt/mediawiki-static/dumps/allthetropeswiki06102020.zip /mnt/mediawiki-static/allthetropeswiki/
[12:45:23] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[12:53:26] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures
[12:54:28] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[13:19:13] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.12, 19.50, 17.83
[13:21:11] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 14.43, 17.38, 17.23
[13:40:18] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAJw
[13:40:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot 03c19107d - BOT: Updating services config for wikis
[13:42:58] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.05, 18.41, 17.62
[13:44:58] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 17.86, 18.72, 17.86
[13:50:20] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAUM
[13:50:22] <Not>	 [02miraheze/services] 07MirahezeSSLBot 034f42669 - BOT: Updating services config for wikis
[14:05:24] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 41%
[14:07:24] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 33%
[14:13:45] <icinga-miraheze>	 PROBLEM - wiki.itsuali.tk - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.itsuali.tk could not be found
[14:33:50] <icinga-miraheze>	 PROBLEM - wiki.itsuali.tk - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.itsuali.tk and port 443: No route to hostHTTP CRITICAL - Unable to open TCP socket
[14:34:57] <Spookreeeno>	 !sre ^
[14:35:06] <Spookreeeno>	 Triggering a bt scam alert
[14:35:25] <MH-Discord>	 <RhinosF1> @Site Reliability Engineers
[14:35:31] <Spookreeeno>	 JohnLewis: ^
[14:39:30] <Not>	 [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JUAq6
[14:39:31] <Not>	 [02miraheze/ssl] 07paladox 030fc35e4 - Remove wiki.itsuali.tk ssl certificate
[14:39:33] <Not>	 [02ssl] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vxP9L
[14:39:34] <Not>	 [02ssl] 07paladox opened pull request 03#364: Remove wiki.itsuali.tk ssl certificate - 13https://git.io/JUAqP
[14:39:48] <Not>	 [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-1/±0] 13https://git.io/JUAq1
[14:39:50] <Not>	 [02miraheze/ssl] 07paladox 03f1cfe66 - Delete wiki.itsuali.tk.crt
[14:39:51] <Not>	 [02ssl] 07paladox synchronize pull request 03#364: Remove wiki.itsuali.tk ssl certificate - 13https://git.io/JUAqP
[14:40:07] <Not>	 [02ssl] 07paladox edited pull request 03#364: Remove wiki.itsuali.tk ssl certificate - 13https://git.io/JUAqP
[14:40:17] <Not>	 [02ssl] 07paladox closed pull request 03#364: Remove wiki.itsuali.tk ssl certificate - 13https://git.io/JUAqP
[14:40:18] <Not>	 [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-1/±1] 13https://git.io/JUAq5
[14:40:20] <Not>	 [02miraheze/ssl] 07paladox 03027ecf4 - Remove wiki.itsuali.tk ssl certificate (#364) * Remove wiki.itsuali.tk ssl certificate * Delete wiki.itsuali.tk.crt
[14:40:21] <Not>	 [02miraheze/ssl] 07paladox deleted branch 03paladox-patch-1
[14:40:23] <Not>	 [02ssl] 07paladox deleted branch 03paladox-patch-1 - 13https://git.io/vxP9L
[14:40:43] <Spookreeeno>	 Thanks paladox
[14:40:55] <Spookreeeno>	 Can you unset whatever wiki is using it?
[14:42:18] <paladox>	 MariaDB [mhglobal]> select * from cw_wikis where wiki_url = 'wiki.itsuali.tk';
[14:42:18] <paladox>	 Empty set (0.003 sec)
[14:43:07] <Spookreeeno>	 ok ty
[15:04:56] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 26.86, 21.30, 18.57
[15:06:55] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 20.39, 20.77, 18.70
[15:08:55] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 18.75, 20.38, 18.84
[15:17:39] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAGZ
[15:17:40] <Not>	 [02miraheze/puppet] 07paladox 03df93a84 - varnish: Allow parsoid 120 requests every 10s
[15:21:56] <icinga-miraheze>	 PROBLEM - gluster1 Current Load on gluster1 is CRITICAL: CRITICAL - load average: 8.07, 4.94, 3.04
[15:22:34] <icinga-miraheze>	 PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 3 datacenters are down: 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb, 2001:41d0:800:1056::2/cpweb
[15:22:54] <icinga-miraheze>	 PROBLEM - cp3 Stunnel Http for mw4 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[15:22:58] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.38, 22.60, 19.63
[15:23:35] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 3 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb
[15:24:33] <icinga-miraheze>	 RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online
[15:24:41] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAZs
[15:24:42] <Not>	 [02miraheze/puppet] 07paladox 03b9eb12d - varnish: allow 120/20s for parsoid
[15:24:51] <icinga-miraheze>	 RECOVERY - cp3 Stunnel Http for mw4 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15662 bytes in 2.566 second response time
[15:25:34] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[15:25:56] <icinga-miraheze>	 RECOVERY - gluster1 Current Load on gluster1 is OK: OK - load average: 4.54, 5.63, 3.84
[15:26:55] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 19.11, 21.69, 20.02
[15:26:59] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAZV
[15:27:00] <Not>	 [02miraheze/puppet] 07paladox 0304ba872 - Revert "varnish: allow 120/20s for parsoid" This reverts commit b9eb12da73377ef42919d46371331ecb758cc955.
[15:28:55] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 17.30, 20.19, 19.68
[15:29:02] <icinga-miraheze>	 PROBLEM - cp6 Puppet on cp6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 1 minute ago with 1 failures. Failed resources (up to 3 shown): Service[varnish]
[15:32:56] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 31.40, 24.79, 21.51
[15:33:00] <icinga-miraheze>	 RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures
[15:34:56] <icinga-miraheze>	 PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 19.49, 23.05, 21.32
[15:46:55] <icinga-miraheze>	 RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 14.86, 17.96, 19.76
[15:51:41] <MH-Discord>	 <Doug> > <avengium> Reception123 , in Gazetteer of wikis, Is ok if i move the place in list of some wikis to follow the alphabetical order? @Avengium (Ángel) Yes, that's fine. You'll need a sysop or translationadmin to remark the page for translation when you've made the change.
[15:53:04] <MH-Discord>	 <Avengium (Ángel)> ok, i will contact someone after that
[15:55:18] <MH-Discord>	 <Doug> > ok, i will contact someone after that @Avengium (Ángel) Okay, sounds good. By the way, DM me on Discord or message me on my talk page if you are familiar enough with the Translate extension, as I think you would likely benefit with the translationadmin tools given your translation activity.
[15:58:34] <MH-Discord>	 <Avengium (Ángel)> saved the edit: https://meta.miraheze.org/wiki/Gazetteer_of_wikis
[15:58:34] <MirahezeBot>	 [ Gazetteer of wikis - Miraheze Meta ] - meta.miraheze.org
[15:59:07] <MH-Discord>	 <Avengium (Ángel)> i need to leave, bye
[16:31:50] <icinga-miraheze>	 PROBLEM - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is WARNING: WARNING - NGINX Error Rate is 43%
[16:35:39] <icinga-miraheze>	 RECOVERY - cp6 HTTP 4xx/5xx ERROR Rate on cp6 is OK: OK - NGINX Error Rate is 28%
[16:40:00] <Spookreeeno>	 paladox: ^
[17:01:27] <Naleksuh>	 yeah there's a lot of these wikis that are just "The (negative attribute) (online website) Wiki"
[17:04:09] <Spookreeeno>	 Naleksuh: the rules are being made more clear and enforced a bit better now
[17:04:46] <Naleksuh>	 The rfc is still open
[17:05:02] <Naleksuh>	 However I think proposal 3 is best (and has the most suppor)
[17:05:14] <Spookreeeno>	 Yeah
[17:05:24] <Spookreeeno>	 Hopefully it'll be closed soon
[17:06:50] <Not>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JUAEj
[17:06:52] <Not>	 [02miraheze/puppet] 07paladox 0302be522 - varnish: Increase rate limit for static to 500/1s The reason is static can handle much more without issues. So 120 over 10s was little especially for static which can handle even more than 500 but I think 500 is a good in between number in the meantime till I get @Southparkfan thoughts.
[17:06:53] <Not>	 [02puppet] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbiAS
[17:06:55] <Not>	 [02puppet] 07paladox opened pull request 03#1505: varnish: Increase rate limit for static to 500/1s - 13https://git.io/JUAue
[17:52:16] <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.
[17:52:21] <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.
[17:52:31] <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.
[17:52:34] <Spookreeeno>	 Weeeeeeee silly puppet
[17:52:35] <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.
[17:52:36] <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.
[17:52:36] <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.
[17:52:37] <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.
[17:52:41] <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.
[17:52:49] <icinga-miraheze>	 PROBLEM - graylog1 Puppet on graylog1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[17:52:56] <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.
[17:52:56] <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.
[17:52:58] <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.
[17:53:03] <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.
[17:53:08] <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.
[17:53:09] <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.
[17:53:10] <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.
[17:53:11] <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.
[17:53: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.
[17:53:27] <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.
[17:53:28] <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.
[17:53:29] <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.
[17:53:31] <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.
[17:53:35] <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.
[17:53:35] <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.
[17:53:40] <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.
[17:53:43] <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.
[17:53:51] <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.
[17:53:59] <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.
[17:54:03] <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.
[17:54:03] <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.
[17:54:03] <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.
[17:54:04] <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.
[17:54:04] <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.
[18:02:41] <paladox>	 what happened
[18:02:49] <Spookreeeno>	 Puppet
[18:03:22] <paladox>	 Oct  6 18:00:18 puppet2 puppet-agent[24211]: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Lookup of key 'lookup_options' failed: Unable to parse (/etc/puppetlabs/puppet/hieradata/private/common.yaml): expected ',' or ']', but got <scalar> while parsing a flow sequence at line 115 column 151 (file: /etc/puppetlabs/puppet/environments/production/modules/base/
[18:03:23] <paladox>	 manifests/init.pp, line: 3, column: 5) on node puppet2.miraheze.org
[18:03:30] <Reception123>	 paladox: my fault yeah
[18:03:33] <Reception123>	 fixed it
[18:03:42] <Reception123>	 That webhook syntax gets me every time :(
[18:03:52] <paladox>	 oh ok
[18:12:16] <icinga-miraheze>	 RECOVERY - ldap1 Puppet on ldap1 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures
[18:12:34] <icinga-miraheze>	 RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures
[18:12:36] <icinga-miraheze>	 RECOVERY - db12 Puppet on db12 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures
[18:12:49] <icinga-miraheze>	 RECOVERY - graylog1 Puppet on graylog1 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures
[18:12:57] <icinga-miraheze>	 RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures
[18:12:57] <icinga-miraheze>	 RECOVERY - db11 Puppet on db11 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures
[18:12:59] <icinga-miraheze>	 RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures
[18:13:03] <icinga-miraheze>	 RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures
[18:13:10] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures
[18:13:13] <icinga-miraheze>	 RECOVERY - gluster2 Puppet on gluster2 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures
[18:13:14] <icinga-miraheze>	 RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:16] <icinga-miraheze>	 RECOVERY - cloud3 Puppet on cloud3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:29] <icinga-miraheze>	 RECOVERY - jobrunner2 Puppet on jobrunner2 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures
[18:13:30] <icinga-miraheze>	 RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:31] <icinga-miraheze>	 RECOVERY - db13 Puppet on db13 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:31] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:32] <icinga-miraheze>	 RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:36] <icinga-miraheze>	 RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:40] <icinga-miraheze>	 RECOVERY - gluster1 Puppet on gluster1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:43] <icinga-miraheze>	 RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:51] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:13:59] <icinga-miraheze>	 RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:03] <icinga-miraheze>	 RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:03] <icinga-miraheze>	 RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:04] <icinga-miraheze>	 RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:04] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures
[18:14:04] <icinga-miraheze>	 RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:21] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:31] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:35] <icinga-miraheze>	 RECOVERY - cp9 Puppet on cp9 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:37] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:14:41] <icinga-miraheze>	 RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[18:15:34] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures
[18:34:10] <MH-Discord>	 <Doug> > saved the edit: https://meta.miraheze.org/wiki/Gazetteer_of_wikis @Avengium (Ángel) ✅ Done
[18:34:11] <MirahezeBot>	 [ Gazetteer of wikis - Miraheze Meta ] - meta.miraheze.org
[18:46:25] <aoam>	 Hi, we have put a request for a new wiki, if somebody could check that?
[18:47:13] <aoam>	 Its for our community mineland
[18:48:16] <MH-Discord>	 <Doug> @aoam I am reviewing requests right now. Give me a few minutes. Thanks.
[18:50:16] <aoam>	 Doug: thanks, we would like to migrate our current wiki, and use our current domain (wiki.mineland.eu) i hope thats all possible
[18:54:10] <Spookreeeno>	 We can do custom domains
[19:05:10] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAiw
[19:05:12] <Not>	 [02miraheze/services] 07MirahezeSSLBot 039d6f533 - BOT: Updating services config for wikis
[19:12:32] <MH-Discord>	 <Doug> > <aoam> @Doug thanks, we would like to migrate our current wiki, and use our current domain (wiki.mineland.eu) i hope thats all possible @aoam Ah, you're that one. I'm doing yours next.
[19:14:18] <MH-Discord>	 <Doug> > @aoam Ah, you're that one. I'm doing yours next. @aoam ✅ Done. Please see [[Custom domains]] for how to request a custom domain on [[Phabricator]].
[19:14:21] <aoam>	 Thanks, collegue has updated description
[19:16:40] <aoam>	 Thanks for approval, im going to study that stuff :) 
[19:26:34] <aoam>	 "Reception123: you would need an XML dump that we can import" is it this one? "Backup the content of the wiki (XML dump" (https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki)
[19:26:34] <MirahezeBot>	 [ Manual:Backing up a wiki - MediaWiki ] - www.mediawiki.org
[19:31:16] <MirahezeBot>	 Hello omair212! If you have any questions, feel free to ask and someone should answer soon.
[19:34:11] <MH-Discord>	 <Avengium (Ángel)> Hi, only making https://athas.miraheze.org/wiki/Special:Log/newusers counts as recent edits for a page, related with the dormancy policy?
[19:34:12] <MirahezeBot>	 [ User creation log - Athas ] - athas.miraheze.org
[19:34:58] <MH-Discord>	 <Avengium (Ángel)> I think that wiki is inactive, because i can't see any activity beside the new user creation
[19:35:11] <Not>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JUAXd
[19:35:12] <Not>	 [02miraheze/services] 07MirahezeSSLBot 0355ded7d - BOT: Updating services config for wikis
[19:41:02] <MH-Discord>	 <Avengium (Ángel)> What do you think about the (in)activity of Athas wiki? @Doug
[19:52:41] <MH-Discord>	 <Avengium (Ángel)> doug is busy, so i will ask someone different. @paladox , what do you think about Athas being inactive and having new user creation logs in recent changes, and that being and edit to the wiki that makes it escape the dormancy policy?
[19:53:33] <MH-Discord>	 <paladox> if the wiki matches the criteria at https://meta.miraheze.org/wiki/Dormancy_Policy
[19:53:34] <MirahezeBot>	 [ Dormancy Policy - Miraheze Meta ] - meta.miraheze.org
[19:53:40] <MH-Discord>	 <paladox> it can be exempted.
[19:55:51] <MH-Discord>	 <Avengium (Ángel)> oh, is exempted, that a plot twist
[19:56:40] <MH-Discord>	 <Avengium (Ángel)> Ok, i will like to adopt it, but i will wait
[19:56:54] <MH-Discord>	 <Avengium (Ángel)> * would like. sorry for the grammar
[19:58:05] <MH-Discord>	 <paladox> i mean it can be
[19:58:11] <MH-Discord>	 <paladox> not that it's exempted.
[20:00:15] <MH-Discord>	 <Avengium (Ángel)> Could we show the "60 days" button as a default for other wikis? It would be easier to check if that button was available for outsiders. But i understand if that decision needs consensus or talk between admins
[20:00:21] <Reception123>	 !log created mail account for noreply-bots (T6186)
[20:00:25] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log
[20:06:25] <MH-Discord>	 <Avengium (Ángel)> i mean, the default of days in other wikis is "30 days", but it can be extended in manage settings checking the "60", "90" and 180 days, buttons in manage settings
[20:06:26] <MH-Discord>	 <Avengium (Ángel)> https://cdn.discordapp.com/attachments/435711390544560128/763130059220844634/Cambios_recientes_01.png
[20:08:09] <omair212>	 Hi, I was just wondering how long it takes to typically get a Wiki approved. I really admire the miraheze nonprofit model and just wanted to learn more as well
[20:08:23] <MH-Discord>	 <RhinosF1> Up to a day probably
[20:08:55] <MH-Discord>	 <RhinosF1> > Could we show the "60 days" button as a default for other wikis? It would be easier to check if that button was available for outsiders. But i understand if that decision needs consensus or talk between admins @Avengium (Ángel): As far as I know, we follow the MediaWiki default
[20:09:56] <MH-Discord>	 <Avengium (Ángel)> Yes. is ok. I was wondering because i can't see if a wiki is near to 45 or not because 45 is beyond that
[20:10:37] <MH-Discord>	 <RhinosF1> We can add 45 days as an option
[20:11:00] <MH-Discord>	 <RhinosF1> And you can change it yourself in settings
[20:12:49] <MH-Discord>	 <Avengium (Ángel)> My idea beyond that is, i see a wiki that looks good, i go to recent changes, it has no edits in the 30 days, and i don't know if that is because is the day 31 or the 44, so i don't know if that will be close to adoption
[20:13:53] <Spookreeeno>	 I mean you could start a discussion on meta to change the default
[20:13:55] <MH-Discord>	 <Avengium (Ángel)> And that happens in wikis i'm not admin, and have no edits, because are wikis i didn't know until i checked and reached that destination
[20:14:25] <MH-Discord>	 <Avengium (Ángel)> I like that idea, where would be the best place?
[20:14:41] <Spookreeeno>	 CN
[20:14:56] <Spookreeeno>	 [[CN]]
[20:15:04] <Spookreeeno>	 .mh CN
[20:15:04] <MirahezeBot>	 https://meta.miraheze.org/wiki/CN
[20:15:09] <MH-Discord>	 <Avengium (Ángel)> thanks
[20:17:22] <MH-Discord>	 <Avengium (Ángel)> Title,  which one do you prefer: "Number of days in recent changes" or "Add 45 days as a new default for recent changes"?
[20:19:43] <omair212>	 Just a prospective question, but is there anyway to embed maps within a Miraheze Wiki?
[20:20:25] <Spookreeeno>	 I believe it's working again
[20:23:07] <MH-Discord>	 <Avengium (Ángel)> Prospective? and that means the titles are ok or not?  What would be an example of a prospective title for this case?
[20:24:31] <Spookreeeno>	 Switch default for recent changes to 45 days
[20:25:06] <MH-Discord>	 <Avengium (Ángel)> that's very similar to mine, but ok
[20:25:08] <MH-Discord>	 <Avengium (Ángel)> thanks
[20:30:05] <MH-Discord>	 <Avengium (Ángel)> is saved here: https://meta.miraheze.org/wiki/Community_noticeboard#Switch_default_for_recent_changes_to_45_days
[20:30:08] <MirahezeBot>	 [ Community noticeboard - Miraheze Meta ] - meta.miraheze.org
[20:30:11] <MH-Discord>	 <Avengium (Ángel)> i have to go, bye
[23:21:00] <hispano76>	 Hii
[23:21:25] <hispano76>	 who is?
[23:53:41] <hispano76>	 I want to make a change in a configuration but it is restricted on managewiki. 
[23:59:03] <dmehus>	 @hispano76 what change do you want to change that is `managewiki-restricted` Depending on what it is, it's either a steward or sysadmin that can do it.
[23:59:46] <hispano76>	 index, follow