[00:02:50] PROBLEM - dbt1 Puppet on dbt1 is CRITICAL: connect to address 51.77.109.151 port 5666: Connection refusedconnect to host 51.77.109.151 port 5666: Connection refused [00:03:08] PROBLEM - dbt1 Current Load on dbt1 is CRITICAL: connect to address 51.77.109.151 port 5666: Connection refusedconnect to host 51.77.109.151 port 5666: Connection refused [00:03:29] PROBLEM - dbt1 Disk Space on dbt1 is CRITICAL: connect to address 51.77.109.151 port 5666: Connection refusedconnect to host 51.77.109.151 port 5666: Connection refused [00:06:25] PROBLEM - dbt1 Puppet on dbt1 is UNKNOWN: NRPE: Unable to read output [00:06:34] RECOVERY - dbt1 Current Load on dbt1 is OK: OK - load average: 1.03, 0.65, 0.27 [00:06:44] RECOVERY - dbt1 Disk Space on dbt1 is OK: DISK OK - free space: / 94659 MB (97% inode=98%); [00:13:38] RECOVERY - dbt1 Puppet on dbt1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [01:09:04] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 101.04 ms [01:12:35] Hello ziggurat6! If you have any questions, feel free to ask and someone should answer soon. [01:12:44] Hey all, I'm making some dropdown input fields using PageForms, but how do I make 'values from category' show only the pages in said category, and not pages & categories both? Alternatively, is there a way to have the value be something which is in both category A and B, but NOT in category C? [01:36:41] [02mw-config] 07soratako commented on pull request 03#2942: Change copyright license on wikilexicon.miraheze.org per T5318 - 13https://git.io/Jv9Ff [01:59:37] [02mw-config] 07soratako commented on pull request 03#2942: Change copyright license on wikilexicon.miraheze.org per T5318 - 13https://git.io/Jv9FF [02:04:14] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2640 MB (10% inode=93%); [02:06:36] [02WikiDiscover] 07cscott opened pull request 03#10: Use the magic word value cache for magic word handlers - 13https://git.io/Jv9bf [02:11:43] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 3 datacenters are down: 51.77.107.210/cpweb, 2001:41d0:800:1056::2/cpweb, 2607:5300:205:200::17f6/cpweb [02:15:30] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [02:45:21] RECOVERY - ping4 on ns1 is OK: PING OK - Packet loss = 0%, RTA = 99.02 ms [03:19:38] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 101.85 ms [03:43:23] [02WikiDiscover] 07cscott opened pull request 03#11: Use the magic word value cache for magic word handlers - 13https://git.io/Jv9hf [03:43:50] [02WikiDiscover] 07cscott commented on pull request 03#10: Use the magic word value cache for magic word handlers - 13https://git.io/Jv9hk [03:43:51] [02WikiDiscover] 07cscott closed pull request 03#10: Use the magic word value cache for magic word handlers - 13https://git.io/Jv9bf [05:19:55] RECOVERY - ping4 on ns1 is OK: PING OK - Packet loss = 0%, RTA = 98.09 ms [05:32:01] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 102.99 ms [06:19:35] PROBLEM - rdb2 Puppet on rdb2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 7 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [06:22:36] RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:28:25] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3436 MB (14% inode=93%); [07:50:31] PROBLEM - cp3 Current Load on cp3 is WARNING: WARNING - load average: 1.51, 1.72, 1.62 [07:57:36] RECOVERY - cp3 Current Load on cp3 is OK: OK - load average: 1.63, 1.65, 1.63 [08:58:27] PROBLEM - db7 Puppet on db7 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 5 minutes ago with 14 failures. Failed resources (up to 3 shown) [08:58:34] PROBLEM - services2 Puppet on services2 is CRITICAL: CRITICAL: Puppet has 20 failures. Last run 5 minutes ago with 20 failures. Failed resources (up to 3 shown) [08:58:38] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 5 minutes ago with 15 failures. Failed resources (up to 3 shown) [08:58:47] PROBLEM - cp6 Puppet on cp6 is CRITICAL: CRITICAL: Puppet has 445 failures. Last run 5 minutes ago with 445 failures. Failed resources (up to 3 shown) [08:58:48] PROBLEM - mail1 Puppet on mail1 is CRITICAL: CRITICAL: Puppet has 36 failures. Last run 5 minutes ago with 36 failures. Failed resources (up to 3 shown) [08:58:53] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 40 failures. Last run 5 minutes ago with 40 failures. Failed resources (up to 3 shown) [08:58:55] PROBLEM - puppet2 Puppet on puppet2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [08:58:56] PROBLEM - dbt1 Puppet on dbt1 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 5 minutes ago with 13 failures. Failed resources (up to 3 shown) [08:59:03] PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 453 failures. Last run 5 minutes ago with 453 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/usr/local/bin/gen_fingerprints] [08:59:27] PROBLEM - rdb1 Puppet on rdb1 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 6 minutes ago with 16 failures. Failed resources (up to 3 shown) [08:59:44] PROBLEM - cloud2 Puppet on cloud2 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 6 minutes ago with 9 failures. Failed resources (up to 3 shown) [08:59:44] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 6 minutes ago with 11 failures. Failed resources (up to 3 shown) [08:59:45] PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Puppet has 20 failures. Last run 6 minutes ago with 20 failures. Failed resources (up to 3 shown) [08:59:46] PROBLEM - cp8 Puppet on cp8 is CRITICAL: CRITICAL: Puppet has 139 failures. Last run 5 minutes ago with 139 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades] [08:59:51] PROBLEM - cp7 Puppet on cp7 is CRITICAL: CRITICAL: Puppet has 444 failures. Last run 6 minutes ago with 444 failures. Failed resources (up to 3 shown) [08:59:51] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [09:00:14] PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Puppet has 462 failures. Last run 5 minutes ago with 462 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/etc/letsencrypt/cli.ini] [09:00:23] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 243 failures. Last run 6 minutes ago with 243 failures. Failed resources (up to 3 shown): File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix] [09:00:28] PROBLEM - rdb2 Puppet on rdb2 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 7 minutes ago with 15 failures. Failed resources (up to 3 shown) [09:00:33] PROBLEM - phab1 Puppet on phab1 is CRITICAL: CRITICAL: Puppet has 24 failures. Last run 7 minutes ago with 24 failures. Failed resources (up to 3 shown) [09:00:34] PROBLEM - bacula2 Puppet on bacula2 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 7 minutes ago with 13 failures. Failed resources (up to 3 shown) [09:00:38] PROBLEM - db6 Puppet on db6 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 7 minutes ago with 14 failures. Failed resources (up to 3 shown) [09:00:42] PROBLEM - mon1 Puppet on mon1 is CRITICAL: CRITICAL: Puppet has 44 failures. Last run 7 minutes ago with 44 failures. Failed resources (up to 3 shown) [09:01:16] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 8 minutes ago with 11 failures. Failed resources (up to 3 shown) [09:01:22] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [09:01:22] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [09:01:47] PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Puppet has 459 failures. Last run 8 minutes ago with 459 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/usr/local/bin/gen_fingerprints] [09:01:51] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 456 failures. Last run 8 minutes ago with 456 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/usr/local/bin/gen_fingerprints],File[/etc/vim/vimrc.local] [09:02:13] PROBLEM - cloud1 Puppet on cloud1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 8 minutes ago with 1 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/20auto-upgrades] [09:02:38] RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [09:02:44] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [09:02:47] RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [09:02:54] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [09:02:56] RECOVERY - dbt1 Puppet on dbt1 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [09:02:56] RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [09:03:11] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 453 failures. Last run 9 minutes ago with 453 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/usr/local/bin/gen_fingerprints] [09:03:26] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 247 failures. Last run 9 minutes ago with 247 failures. Failed resources (up to 3 shown): File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix] [09:03:32] RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:03:54] RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:03:55] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:03:59] RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:00] RECOVERY - cp8 Puppet on cp8 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [09:04:06] RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:07] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [09:04:18] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [09:04:22] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [09:04:24] RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:29] RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:04:29] RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:34] RECOVERY - db6 Puppet on db6 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:04:34] RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:50] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:04:55] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:05:05] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:05:08] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:05:49] RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:06:02] RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:06:30] RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:06:43] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:06:45] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:06:56] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [09:08:25] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:58:16] PROBLEM - cp3 Current Load on cp3 is WARNING: WARNING - load average: 1.43, 1.74, 1.67 [10:01:58] RECOVERY - cp3 Current Load on cp3 is OK: OK - load average: 1.35, 1.49, 1.58 [10:04:04] RECOVERY - ping4 on ns1 is OK: PING OK - Packet loss = 0%, RTA = 99.85 ms [10:15:48] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 102.82 ms [13:16:52] RECOVERY - ping4 on ns1 is OK: PING OK - Packet loss = 0%, RTA = 99.82 ms [13:28:58] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 102.81 ms [14:27:23] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 128.199.139.216/cpweb, 2607:5300:205:200::17f6/cpweb [14:27:50] PROBLEM - cp3 Stunnel Http for mw4 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [14:31:16] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [14:31:36] RECOVERY - cp3 Stunnel Http for mw4 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.700 second response time [14:41:47] PROBLEM - cp3 Stunnel Http for mw4 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [14:42:43] PROBLEM - cp7 Stunnel Http for mw4 on cp7 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [14:43:16] PROBLEM - cp6 Stunnel Http for mw4 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [14:45:36] RECOVERY - cp3 Stunnel Http for mw4 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.767 second response time [14:45:56] RECOVERY - cp7 Stunnel Http for mw4 on cp7 is OK: HTTP OK: HTTP/1.1 200 OK - 15330 bytes in 0.017 second response time [14:45:58] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 33 failures. Last run 5 minutes ago with 33 failures. Failed resources (up to 3 shown): File[wiki.iufs.cf_private],File[vault.aics.cf],File[vault.aics.cf_private],File[wiki.hrznstudio.com] [14:46:38] RECOVERY - cp6 Stunnel Http for mw4 on cp6 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.348 second response time [14:56:47] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:33:03] PROBLEM - cp7 Stunnel Http for mw4 on cp7 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [15:36:47] RECOVERY - cp7 Stunnel Http for mw4 on cp7 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 5.460 second response time [16:32:00] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvHXn [16:32:01] [02miraheze/mw-config] 07paladox 033e579e3 - Add dbt1 to Database.php [16:41:42] PROBLEM - test2 HTTPS on test2 is CRITICAL: connect to address 51.77.107.211 and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [16:45:58] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 2001:41d0:800:1056::2/cpweb [16:49:20] RECOVERY - test2 HTTPS on test2 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 618 bytes in 0.312 second response time [16:49:33] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [17:34:59] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 2001:41d0:800:1056::2/cpweb [17:38:17] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [17:48:20] * hispano76 greetings [17:51:55] hi [18:03:56] ping Reception123 [18:05:21] hi hispano76 [18:09:30] Reception123 Sorry, I've been checking and I'm still seeing errors in my wikis. I've been wondering if I should just ask for their deletion and in several hours/days I would create those wikis myself hoping that they would be fixed. https://phabricator.miraheze.org/T5340 Because it seems strange to me that those mistakes only happen in these wikis and not in another temporary wiki I made (Hispano76Wiki). [18:09:31] [ ⚓ T5340 Recreate wikis HispanoWiki, UcroniasWiki and PrivadoWiki ] - phabricator.miraheze.org [18:09:52] ^ paladox could you help with the errors? [18:09:57] I'm sorry if I got confused [18:10:03] the wikis will need to be recreated [18:10:12] i've already inserted into the table, and it keeps breaking [18:28:34] ok [18:31:17] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 5 minutes ago with 5 failures. Failed resources (up to 3 shown) [18:33:04] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 7 minutes ago with 2 failures. Failed resources (up to 3 shown) [18:33:19] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 7 minutes ago with 7 failures. Failed resources (up to 3 shown) [18:33:29] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 8 minutes ago with 8 failures. Failed resources (up to 3 shown) [18:34:58] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 35 failures. Last run 7 minutes ago with 35 failures. Failed resources (up to 3 shown): File[wiki.campaign-labour.org],File[wiki.campaign-labour.org_private],File[wiki.bonessdiving.club],File[wiki.bonessdiving.club_private] [18:35:31] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:37:27] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 4 minutes ago with 0 failures [18:37:43] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 4 minutes ago with 0 failures [18:37:52] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 4 minutes ago with 0 failures [18:38:19] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvH9J [18:38:20] [02miraheze/puppet] 07paladox 033e82672 - mediawiki: Increase php childs to 8 [18:39:57] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [18:40:25] !log restart php7.3-fpm on mw* [18:41:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:57:02] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JvHQo [19:57:03] [02miraheze/mw-config] 07paladox 032445282 - Set 1.6k wikis to read only (closed wikis only) [19:57:05] [02mw-config] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbvb3 [19:57:06] [02mw-config] 07paladox opened pull request 03#2949: Set 1.6k wikis to read only (closed wikis only) - 13https://git.io/JvHQK [19:58:55] paladox: is anyone helping ya? [19:59:35] RhinosF1 why? [20:00:57] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JvHQ9 [20:00:58] [02miraheze/mw-config] 07paladox 031e54f36 - Set all closed wikis into read only [20:01:00] [02mw-config] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbvb3 [20:01:01] [02mw-config] 07paladox opened pull request 03#2950: Set all closed wikis into read only - 13https://git.io/JvHQH [20:03:30] [02mw-config] 07paladox closed pull request 03#2950: Set all closed wikis into read only - 13https://git.io/JvHQH [20:03:31] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvHQ5 [20:03:33] [02miraheze/mw-config] 07paladox 03f330630 - Set all closed wikis into read only (#2950) [20:03:34] [02mw-config] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbvb3 [20:03:36] [02miraheze/mw-config] 07paladox deleted branch 03paladox-patch-2 [20:06:03] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JvHQb [20:06:05] [02miraheze/mw-config] 07paladox 036387f0d - Migrate 1.6k wikis to dbt1 [20:06:06] [02mw-config] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbvb3 [20:06:08] [02mw-config] 07paladox opened pull request 03#2951: Migrate 1.6k wikis to dbt1 - 13https://git.io/JvHQN [20:27:45] paladox: in case you want a break or things go wrong [20:28:08] Oh, i won't need a break :) [20:28:45] Don’t wear yourself out [20:36:12] RhinosF1: it's only closed wikis anyway [20:36:17] so that way we don't disrupt anyone [20:36:27] we can take all the time we want too since they're read only anyway [21:02:06] :) [21:05:41] Tru [21:18:08] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ufw-allow-udp-from-any-to-any-port-53] [21:25:14] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [21:39:17] PROBLEM - mw2 Puppet on mw2 is WARNING: WARNING: Puppet last ran 1 hour ago [22:06:10] miraheze/mw-config/paladox-patch-1/2445282 - paladox The build passed. https://travis-ci.org/miraheze/mw-config/builds/667865924 [22:06:50] miraheze/mw-config/paladox-patch-2/1e54f36 - paladox The build has errored. https://travis-ci.org/miraheze/mw-config/builds/667866233 [22:11:14] JohnLewis: around? [22:14:06] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [22:19:28] RhinosF1: what's up? [22:20:20] JohnLewis: Could you disable ReplaceText on meta as it doesn’t work with compress revisions? [22:20:27] sure [22:25:48] thanks [23:00:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvHNr [23:00:11] [02miraheze/services] 07MirahezeSSLBot 038ee2da7 - BOT: Updating services config for wikis [23:10:33] PROBLEM - mw3 Puppet on mw3 is WARNING: WARNING: Puppet last ran 1 hour ago [23:14:06] !log apt-get upgrade puppet-agent - mw3 [23:14:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [23:17:34] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 263 failures. Last run 1 second ago with 263 failures. Failed resources (up to 3 shown) [23:20:34] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [23:24:13] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 37 failures. Last run 5 minutes ago with 37 failures. Failed resources (up to 3 shown): File[vise.dayid.org],File[vise.dayid.org_private],File[runzeppelin.ru],File[runzeppelin.ru_private] [23:27:36] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures