[00:04:51] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [00:32:57] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:55:05] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [01:13:09] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:23:09] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 1 minute ago with 9 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666] [01:26:48] RECOVERY - db4 Disk Space on db4 is OK: DISK OK - free space: / 49828 MB (13% inode=96%); [01:27:08] !log ran my purge-binary script on db[45] [01:27:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:27:50] !log delete and recreated puppetdb database on postgresql [01:27:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:30:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JePmA [01:30:11] [02miraheze/services] 07MirahezeSSLBot 0333178e8 - BOT: Updating services config for wikis [01:32:57] PROBLEM - bacula1 Disk Space on bacula1 is CRITICAL: DISK CRITICAL - free space: / 1613 MB (0% inode=99%); [01:32:59] PROBLEM - cp2 Stunnel Http for lizardfs6 on cp2 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8203: HTTP/1.1 200 OK [01:33:26] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 1966 MB (8% inode=94%); [01:33:39] PROBLEM - bacula1 Bacula Static on bacula1 is CRITICAL: CRITICAL: no terminated jobs [01:33:51] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [01:33:53] PROBLEM - cp3 Stunnel Http for lizardfs6 on cp3 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8203: HTTP/1.1 200 OK [02:25:53] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.62, 7.35, 6.86 [02:33:34] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.19, 6.63, 6.80 [03:04:31] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.75, 6.93, 6.71 [03:06:26] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.58, 5.99, 6.37 [03:28:02] Hello CSyde65! If you have any questions, feel free to ask and someone should answer soon. [03:33:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:53:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [04:21:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [04:33:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [04:41:57] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [04:53:58] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [05:21:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:33:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [05:51:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:05:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter] [06:11:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:12:09] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.45, 6.63, 5.99 [06:16:09] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.60, 6.36, 6.17 [06:27:39] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2694 MB (11% inode=94%); [06:32:07] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.74, 7.05, 6.58 [06:33:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [06:36:07] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.43, 6.74, 6.66 [07:03:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:13:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [07:17:42] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2647 MB (10% inode=94%); [07:32:22] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:32:28] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:32:30] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:32:39] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:32:42] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:32:43] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:03] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:08] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:13] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:20] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:29] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:46] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:48] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:54] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:33:57] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:34:10] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:43:08] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [07:43:46] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [07:43:48] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [07:43:54] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [07:43:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [07:43:57] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [07:44:10] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:44:22] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:44:28] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:44:30] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:44:41] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [07:44:43] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:44:44] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [07:45:10] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [07:45:15] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:45:25] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [07:45:29] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [08:03:57] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:13:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [08:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [08:53:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [09:11:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [09:25:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 4 minutes ago with 7 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [10:01:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [10:23:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 4 failures. Last run 2 minutes ago with 4 failures. Failed resources (up to 3 shown): Exec[ufw-allow-udp-from-any-to-any-port-53],Exec[ufw-allow-tcp-from-any-to-any-port-53],Exec[ufw-allow-tcp-from-185.52.1.76-to-any-port-3506],Exec[ops_ensure_members] [10:51:57] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [11:13:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [11:21:59] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [11:32:18] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1 [11:33:57] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 3 datacenters are down: 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:34:51] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw2 [11:36:12] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [11:36:46] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 6 backends are healthy [11:36:49] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [11:54:10] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [12:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [12:53:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 2 minutes ago with 10 failures. Failed resources (up to 3 shown): Package[exim4],Service[postfix],Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22] [12:55:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JePl9 [12:55:08] [02miraheze/services] 07MirahezeSSLBot 03668e69e - BOT: Updating services config for wikis [13:11:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [13:19:38] [02miraheze/mw-config] 07Pix1234 created branch 03T4926 13https://git.io/JeP8O [13:19:40] [02mw-config] 07Pix1234 created branch 03T4926 - 13https://git.io/vbvb3 [13:20:52] miraheze/mw-config/T4926/56e1279 - paladox The build passed. https://travis-ci.org/miraheze/mw-config/builds/616676012 [13:21:54] [02miraheze/mw-config] 07Pix1234 pushed 031 commit to 03T4926 [+0/-0/±1] 13https://git.io/JeP83 [13:21:55] [02miraheze/mw-config] 07Pix1234 038231c64 - add https:// to relative urls in LocalSettings.php [13:23:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [13:27:19] [02mw-config] 07Pix1234 opened pull request 03#2821: add https:// to relative urls in LocalSettings.php - 13https://git.io/JeP8c [13:27:36] [02mw-config] 07Pix1234 closed pull request 03#2821: add https:// to relative urls in LocalSettings.php - 13https://git.io/JeP8c [13:27:37] [02miraheze/mw-config] 07Pix1234 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeP8C [13:27:39] [02miraheze/mw-config] 07Pix1234 03819327c - add https:// to relative urls in LocalSettings.php (#2821) [13:27:43] [02miraheze/mw-config] 07Pix1234 deleted branch 03T4926 [13:27:44] [02mw-config] 07Pix1234 deleted branch 03T4926 - 13https://git.io/vbvb3 [13:31:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [13:43:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [13:51:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:03:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [14:31:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [15:01:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [15:13:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [15:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [15:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [15:59:02] [ANNOUNCEMENT] Please vote on https://meta.miraheze.org/wiki/Requests_for_Comment/Community_Directors [15:59:03] [ Requests for Comment/Community Directors - Miraheze Meta ] - meta.miraheze.org [16:02:48] .status mhmeta On [16:02:52] RhinosF1: Updating User:RhinosF1/Status to On! [16:03:02] RhinosF1: Updated! [16:21:59] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [16:33:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [16:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [16:52:45] .status mhmeta Around-A [16:52:52] RhinosF1: Updating User:RhinosF1/Status to Around-A! [16:53:05] RhinosF1: Updated! [16:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [17:02:05] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [17:13:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Exec[ufw-logging-low] [17:21:59] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [17:34:01] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [17:42:02] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [17:42:40] PROBLEM - browndust.wiki - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'browndust.wiki' expires in 15 day(s) (Wed 11 Dec 2019 05:38:57 PM GMT +0000). [17:42:57] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JePzq [17:42:58] [02miraheze/ssl] 07MirahezeSSLBot 03224c1a2 - Bot: Update SSL cert for browndust.wiki [17:52:38] RECOVERY - browndust.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'browndust.wiki' will expire on Sun 23 Feb 2020 04:42:50 PM GMT +0000. [18:23:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 2 minutes ago with 13 failures. Failed resources (up to 3 shown): Package[openssh-client],Package[openssh-server],Service[ssh],Package[exim4] [18:24:08] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.99, 7.09, 6.67 [18:28:08] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.47, 6.51, 6.56 [18:31:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [18:32:10] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.73, 7.07, 6.83 [18:34:08] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.50, 6.49, 6.67 [18:53:12] * hispano76 greetings [18:54:07] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.74, 7.20, 6.62 [18:56:07] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.79, 6.59, 6.53 [19:11:04] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.56, 7.35, 6.91 [19:20:46] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.39, 6.62, 6.78 [19:23:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 2 minutes ago with 10 failures. Failed resources (up to 3 shown): Package[exim4],Service[postfix],Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22] [19:33:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:43:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 2 minutes ago with 9 failures. Failed resources (up to 3 shown): Service[postfix],Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666] [20:01:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [20:33:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 2 minutes ago with 16 failures. Failed resources (up to 3 shown): Service[ufw],Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client] [20:40:30] <𝐂.𝐒𝐲𝐝𝐞> Stupid question: How do you get into the IRC channel? I forgot. [20:40:42] <𝐂.𝐒𝐲𝐝𝐞> I know I was literally there last night. [20:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [20:42:02] <𝐂.𝐒𝐲𝐝𝐞> Never mind. [20:42:05] <𝐂.𝐒𝐲𝐝𝐞> I think I did it. [20:42:55] Hi CSyde65 [20:44:49] I was hoping someone was on here that knew about the different usergroup permissions. I wanted to ask them a question regarding (suppressrevision). Whether it needed (deleterevision) to use or whether it could be used on its own. I'm asking since I've never had access to (suppressrevision), and all usergroups that have (suppressrevision) also have [20:44:49] (deleterevision), so I wouldn't be able to ask anyone that had (suppressrevision) only. [20:45:19] I'm not sure tbh [20:48:25] Someone with access to both would have to create a test group on a test wiki and then give themselves (suppressrevision) only, and attempt to hide a revision. [20:49:16] We could try [20:49:35] But supressrevision would require a config change rather than ManageWiki [20:49:55] Unless there's some technical documentation or code for it that could tell me. [20:50:00] Ah, okay. [20:50:27] CSyde65: I think supressrevision is what gives the extra flag for oversight [20:50:34] So it's part of core [20:51:03] I know that both (deleterevision) and (suppressrevision) are both built on the same page Special:RevisionDelete. [20:51:46] Supression hides it from admins as well [20:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [20:54:42] True, but the part of (suppressrevision) that I'm aware of is built on the Special:RevisionDelete page. I think it may be built on another page as well, but I'm not sure. [20:55:22] It works on Delete as well [20:56:07] I wonder if it would work if the user didn't have access to any of the delete permissions. [20:56:51] I've never tried [20:58:35] I always wanted to try but I've never had access to (suppressrevision) so I wouldn't be able to check myself. I managed to check certain other permissions with promising results. Like I can access (nuke) without (delete), but I can't use it without (delete) [20:59:20] CSyde65: only staff and stewards will ever get supressrevision [20:59:30] And I don't really want to test it [21:00:03] You wouldn't need to test it. Just being able to access either version of delete would be enough. [21:01:23] I don't know if you would [21:01:24] I also can't use (deletelogentry) without (deleterevision). I can't use (blockemail) without (block). I can't use (editsitecss), (editsitejs), (editsitejson), or (gadgets-edit) unless I have (editinterface) [21:01:42] But in terms of Miraheze you'd never be in that situation [21:01:49] Correct. [21:01:50] Based on that unlikely [21:01:58] Based on what? [21:02:16] What you just said about similar situations [21:03:37] Ah. [21:04:38] I would have tested (bigdelete) as well, but I don't have access to that for some weird reason. [21:04:50] CSyde65: suppressrevision is not really much [21:05:07] bigdelete is just to delete a page with a big history [21:05:13] And even if I did, none of the pages that I'd be able to test it on have a large enough history. [21:05:30] Yeah. So I'm assuming that it would need (delete) to work. [21:05:51] yup [21:06:02] My goal is to write a page for my own personal interest about various user permissions that need a parent permission to function. [21:06:41] CSyde65: see https://meta.miraheze.org/wiki/Requests_for_Comment/CheckUser_and_Oversight [21:06:42] [ Requests for Comment/CheckUser and Oversight - Miraheze Meta ] - meta.miraheze.org [21:09:34] What does that do anyway? [21:10:20] what does what do? [21:15:37] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 3 minutes ago with 3 failures. Failed resources (up to 3 shown): Exec[git_checkout_landing],Exec[ufw-allow-tcp-from-any-to-any-port-80],Exec[ufw-allow-tcp-from-any-to-any-port-443] [21:21:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [21:33:59] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [21:34:19] Examknow Well you pointed me to the CheckUser and Oversight page, but I'm not sure why I'd need it. [21:51:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [22:03:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [22:04:25] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:41:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [22:53:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [23:04:07] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.86, 6.97, 6.07 [23:06:07] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.33, 6.33, 5.99 [23:21:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [23:43:56] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix]