[00:40:07] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvM59
[00:40:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 030538553 - BOT: Updating services config for wikis
[00:43:50] <hispano76>	 It looks great. DataDump :) 
[02:43:39] <icinga-miraheze>	 PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2645 MB (10% inode=93%);
[03:05:07] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvMxv
[03:05:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03635d0d1 - BOT: Updating services config for wikis
[03:30:15] <icinga-miraheze>	 PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 51.161.32.127/cpweb
[03:33:14] <icinga-miraheze>	 PROBLEM - cp3 Stunnel Http for mw5 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[03:36:55] <icinga-miraheze>	 RECOVERY - cp3 Stunnel Http for mw5 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15324 bytes in 0.751 second response time
[03:37:20] <icinga-miraheze>	 RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online
[04:04:49] <icinga-miraheze>	 PROBLEM - cp8 Stunnel Http for mw6 on cp8 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[04:08:28] <icinga-miraheze>	 RECOVERY - cp8 Stunnel Http for mw6 on cp8 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.319 second response time
[06:18:07] <icinga-miraheze>	 PROBLEM - bacula2 Puppet on bacula2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins]
[06:24:40] <Not-a789>	 [02mw-config] 07RhinosF1 commented on pull request 03#2942: Change copyright license on wikilexicon.miraheze.org per T5318 - 13https://git.io/JvMhn
[06:25:06] <icinga-miraheze>	 RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[06:26:16] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3456 MB (14% inode=93%);
[07:05:07] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvMh5
[07:05:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 030d1ad15 - BOT: Updating services config for wikis
[08:01:00] <icinga-miraheze>	 PROBLEM - puppet2 Puppet on puppet2 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 5 minutes ago with 10 failures. Failed resources (up to 3 shown)
[08:02:12] <icinga-miraheze>	 PROBLEM - cp8 Puppet on cp8 is CRITICAL: CRITICAL: Puppet has 41 failures. Last run 7 minutes ago with 41 failures. Failed resources (up to 3 shown)
[08:03:14] <icinga-miraheze>	 PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 36 failures. Last run 6 minutes ago with 36 failures. Failed resources (up to 3 shown): File[m.miraheze.org],File[m.miraheze.org_private],File[www.netazar.org],File[www.netazar.org_private]
[08:04:36] <icinga-miraheze>	 RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[08:05:36] <icinga-miraheze>	 RECOVERY - cp8 Puppet on cp8 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[08:06:19] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures
[12:00:07] <Reception123>	 !log reception@mw1:~$ sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki rottenwebsiteswiki -r "Requested - T5313" /home/reception/delrt.txt
[12:00:20] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[12:25:17] <Not-a789>	 [02mw-config] 07soratako commented on pull request 03#2942: Change copyright license on wikilexicon.miraheze.org per T5318 - 13https://git.io/JvDU5
[12:29:35] <Not-a789>	 [02mw-config] 07RhinosF1 commented on pull request 03#2942: Change copyright license on wikilexicon.miraheze.org per T5318 - 13https://git.io/JvDUF
[12:55:07] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDTu
[12:55:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03c97c88e - BOT: Updating services config for wikis
[13:37:10] <Reception123>	 !log manually ran manageInactiveWikis.php
[13:45:11] <Reception123>	 hm what's up with MirahezeLogbot 
[13:45:14] <Reception123>	 !log manually ran manageInactiveWikis.php
[13:45:23] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[13:52:55] <Rots61>	 Why are al the wiki's of miraheze so slow? I wait for a minute?
[13:54:42] <Rots61>	 If I will save my edit he gives an error.
[13:55:21] <Reception123>	 Rots61: Hi. what error are you getting when you try to save your edit?
[13:55:42] <icinga-miraheze>	 PROBLEM - cp6 Varnish Backends on cp6 is CRITICAL: 1 backends are down. mw5
[13:56:40] <Rots61>	 he say, return save
[13:57:20] <Rots61>	 and if I return he say is again.
[13:59:03] <Reception123>	 Rots61: I apologize that your wikis are slow, I'll take a look but it could be increased traffic 
[13:59:20] <icinga-miraheze>	 RECOVERY - cp6 Varnish Backends on cp6 is OK: All 11 backends are healthy
[14:07:04] <hispano76>	 Hi
[14:07:23] <RhinosF1>	 hi
[14:13:20] <Reception123>	 !log sudo -u www-data php /srv/mediawiki/w/maintenance/importDump.php --wiki sagan4alphawiki /home/reception/sagan4wiki.xml
[14:13:45] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[14:36:27] <Reception123>	 !log reception@mw1:~$ sudo -u www-data php /srv/mediawiki/w/maintenance/rebuildall.php --wiki rottenwebsiteswiki
[14:36:32] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JvDIv
[14:36:33] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis 03f903f35 - replace use of useDB in manageInactiveWikis
[14:36:36] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[14:37:26] <Reception123>	 JohnLewis: thanks!
[14:40:00] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDIT
[14:40:02] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis 03f64e009 - add isset clause for protection
[14:41:33] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JvDIk
[14:41:35] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis 030bb7423 - update CW
[14:41:35] <JohnLewis>	 Reception123: and there you go :)
[14:43:26] <Reception123>	 JohnLewis: time for a manual run and to see if we beat the deletedwikis record
[14:45:31] <Reception123>	 actually it'll run anyway, I'll just leave it do it's thing since anyway they won't be deletable right away
[14:45:56] <JohnLewis>	 Reception123: but we need to know if it works :)
[14:46:13] <JohnLewis>	 as we've just seen, leaving things to happen - issues don't get noticed for months
[14:46:48] <Reception123>	 JohnLewis: fine good point I'll do it at 51 :)
[14:47:16] <paladox>	 Why :51?
[14:47:25] <Reception123>	 paladox: so that puppet runs :D
[14:47:53] <paladox>	 Reception123 you could just do cd /srv/mediawiki/w ; sudo -u www-data git pull ; sudo -u www-data git submodule update
[14:48:07] <Reception123>	 paladox: meh why do that when I can wait 3 mins? :P
[14:48:11] <paladox>	 also there's no gurentee puppet will finish running at :51
[14:48:19] <JohnLewis>	 or run puppet - no need to do manual steps when it's automatic
[14:48:52] <paladox>	 or that ^
[14:55:57] <icinga-miraheze>	 PROBLEM - test2 Puppet on test2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 1 minute ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core]
[14:58:12] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDIC
[14:58:13] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis 03f11d376 - remove usage of selectDB in emailBureaucrats
[14:58:42] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JvDIW
[14:58:43] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis 034ccaa55 - update CW
[15:03:24] <Reception123>	 !log php /srv/mediawiki/w/extensions/CreateWiki/maintenance/manageInactiveWikis.php --wiki loginwiki --write > /var/log/mediawiki/cron/managewikis.log on mw1
[15:03:29] <Reception123>	 JohnLewis: seems to be working now!
[15:03:42] <icinga-miraheze>	 PROBLEM - cp6 Varnish Backends on cp6 is CRITICAL: 1 backends are down. mw5
[15:03:47] <Reception123>	 yup the list is getting populated now 
[15:03:49] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb
[15:03:54] <JohnLewis>	 great
[15:04:29] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[15:05:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDIR
[15:05:10] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03175e2a6 - BOT: Updating services config for wikis
[15:07:51] <icinga-miraheze>	 RECOVERY - cp6 Varnish Backends on cp6 is OK: All 11 backends are healthy
[15:07:52] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[15:10:07] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDIa
[15:10:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03bee9672 - BOT: Updating services config for wikis
[15:13:06] <Reception123>	 !log UPDATE cw_wikis SET wiki_closed = 0 AND wiki_closed_timestamp = NULL WHERE wiki_closed_timestamp > 20200321000000 on db4
[15:13:15] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[15:17:03] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDIH
[15:17:04] <Not-a789>	 [02miraheze/CreateWiki] 07JohnFLewis 03c319e0f - globals are bad (tm)
[15:17:34] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JvDIQ
[15:17:34] <JohnLewis>	 Reception123
[15:17:35] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis 03adccf4a - update CW
[15:17:46] <Reception123>	 JohnLewis: heh let's give it another try 
[15:18:09] <JohnLewis>	 Reception123: I wouldn't pipe to a file
[15:18:23] <JohnLewis>	 You would have seen something was wrong if you hadn't of piped :P
[15:18:55] <Reception123>	 JohnLewis: ah, true will get rid of it, it was left from the original cron
[15:23:16] <Reception123>	 !log php /srv/mediawiki/w/extensions/CreateWiki/maintenance/manageInactiveWikis.php --wiki loginwiki on mw1
[15:24:22] <Reception123>	 an awful lot of wikis getting warned/closed but don't see anything unusual
[15:24:36] <JohnLewis>	 are there actual timestamps?
[15:25:52] <Reception123>	 JohnLewis: there are, and there's also stuff like this
[15:25:53] <Reception123>	 chestwiki should be closed. Timestamp of last recent changes entry: 0
[15:26:00] <Reception123>	 does that not just mean that there's never been edits?
[15:26:22] <icinga-miraheze>	 PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 51.161.32.127/cpweb
[15:29:04] <icinga-miraheze>	 PROBLEM - cp6 Stunnel Http for mw5 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[15:30:29] <icinga-miraheze>	 RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online
[15:33:05] <JohnLewis>	 It means there’s no RC entries
[15:33:05] <icinga-miraheze>	 RECOVERY - cp6 Stunnel Http for mw5 on cp6 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.007 second response time
[15:36:52] <Reception123>	 JohnLewis: ok, then it's working as intended
[15:37:02] <Reception123>	 the other wikis have normal timestamps
[15:57:34] <Reception123>	 !log renamed magnaversewiki to cnocbridewiki (db+cw)
[15:57:46] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[16:00:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDLa
[16:00:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03c3b93ad - BOT: Updating services config for wikis
[16:01:02] <Reception123>	 !log sudo -u www-data php /srv/mediawiki/w/maintenance/dumpBackup.php --wiki aerosswiki --full > /home/reception/aerosswiki21032020.xml
[16:01:12] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[16:09:22] <Reception123>	 !log sudo -u www-data php /srv/mediawiki/w/maintenance/deleteBatch.php --wiki rottenwebsiteswiki -r "Requested - T5313" /home/reception/delrt1.txt on mw1
[16:09:30] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[18:40:59] <icinga-miraheze>	 PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 2 datacenters are down: 2001:41d0:800:1056::2/cpweb, 51.161.32.127/cpweb
[18:44:35] <icinga-miraheze>	 RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online
[19:05:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDYc
[19:05:10] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03d22cb36 - BOT: Updating services config for wikis
[19:32:00] <hispano76>	 Could you get that? I'd like to start reorganizing my projects.  Sorry for the inconvenience.  https://phabricator.miraheze.org/T5340 
[19:32:00] <ZppixBot>	 [ ⚓ T5340 Recreate wikis HispanoWiki, UcroniasWiki and PrivadoWiki ] - phabricator.miraheze.org
[19:50:47] <RhinosF1>	 hispano76: being worked on
[19:51:51] <paladox>	 !log delete hispanowiki
[19:51:59] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[19:52:01] <paladox>	 hispano76 you'll need to request the wikis on meta again though
[19:52:40] <paladox>	 !log delete ucroniaswiki
[19:52:49] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[19:53:17] <RhinosF1>	 paladox: Special:CreateWiki
[19:53:27] <paladox>	 Thats for me
[19:53:54] <RhinosF1>	 paladox: why not just create through that rather than request then recreate that way?
[19:53:56] <paladox>	 I'm meaning him to request it as i doin't know what the sitename is and lang he wants
[19:54:24] <RhinosF1>	 hispano76: Are all the sitenames and languages the same as last time?
[19:54:30] <paladox>	 and also leaves a trail to show the wikis does not belong to me
[19:54:36] <paladox>	 and so it makes him the admin and not me
[19:54:50] <RhinosF1>	 Requestor field and phab task as the reason
[19:55:22] <hispano76>	 ah
[19:56:34] <JohnLewis>	 paladox: to make someone else the admin you don't put your own name in the relevant field :)
[19:56:47] <paladox>	 ok
[19:56:56] <paladox>	 JohnLewis WikiManager seems broken, its not deleting things.
[19:57:04] <RhinosF1>	 JohnLewis: I’ll sort it if needed
[19:57:16] <JohnLewis>	 paladox: what are you running?
[19:57:27] <paladox>	 I did this:
[19:57:27] <paladox>	 root@mw1:/home/paladox# php /srv/mediawiki/w/maintenance/eval.php --wiki=loginwiki
[19:57:29] <paladox>	 then:
[19:57:34] <paladox>	 $wm = new WikiManager( 'hispanowiki' ); $wm->delete( true );
[19:57:48] <paladox>	 yet i can still access https://hispano.miraheze.org/wiki/Hispano:Portada
[19:57:49] <ZppixBot>	 [ Hispano ] - hispano.miraheze.org
[19:58:14] <JohnLewis>	 paladox: because you haven't marked the wiki for deletion
[19:58:20] <paladox>	 ohhhh
[19:58:24] * paladox facepalms
[20:00:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDOv
[20:00:10] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03172fdde - BOT: Updating services config for wikis
[20:01:58] <Not-a789>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDOJ
[20:01:59] <Not-a789>	 [02miraheze/mw-config] 07paladox 03cb562be - Update Database.php
[20:04:29] <RhinosF1>	 paladox: are you recreating with exact same info? https://meta.miraheze.org/wiki/Special:RequestWikiQueue?dbname=&requester=Hispano76&status=*
[20:04:30] <ZppixBot>	 [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org
[20:10:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDOt
[20:10:10] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 03524d4fe - BOT: Updating services config for wikis
[20:13:14] <Not-a789>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDO3
[20:13:15] <Not-a789>	 [02miraheze/mw-config] 07paladox 03929a9ae - Revert "Update Database.php" This reverts commit cb562bea5dda242629c9519c593b84a65e62bdef.
[20:14:16] <paladox>	 hispano76 done
[20:15:47] <RhinosF1>	 Thanks paladox
[20:16:00] <hispano76>	 Thanks paladox  
[20:16:06] <hispano76>	 :)
[20:35:51] <hispano76>	 to be sure, ExternalLinkTarget  "_blank" does the same as enwikipedia Gadget-exlinks.js? 
[20:45:09] <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.
[20:45:16] <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.
[20:45:24] <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.
[20:45:25] <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.
[20:45:30] <icinga-miraheze>	 PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:45:32] <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.
[20:45:32] <icinga-miraheze>	 PROBLEM - cp8 Puppet on cp8 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:45:39] <RhinosF1>	 weeee, puppet spam
[20:45:59] <icinga-miraheze>	 PROBLEM - puppet2 Puppet on puppet2 is CRITICAL: CRITICAL: Puppet has 17 failures. Last run 5 minutes ago with 17 failures. Failed resources (up to 3 shown)
[20:46:02] <icinga-miraheze>	 PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:46:02] <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.
[20:46:20] <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.
[20:46:33] <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.
[20:46:42] <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.
[20:46:42] <icinga-miraheze>	 PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:46:42] <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.
[20:46:43] <icinga-miraheze>	 PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:46:43] <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.
[20:46:51] <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.
[20:46:51] <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.
[20:47:11] <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.
[20:47:21] <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.
[20:47:38] <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.
[20:47:55] <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.
[20:47:55] <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.
[20:47:55] <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.
[20:47:55] <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.
[20:47:56] <icinga-miraheze>	 PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[20:47:59] <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.
[20:48:17] <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.
[20:52:47] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures
[20:53:23] <icinga-miraheze>	 RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures
[20:53:25] <icinga-miraheze>	 RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures
[20:53:31] <icinga-miraheze>	 RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures
[20:53:35] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures
[20:53:36] <icinga-miraheze>	 RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures
[20:53:39] <icinga-miraheze>	 RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures
[20:54:00] <icinga-miraheze>	 RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:54:17] <icinga-miraheze>	 RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:54:42] <icinga-miraheze>	 RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:54:42] <icinga-miraheze>	 RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:54:42] <icinga-miraheze>	 RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:54:44] <icinga-miraheze>	 RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:54:48] <icinga-miraheze>	 RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:54:50] <icinga-miraheze>	 RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:02] <icinga-miraheze>	 RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:55:04] <icinga-miraheze>	 RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:04] <icinga-miraheze>	 RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:05] <icinga-miraheze>	 RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:55:05] <icinga-miraheze>	 RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:19] <icinga-miraheze>	 RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:55:20] <icinga-miraheze>	 RECOVERY - cp8 Puppet on cp8 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:22] <icinga-miraheze>	 RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:55:48] <icinga-miraheze>	 RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures
[20:55:48] <icinga-miraheze>	 RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures
[20:55:48] <icinga-miraheze>	 RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures
[20:56:26] <icinga-miraheze>	 RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[20:56:40] <icinga-miraheze>	 RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures
[20:57:59] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[21:08:06] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 1 datacenter is down: 2400:6180:0:d0::403:f001/cpweb
[21:10:08] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvDOH
[21:10:09] <Not-a789>	 [02miraheze/services] 07MirahezeSSLBot 034b393c8 - BOT: Updating services config for wikis
[21:11:52] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[21:54:31] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 1 datacenter is down: 2607:5300:205:200::17f6/cpweb
[21:58:00] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[22:12:19] <Not-a789>	 [02miraheze/IncidentReporting] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±5] 13https://git.io/JvDsm
[22:12:20] <Not-a789>	 [02miraheze/IncidentReporting] 07JohnFLewis 03ead301e - release 1.1.2 including fixes and configregistry
[22:12:57] <JohnLewis>	 paladox: ^ how does that look?
[22:13:05] * paladox looks
[22:16:11] <paladox>	 JohnLewis looking at that (unrelated to your change), default value for IncidentReportingServices should be [], IncidentReportingDatabase should be an empty string and same for IncidentReportingTaskUrl. Other then that it looks perfect to my eyes.
[22:17:07] <JohnLewis>	 those are essentially the same as false
[22:17:20] <paladox>	 oh?
[22:17:22] <paladox>	 ok
[22:17:42] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JvDsC
[22:17:44] <Not-a789>	 [02miraheze/mediawiki] 07JohnFLewis 032275d55 - update IR
[22:59:15] <icinga-miraheze>	 PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins]
[23:03:19] <icinga-miraheze>	 RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures