[00:35:53] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JeAzs [00:35:54] [02miraheze/MirahezeMagic] 07paladox 039c23b14 - Add "Recent Changes" i18n [00:35:56] [02MirahezeMagic] 07paladox created branch 03paladox-patch-2 - 13https://git.io/fQRGX [00:35:57] [02MirahezeMagic] 07paladox opened pull request 03#93: Add "Recent Changes" i18n - 13https://git.io/JeAzG [00:38:44] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeAzn [00:38:46] [02miraheze/mw-config] 07paladox 03ac2ca03 - Move "Recent Changes" configs to it's own section [00:38:47] [02mw-config] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbvb3 [00:38:49] [02mw-config] 07paladox opened pull request 03#2843: Move "Recent Changes" configs to it's own section - 13https://git.io/JeAzc [00:39:05] [02MirahezeMagic] 07paladox closed pull request 03#93: Add "Recent Changes" i18n - 13https://git.io/JeAzG [00:39:06] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeAzC [00:39:08] [02miraheze/MirahezeMagic] 07paladox 03e9b8fd7 - Add "Recent Changes" i18n (#93) [00:40:05] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JeAzW [00:40:06] [02miraheze/mediawiki] 07paladox 037d6b4fe - Update MirahezeMagic [00:40:19] [02mw-config] 07paladox edited pull request 03#2843: Move "Recent Changes" configs to it's own section - 13https://git.io/JeAzc [00:41:15] [02mw-config] 07paladox closed pull request 03#2843: Move "Recent Changes" configs to it's own section - 13https://git.io/JeAzc [00:41:17] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeAzB [00:41:18] [02miraheze/mw-config] 07paladox 0363c0121 - Move "Recent Changes" configs to it's own section (#2843) [00:41:19] [02miraheze/mw-config] 07paladox deleted branch 03paladox-patch-1 [00:41:21] [02mw-config] 07paladox deleted branch 03paladox-patch-1 - 13https://git.io/vbvb3 [00:42:54] !log rebuild lc on mw* and lizardfs6 [00:44:02] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:46:23] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 2604:180:0:33b::2/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:47:52] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:52:03] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 4 datacenters are down: 107.191.126.23/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:54:03] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:54:33] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [00:55:05] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:58:20] !log root@misc2:/srv/redis# rm appendonly.aof [00:58:28] !log root@misc2:/srv/redis# rm dump.rdb [00:58:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [00:58:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:00:20] !log test [01:00:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:01:17] !log restart logbot on misc1 [01:01:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:01:35] !log test [01:01:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:03:22] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [01:08:48] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb [01:10:43] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [03:03:50] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown) [03:03:51] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown) [03:03:59] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown) [03:04:06] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 2 minutes ago with 3 failures. Failed resources (up to 3 shown) [03:04:12] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 48 failures. Last run 2 minutes ago with 48 failures. Failed resources (up to 3 shown) [03:04:37] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [03:04:39] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown) [03:04:44] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [03:04:48] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 422 failures. Last run 3 minutes ago with 422 failures. Failed resources (up to 3 shown) [03:04:52] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 232 failures. Last run 2 minutes ago with 232 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] [03:05:04] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown) [03:05:09] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 427 failures. Last run 3 minutes ago with 427 failures. Failed resources (up to 3 shown) [03:05:34] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 421 failures. Last run 3 minutes ago with 421 failures. Failed resources (up to 3 shown): File[/usr/lib/php/20180731/tideways_xhprof.so],File[/etc/systemd/system/jobrunner.service],File[/etc/systemd/system/jobchron.service],File[/etc/rsyslog.d/20-jobrunner.conf] [03:05:35] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 416 failures. Last run 3 minutes ago with 416 failures. Failed resources (up to 3 shown) [03:06:06] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 421 failures. Last run 3 minutes ago with 421 failures. Failed resources (up to 3 shown): File[wildcard.miraheze.org_private],File[/opt/ploticus_2.42-3+b4_amd64.deb],File[/opt/texvc_3.0.0+git20160613-1_amd64.deb],File[/etc/mathoid/config.yaml] [03:06:25] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 122 failures. Last run 2 minutes ago with 122 failures. Failed resources (up to 3 shown): File[wildcard.miraheze.org_private],File[/etc/default/stunnel4],File[/etc/stunnel/mediawiki.conf],File[/usr/lib/nagios/plugins/check_varnishbackends] [03:06:48] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 3 minutes ago with 16 failures. Failed resources (up to 3 shown): File[/etc/stunnel/mediawiki.conf],File[/usr/lib/nagios/plugins/check_varnishbackends],File[/usr/lib/nagios/plugins/check_nginx_errorrate],File[/etc/logrotate.d/salt-common] [03:12:37] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [03:12:40] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [03:12:50] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [03:13:03] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [03:13:25] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [03:13:32] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [03:13:45] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:13:46] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:13:49] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:14:03] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:14:21] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [03:14:23] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:14:44] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [03:14:52] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:15:22] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:15:29] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:16:21] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:30:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA2i [03:30:09] [02miraheze/services] 07MirahezeSSLBot 03508464c - BOT: Updating services config for wikis [05:13:40] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown) [05:14:22] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 47 failures. Last run 2 minutes ago with 47 failures. Failed resources (up to 3 shown) [05:14:48] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown) [05:14:52] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [05:14:53] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [05:15:00] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [05:15:08] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 427 failures. Last run 3 minutes ago with 427 failures. Failed resources (up to 3 shown) [05:15:09] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 3 minutes ago with 6 failures. Failed resources (up to 3 shown) [05:15:16] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 422 failures. Last run 3 minutes ago with 422 failures. Failed resources (up to 3 shown) [05:15:28] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown) [05:15:45] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 424 failures. Last run 3 minutes ago with 424 failures. Failed resources (up to 3 shown): File[/etc/mathoid/config.yaml],File[/etc/apt/trusted.gpg.d/php.gpg],File[/usr/lib/php/20180731/luasandbox.so],File[/usr/lib/php/20170718/luasandbox.so] [05:15:47] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 422 failures. Last run 3 minutes ago with 422 failures. Failed resources (up to 3 shown) [05:15:48] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 412 failures. Last run 4 minutes ago with 412 failures. Failed resources (up to 3 shown) [05:15:54] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 4 minutes ago with 9 failures. Failed resources (up to 3 shown) [05:15:56] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 431 failures. Last run 3 minutes ago with 431 failures. Failed resources (up to 3 shown): File[/usr/local/bin/gen_fingerprints],File[/etc/vim/vimrc.local],File[/usr/share/nginx/favicons/default.ico],File[/usr/share/nginx/favicons/apple-touch-icon-default.png] [05:16:23] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 137 failures. Last run 2 minutes ago with 137 failures. Failed resources (up to 3 shown): File[/etc/default/stunnel4],File[/etc/stunnel/mediawiki.conf],File[/usr/lib/nagios/plugins/check_varnishbackends],File[/usr/lib/nagios/plugins/check_nginx_errorrate] [05:16:47] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 208 failures. Last run 3 minutes ago with 208 failures. Failed resources (up to 3 shown): File[/usr/lib/nagios/plugins/check_nginx_errorrate],File[/etc/logrotate.d/salt-common],File[/etc/logrotate.d/puppet],File[/etc/update-motd.d/97-last-puppet-run] [05:22:42] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [05:22:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:23:05] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:23:28] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [05:23:36] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [05:23:39] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [05:23:41] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:23:52] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:23:53] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:24:17] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [05:24:35] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:24:39] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:24:42] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [05:24:44] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:25:18] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:25:26] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:26:22] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:24:38] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 43 failures. Last run 2 minutes ago with 43 failures. Failed resources (up to 3 shown) [06:24:44] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 2 minutes ago with 9 failures. Failed resources (up to 3 shown) [06:24:44] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown) [06:24:45] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 2 minutes ago with 5 failures. Failed resources (up to 3 shown) [06:25:00] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown) [06:25:08] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 4 failures. Last run 3 minutes ago with 4 failures. Failed resources (up to 3 shown) [06:25:31] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 418 failures. Last run 3 minutes ago with 418 failures. Failed resources (up to 3 shown) [06:25:34] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 423 failures. Last run 3 minutes ago with 423 failures. Failed resources (up to 3 shown) [06:25:44] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 420 failures. Last run 3 minutes ago with 420 failures. Failed resources (up to 3 shown): File[/usr/lib/php/20180731/tideways_xhprof.so],File[/etc/ImageMagick-6/policy.xml],File[/srv/mediawiki/robots.php],File[/usr/local/bin/fileLockScript.sh] [06:25:48] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 420 failures. Last run 3 minutes ago with 420 failures. Failed resources (up to 3 shown) [06:25:49] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 4 minutes ago with 6 failures. Failed resources (up to 3 shown) [06:25:50] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 407 failures. Last run 3 minutes ago with 407 failures. Failed resources (up to 3 shown) [06:25:51] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 4 minutes ago with 7 failures. Failed resources (up to 3 shown) [06:25:52] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 4 minutes ago with 5 failures. Failed resources (up to 3 shown) [06:26:02] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3249 MB (13% inode=94%); [06:26:07] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [06:26:21] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 134 failures. Last run 2 minutes ago with 134 failures. Failed resources (up to 3 shown): File[/usr/lib/nagios/plugins/check_nginx_errorrate],File[/etc/logrotate.d/salt-common],File[/etc/logrotate.d/puppet],File[/etc/update-motd.d/97-last-puppet-run] [06:26:44] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 204 failures. Last run 3 minutes ago with 204 failures. Failed resources (up to 3 shown): File[/etc/update-motd.d/97-last-puppet-run],File[/etc/sudoers],File[/home/nagiosre],File[/etc/nginx/mime.types] [06:32:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [06:33:03] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [06:33:47] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:33:48] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:33:48] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:33:51] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:33:58] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:34:00] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:34:01] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:34:26] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:34:33] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:34:36] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:34:36] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:34:37] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:34:37] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:35:28] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:36:14] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:47:49] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeAo1 [06:47:50] [02miraheze/ManageWiki] 07translatewiki 0320e3b1e - Localisation updates from https://translatewiki.net. [06:47:51] [ Main page - translatewiki.net ] - translatewiki.net. [06:47:52] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/JeAoM [06:47:54] [02miraheze/MirahezeMagic] 07translatewiki 032926a40 - Localisation updates from https://translatewiki.net. [06:47:55] [ Main page - translatewiki.net ] - translatewiki.net. [08:53:48] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 2 minutes ago with 5 failures. Failed resources (up to 3 shown) [08:54:42] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 40 failures. Last run 2 minutes ago with 40 failures. Failed resources (up to 3 shown) [08:54:48] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [08:54:50] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 3 minutes ago with 11 failures. Failed resources (up to 3 shown) [08:54:51] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 4 failures. Last run 3 minutes ago with 4 failures. Failed resources (up to 3 shown) [08:54:52] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 3 minutes ago with 3 failures. Failed resources (up to 3 shown) [08:54:52] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 3 minutes ago with 5 failures. Failed resources (up to 3 shown) [08:54:52] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 3 minutes ago with 6 failures. Failed resources (up to 3 shown) [08:54:59] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 3 minutes ago with 9 failures. Failed resources (up to 3 shown) [08:55:28] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 419 failures. Last run 3 minutes ago with 419 failures. Failed resources (up to 3 shown) [08:55:32] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 418 failures. Last run 3 minutes ago with 418 failures. Failed resources (up to 3 shown) [08:55:42] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 419 failures. Last run 3 minutes ago with 419 failures. Failed resources (up to 3 shown): File[/usr/lib/php/20180731/tideways_xhprof.so],File[/etc/ImageMagick-6/policy.xml],File[/srv/mediawiki/robots.php],File[/usr/local/bin/fileLockScript.sh] [08:55:45] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 416 failures. Last run 3 minutes ago with 416 failures. Failed resources (up to 3 shown) [08:55:55] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 417 failures. Last run 3 minutes ago with 417 failures. Failed resources (up to 3 shown): File[/usr/lib/php/20180731/tideways_xhprof.so],File[/etc/ImageMagick-6/policy.xml],File[/srv/mediawiki/robots.php],File[/usr/local/bin/fileLockScript.sh] [08:55:56] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 408 failures. Last run 4 minutes ago with 408 failures. Failed resources (up to 3 shown) [08:56:17] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 125 failures. Last run 2 minutes ago with 125 failures. Failed resources (up to 3 shown): File[/usr/lib/nagios/plugins/check_nginx_errorrate],File[/etc/logrotate.d/salt-common],File[/etc/logrotate.d/puppet],File[/etc/update-motd.d/97-last-puppet-run] [08:56:33] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 199 failures. Last run 3 minutes ago with 199 failures. Failed resources (up to 3 shown): File[/etc/sudoers],File[/home/nagiosre],File[/etc/nginx/mime.types],File[/etc/nginx/fastcgi_params] [09:02:47] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [09:02:55] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [09:02:56] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [09:02:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [09:03:33] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [09:03:38] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [09:03:40] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [09:03:49] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [09:03:53] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:18] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [09:04:32] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [09:04:37] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:38] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:39] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:04:39] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:06:01] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:06:16] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:13:01] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:06] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:20] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 2 minutes ago with 16 failures. Failed resources (up to 3 shown) [10:13:21] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:27] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:35] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 440 failures. Last run 2 minutes ago with 440 failures. Failed resources (up to 3 shown) [10:13:35] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:39] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:13:45] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 2 minutes ago with 14 failures. Failed resources (up to 3 shown) [10:14:12] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 51 failures. Last run 3 minutes ago with 51 failures. Failed resources (up to 3 shown) [10:14:17] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:14:37] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [10:14:38] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 29 failures. Last run 3 minutes ago with 29 failures. Failed resources (up to 3 shown) [10:14:39] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 194 failures. Last run 3 minutes ago with 194 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.d],File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades] [10:14:39] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [10:14:44] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 3 minutes ago with 13 failures. Failed resources (up to 3 shown) [10:15:35] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 246 failures. Last run 4 minutes ago with 246 failures. Failed resources (up to 3 shown) [10:22:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [10:23:03] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [10:23:20] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [10:23:36] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [10:23:48] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [10:23:48] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:24:08] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:24:32] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [10:24:34] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:24:36] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:24:37] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:24:41] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:25:15] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:25:22] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:25:28] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:25:44] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:26:15] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:48:58] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 2.03, 2.30, 1.64 [10:50:57] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.18, 1.14, 1.32 [10:55:00] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 5.52, 3.16, 2.27 [10:58:57] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.87, 1.71, 1.94 [11:00:56] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.75, 1.19, 1.68 [11:43:23] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [11:43:31] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 49 failures. Last run 2 minutes ago with 49 failures. Failed resources (up to 3 shown) [11:43:34] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [11:43:40] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 2 minutes ago with 13 failures. Failed resources (up to 3 shown) [11:44:18] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 122 failures. Last run 2 minutes ago with 122 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.d],File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades] [11:44:33] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 190 failures. Last run 2 minutes ago with 190 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] [11:44:35] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 27 failures. Last run 3 minutes ago with 27 failures. Failed resources (up to 3 shown) [11:44:36] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [11:44:37] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 3 minutes ago with 14 failures. Failed resources (up to 3 shown) [11:44:41] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown) [11:44:53] paladox: ^ [11:44:59] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 22 failures. Last run 3 minutes ago with 22 failures. Failed resources (up to 3 shown) [11:45:00] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 29 failures. Last run 3 minutes ago with 29 failures. Failed resources (up to 3 shown) [11:45:14] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 239 failures. Last run 3 minutes ago with 239 failures. Failed resources (up to 3 shown) [11:45:25] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 4 minutes ago with 15 failures. Failed resources (up to 3 shown) [11:45:26] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 245 failures. Last run 3 minutes ago with 245 failures. Failed resources (up to 3 shown) [11:45:31] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 438 failures. Last run 3 minutes ago with 438 failures. Failed resources (up to 3 shown) [11:45:35] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 239 failures. Last run 3 minutes ago with 239 failures. Failed resources (up to 3 shown) [11:52:37] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [11:52:41] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [11:53:02] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [11:53:03] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [11:53:18] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [11:53:25] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [11:53:29] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [11:53:33] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [11:53:36] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [11:53:43] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [11:53:44] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [11:53:47] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [11:54:32] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [11:54:34] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [11:54:36] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [11:55:22] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [11:56:15] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:43:34] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 3.80, 3.02, 1.88 [13:02:58] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:14] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:21] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:22] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:22] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:32] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 242 failures. Last run 2 minutes ago with 242 failures. Failed resources (up to 3 shown) [13:03:40] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 51 failures. Last run 2 minutes ago with 51 failures. Failed resources (up to 3 shown) [13:03:41] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:03:42] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown) [13:03:46] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 1.02, 1.35, 1.93 [13:04:07] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 17 failures. Last run 3 minutes ago with 17 failures. Failed resources (up to 3 shown) [13:04:18] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:35] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:37] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 29 failures. Last run 3 minutes ago with 29 failures. Failed resources (up to 3 shown) [13:04:37] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:37] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:04:39] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [13:04:41] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [13:05:45] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 6.43, 2.89, 2.31 [13:11:48] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.58, 1.53, 1.96 [13:12:41] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [13:12:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [13:13:11] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [13:13:35] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [13:13:40] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:13:48] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 2.53, 2.21, 2.13 [13:14:07] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:14:31] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [13:14:32] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [13:14:34] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:14:38] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:14:39] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [13:15:15] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:15:22] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:15:23] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:15:25] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:15:33] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:16:16] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:19:47] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.45, 1.15, 1.75 [13:21:45] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.90, 0.96, 1.54 [13:37:14] !log reboot puppet1 [13:37:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:39:11] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JeADK [14:39:12] [02miraheze/mediawiki] 07paladox 03acb34b4 - Update LinkTitles [15:14:46] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1 [15:16:30] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw3 [15:16:53] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [15:18:27] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 6 backends are healthy [15:43:11] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 2.32, 2.77, 1.93 [15:43:48] Hi hispano76 [15:45:11] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.79, 1.70, 1.68 [15:45:20] hi RhinosF1 :) [15:45:47] hispano76: doing much for NYE? [15:48:41] NYE? [15:48:47] RhinosF1: hi [15:48:50] hispano76: New Year's Eve [15:48:50] hispano76: hi [15:49:02] RhinosF1: doing a Phabricator cleanup so we start 2020 with a smaller backlog :) [15:50:31] RhinosF1: Not really. XD [15:50:35] hi Reception123 [15:54:41] I mean, not really much.* [15:56:03] Reception123: i saw [16:15:08] RhinosF1: https://phabricator.miraheze.org/T5014#95437 would you mind doing a PR? [16:15:10] [ ⚓ T5014 "'navbarIcon' => true," on Foreground Skin ] - phabricator.miraheze.org [16:17:04] Reception123: mobile and planning on enjoying the start of the new year [16:17:49] RhinosF1: ok [16:18:27] If I haven’t forgot by later in the week Reception123, yes [16:18:34] But i have poor memory [16:23:50] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 2 minutes ago with 3 failures. Failed resources (up to 3 shown) [16:24:44] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 3 minutes ago with 11 failures. Failed resources (up to 3 shown) [16:24:44] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [16:24:46] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [16:24:51] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown) [16:24:52] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 3 minutes ago with 5 failures. Failed resources (up to 3 shown) [16:25:00] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 17 failures. Last run 3 minutes ago with 17 failures. Failed resources (up to 3 shown) [16:25:08] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03Reception123-patch-2 [+1/-0/±0] 13https://git.io/JeA9t [16:25:09] [02miraheze/ssl] 07Reception123 0355e259f - add wiki.mnzp.xyz cert [16:25:10] [02ssl] 07Reception123 created branch 03Reception123-patch-2 - 13https://git.io/vxP9L [16:25:12] [02ssl] 07Reception123 opened pull request 03#251: add wiki.mnzp.xyz cert - 13https://git.io/JeA9q [16:25:13] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 428 failures. Last run 3 minutes ago with 428 failures. Failed resources (up to 3 shown) [16:25:14] paladox: ^ [16:25:20] Puppet gone mad? [16:25:21] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 3 minutes ago with 9 failures. Failed resources (up to 3 shown) [16:25:27] puppet-server seems to be OOM'g [16:25:29] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 423 failures. Last run 3 minutes ago with 423 failures. Failed resources (up to 3 shown) [16:25:41] paladox: :( [16:25:42] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 424 failures. Last run 3 minutes ago with 424 failures. Failed resources (up to 3 shown) [16:25:44] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 423 failures. Last run 3 minutes ago with 423 failures. Failed resources (up to 3 shown): File[/etc/mathoid/config.yaml],File[/etc/apt/trusted.gpg.d/php.gpg],File[/usr/lib/php/20180731/luasandbox.so],File[/usr/lib/php/20170718/luasandbox.so] [16:25:45] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 48 failures. Last run 4 minutes ago with 48 failures. Failed resources (up to 3 shown) [16:25:47] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 413 failures. Last run 4 minutes ago with 413 failures. Failed resources (up to 3 shown) [16:25:56] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03Reception123-patch-2 [+0/-0/±1] 13https://git.io/JeA9O [16:25:57] [02miraheze/ssl] 07Reception123 03127dbe7 - Update certs.yaml [16:25:58] Can you reboot it or clear the memory? [16:25:59] [02ssl] 07Reception123 synchronize pull request 03#251: add wiki.mnzp.xyz cert - 13https://git.io/JeA9q [16:25:59] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 426 failures. Last run 3 minutes ago with 426 failures. Failed resources (up to 3 shown): File[/usr/local/bin/gen_fingerprints],File[/etc/vim/vimrc.local],File[/usr/share/nginx/favicons/default.ico],File[/usr/share/nginx/favicons/apple-touch-icon-default.png] [16:26:21] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 129 failures. Last run 2 minutes ago with 129 failures. Failed resources (up to 3 shown): File[/etc/default/stunnel4],File[/etc/stunnel/mediawiki.conf],File[/usr/lib/nagios/plugins/check_varnishbackends],File[/usr/lib/nagios/plugins/check_nginx_errorrate] [16:26:31] [02ssl] 07Reception123 closed pull request 03#251: add wiki.mnzp.xyz cert - 13https://git.io/JeA9q [16:26:32] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JeA9s [16:26:34] [02miraheze/ssl] 07Reception123 0375edd09 - add wiki.mnzp.xyz cert (#251) * add wiki.mnzp.xyz cert * Update certs.yaml [16:26:35] [02miraheze/ssl] 07Reception123 deleted branch 03Reception123-patch-2 [16:26:36] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 190 failures. Last run 3 minutes ago with 190 failures. Failed resources (up to 3 shown): File[/usr/lib/nagios/plugins/check_nginx_errorrate],File[/etc/logrotate.d/salt-common],File[/etc/logrotate.d/puppet],File[/etc/update-motd.d/97-last-puppet-run] [16:26:37] [02ssl] 07Reception123 deleted branch 03Reception123-patch-2 - 13https://git.io/vxP9L [16:26:44] [02ssl] 07Reception123 deleted branch 03Reception123-patch-1 - 13https://git.io/vxP9L [16:26:45] [02ssl] 07Reception123 deleted branch 03paladox-patch-1 - 13https://git.io/vxP9L [16:26:47] [02miraheze/ssl] 07Reception123 deleted branch 03paladox-patch-1 [16:26:48] [02miraheze/ssl] 07Reception123 deleted branch 03Reception123-patch-1 [16:27:01] Reception123: how you going to deploy until puppet wakes up? [16:27:02] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA9Z [16:27:04] [02miraheze/mw-config] 07paladox 031381940 - Blcklist staff group Used by SocialProfile. Also blacklist editothersprofiles-private right. [16:27:53] paladox: same Q, shouldn’t we also be recovering puppet? [16:28:19] it'll recover in a few mins [16:28:23] miraheze/mw-config/master/1381940 - paladox The build was broken. https://travis-ci.org/miraheze/mw-config/builds/631339914 [16:28:52] paladox: don't deploy that [16:29:00] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA9C [16:29:01] [02miraheze/mw-config] 07paladox 037679bdf - Fix syntax [16:29:16] SPF|Cloud i'm not :) [16:29:17] anyways fixed ^ [16:29:17] thanks [16:29:30] SPF|Cloud: see PM [16:29:37] PR sent is waiting on u [16:30:07] + the good news from Brent [16:30:21] miraheze/mw-config/master/7679bdf - paladox The build was fixed. https://travis-ci.org/miraheze/mw-config/builds/631340448 [16:30:25] [02puppet] 07Southparkfan closed pull request 03#1172: Update donate@ - 13https://git.io/JeAmk [16:30:27] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA9l [16:30:28] [02miraheze/puppet] 07RhinosF1 03e1a2497 - Update donate@ (#1172) * Update Now handled by Owen. Will contact Owen & Labster to notify * Rebase * Fix this rebase [16:32:36] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [16:32:37] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [16:32:46] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [16:33:00] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [16:33:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [16:33:16] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [16:33:16] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [16:33:28] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [16:33:46] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [16:33:55] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [16:33:59] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [16:34:21] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [16:34:32] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [16:34:34] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:35:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA9z [16:35:09] [02miraheze/services] 07MirahezeSSLBot 03533d9a8 - BOT: Updating services config for wikis [16:35:11] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:35:30] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:36:16] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:37:52] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA9X [16:37:53] [02miraheze/puppet] 07paladox 032dbfb03 - puppet: Increase heap to 750M [16:51:59] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 28940 MB (7% inode=95%); [17:02:23] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2647 MB (10% inode=94%); [17:04:15] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 427 failures. Last run 2 minutes ago with 427 failures. Failed resources (up to 3 shown) [17:04:27] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 2 minutes ago with 3 failures. Failed resources (up to 3 shown) [17:04:30] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 2 minutes ago with 6 failures. Failed resources (up to 3 shown) [17:04:30] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 2 minutes ago with 7 failures. Failed resources (up to 3 shown) [17:04:38] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 420 failures. Last run 2 minutes ago with 420 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.d/20-jobrunner.conf],File[/usr/lib/nagios/plugins/check_jobqueue],File[/etc/ImageMagick-6/policy.xml],File[/srv/mediawiki/robots.php] [17:04:43] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 7 failures. Last run 3 minutes ago with 7 failures. Failed resources (up to 3 shown) [17:04:51] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 3 minutes ago with 6 failures. Failed resources (up to 3 shown) [17:05:04] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [17:05:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 419 failures. Last run 3 minutes ago with 419 failures. Failed resources (up to 3 shown) [17:05:11] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 17 failures. Last run 3 minutes ago with 17 failures. Failed resources (up to 3 shown) [17:05:26] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 19 failures. Last run 3 minutes ago with 19 failures. Failed resources (up to 3 shown) [17:05:31] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [17:05:33] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 422 failures. Last run 3 minutes ago with 422 failures. Failed resources (up to 3 shown) [17:05:35] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 50 failures. Last run 3 minutes ago with 50 failures. Failed resources (up to 3 shown) [17:06:05] paladox: oom? [17:06:20] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 422 failures. Last run 3 minutes ago with 422 failures. Failed resources (up to 3 shown): File[/opt/ploticus_2.42-3+b4_amd64.deb],File[/opt/texvc_3.0.0+git20160613-1_amd64.deb],File[/etc/mathoid/config.yaml],File[/etc/apt/trusted.gpg.d/php.gpg] [17:06:40] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 179 failures. Last run 3 minutes ago with 179 failures. Failed resources (up to 3 shown): File[/etc/default/stunnel4],File[/etc/stunnel/mediawiki.conf],File[/usr/lib/nagios/plugins/check_varnishbackends],File[/usr/lib/nagios/plugins/check_nginx_errorrate] [17:06:51] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 121 failures. Last run 3 minutes ago with 121 failures. Failed resources (up to 3 shown): File[/etc/systemd/system/varnish.service],File[wildcard.miraheze.org],File[wildcard.miraheze.org_private],File[/etc/default/stunnel4] [17:06:53] RIP [17:07:51] yeh [17:12:26] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [17:12:30] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [17:12:49] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [17:12:50] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [17:13:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [17:13:10] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [17:13:24] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [17:13:28] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [17:13:36] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [17:13:46] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [17:14:22] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:14:31] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:14:31] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:14:32] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [17:14:45] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [17:14:58] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [17:15:41] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [17:26:31] Happy #freenode-newyears JohnLewis [17:51:12] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 1.59, 2.35, 1.81 [17:53:08] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 1.73, 1.66, 1.63 [17:55:09] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 4.03, 3.22, 2.30 [17:57:04] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.40, 1.85, 1.96 [17:58:58] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.18, 0.91, 1.55 [18:01:49] !log MariaDB [mhglobal]> update mw_namespaces set ns_dbname = 'metawikis' where ns_dbname = 'metawiki' and ns_namespace_id = 828; [18:01:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:06:53] !log MariaDB [mhglobal]> update mw_namespaces set ns_dbname = 'metawiki' where ns_dbname = 'metawikis' and ns_namespace_id = 828; [18:06:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:06:59] !log MariaDB [mhglobal]> update mw_namespaces set ns_content_model = '' where ns_dbname = 'metawiki' and ns_namespace_id = 828; [18:07:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:09:53] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeAQ8 [18:09:54] [02miraheze/ManageWiki] 07paladox 03a1479cc - Support an empty content model Sometimes the content model is managed by the extension it's self so no need for us to manage it. Fixes T4699 [18:09:56] [02ManageWiki] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vpSns [18:09:57] [02ManageWiki] 07paladox opened pull request 03#127: Support an empty content model - 13https://git.io/JeAQ4 [18:09:59] paladox: what that for [18:10:08] Oooh I see [18:16:46] [02ManageWiki] 07paladox synchronize pull request 03#127: Support an empty content model - 13https://git.io/JeAQ4 [18:16:48] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeAQa [18:16:49] [02miraheze/ManageWiki] 07paladox 03f23d953 - Update ManageWikiFormFactoryBuilder.php [18:16:55] [02ManageWiki] 07paladox closed pull request 03#127: Support an empty content model - 13https://git.io/JeAQ4 [18:16:56] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeAQw [18:16:58] [02miraheze/ManageWiki] 07paladox 03cd15b82 - Support an empty content model (#127) * Support an empty content model Sometimes the content model is managed by the extension it's self so no need for us to manage it. Fixes T4699 * Update ManageWikiFormFactoryBuilder.php [18:17:25] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±2] 13https://git.io/JeAQr [18:17:26] [02miraheze/mediawiki] 07paladox 03d81966f - Update ManageWiki [18:20:59] !log rebuild lc on mw* and lizardfs6 [18:21:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:22:45] !log MariaDB [mhglobal]> update mw_namespaces set ns_content_model = '' where ns_namespace_id = 828; [18:23:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:23:47] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 8.82, 5.15, 2.65 [18:24:15] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown) [18:24:15] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 2 minutes ago with 13 failures. Failed resources (up to 3 shown) [18:24:16] 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) [18:24:44] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 439 failures. Last run 2 minutes ago with 439 failures. Failed resources (up to 3 shown): File[/usr/local/bin/gen_fingerprints],File[/etc/vim/vimrc.local],File[glusterfs.pem],File[glusterfs.key] [18:24:50] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 3 minutes ago with 13 failures. Failed resources (up to 3 shown) [18:25:15] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 21 failures. Last run 3 minutes ago with 21 failures. Failed resources (up to 3 shown) [18:25:17] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 49 failures. Last run 3 minutes ago with 49 failures. Failed resources (up to 3 shown) [18:25:26] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 19 failures. Last run 3 minutes ago with 19 failures. Failed resources (up to 3 shown) [18:25:27] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 25 failures. Last run 3 minutes ago with 25 failures. Failed resources (up to 3 shown) [18:25:39] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 30 failures. Last run 4 minutes ago with 30 failures. Failed resources (up to 3 shown) [18:25:42] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 440 failures. Last run 3 minutes ago with 440 failures. Failed resources (up to 3 shown): File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix],File[/etc/letsencrypt/cli.ini],File[/root/ssl-certificate] [18:25:54] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 122 failures. Last run 2 minutes ago with 122 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] [18:26:19] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [18:26:29] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.d],File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades] [18:26:41] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 179 failures. Last run 4 minutes ago with 179 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] [18:28:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeAQS [18:28:17] [02miraheze/puppet] 07paladox 03cc1635c - Update puppetserver.erb [18:28:52] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 233 failures. Last run 2 minutes ago with 233 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] [18:29:26] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [18:29:36] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.16, 1.33, 1.94 [18:31:31] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.15, 0.82, 1.61 [18:32:26] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [18:33:24] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:38:14] rm -rf /srv/mediawiki/w/cache/managewiki/** on mw* and lizardfs6 [18:41:05] paladox: missing the !log or just typinf [18:41:18] thanks [18:41:20] !log rm -rf /srv/mediawiki/w/cache/managewiki/** on mw* and lizardfs6 [18:41:22] [02mw-config] 07The-Voidwalker reviewed pull request 03#2831 commit - 13https://git.io/JeA7G [18:41:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:42:01] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [18:42:02] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [18:42:13] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [18:42:31] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [18:42:48] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [18:42:50] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [18:43:03] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [18:43:04] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:43:24] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:43:38] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:43:41] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:44:00] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [18:44:22] [02mw-config] 07RhinosF1 reviewed pull request 03#2831 commit - 13https://git.io/JeA7W [18:44:34] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:44:42] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:45:09] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA7l [18:45:11] [02miraheze/puppet] 07paladox 03a853f73 - puppet: Increase heap to 1G [18:45:30] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA78 [18:45:31] [02miraheze/puppet] 07paladox 03ed4cd68 - Update puppetdb.erb [18:46:04] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA74 [18:46:05] [02miraheze/puppet] 07paladox 03bce618c - puppetdb; increase to 200MB [18:47:21] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [18:53:04] [02ManageWiki] 07The-Voidwalker opened pull request 03#128: namespace-talk -> namespacetalk; fixes T4994 - 13https://git.io/JeA7z [18:56:15] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA7i [18:56:17] [02miraheze/mw-config] 07paladox 033ecf56c - Add QuizGame to extension-list [18:56:55] paladox: merhe #128? [18:57:17] ? [18:58:01] oh [18:59:49] [02ManageWiki] 07paladox closed pull request 03#128: namespace-talk -> namespacetalk; fixes T4994 - 13https://git.io/JeA7z [18:59:50] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeA7D [18:59:52] [02miraheze/ManageWiki] 07The-Voidwalker 03532701a - namespace-talk -> namespacetalk; fixes T4994 (#128) [19:00:23] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JeA7S [19:00:25] [02miraheze/mediawiki] 07paladox 03669b4b8 - Update ManageWiki [19:00:38] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [19:01:48] paladox: could you manually ensure namespaces given don’t exists https://phabricator.miraheze.org/T4994 [19:01:49] [ ⚓ T4994 When you delete a name space, the associated name space Discussion still exists ] - phabricator.miraheze.org [19:02:10] 3003,3007,3011 PrivadoWiki [19:02:40] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [19:03:13] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb [19:04:25] paladox: them on hispanowiki and privado is 1683 [19:04:36] s/8/3 [19:04:36] RhinosF1 meant to say: paladox: them on hispanowiki and privado is 1633 [19:04:56] * RhinosF1 suggests read task - energy for 2019 is at 0% [19:05:26] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:06:01] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:06:15] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:07:33] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15190 bytes in 5.217 second response time [19:08:11] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 6.008 second response time [19:08:23] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.662 second response time [19:09:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [19:10:34] RhinosF1 i can do those 2 [19:11:30] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 1.34, 4.35, 3.50 [19:11:45] !log MariaDB [mhglobal]> delete from mw_namespaces where ns_dbname = 'hispanowiki' and ns_namespace_id = 3003; - T4994 [19:11:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:12:09] !log MariaDB [mhglobal]> delete from mw_namespaces where ns_dbname = 'hispanowiki' and ns_namespace_id = 3007; - T4994 [19:12:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:12:33] !log MariaDB [mhglobal]> delete from mw_namespaces where ns_dbname = 'hispanowiki' and ns_namespace_id = 3011; - T4994 [19:12:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:19:10] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.23, 0.50, 1.64 [19:21:24] RhinosF1 he says excluding privado [19:21:31] he only lists hispanowiki which i've done now [19:25:00] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 0.77, 2.36, 2.12 [19:28:14] hispano76: ^ [19:28:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.11, 1.25, 1.80 [19:30:55] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.75, 1.03, 1.59 [19:35:39] paladox: RhinosF1 I meant that I did not review any Wiki that was not mine; except PrivadoWiki that does have the same problem as HispanoWiki. Anyway, I appreciate that they fixed the problem so that no future wiki will have that problem. Maybe the other wikis that have this error will ask for it to be fixed. [19:36:32] hispano76: is it just 1633 on privadowiki [19:37:13] The problem is i'm not sure how to review the 3,000+ other ns [19:37:29] since they will be in other languages too. [19:37:38] custom and core too [19:38:07] paladox: I mean it could be done, but it’d take forever likely [19:38:21] Fix privadowiki and hope they report [19:38:32] Fix what with privadowiki? [19:38:52] "except PrivadoWiki that does have the same problem as HispanoWiki" [19:39:46] paladox: you misunderstand 1633 needs to go [19:40:02] He means he only checked privado and not every other wiki [19:40:13] See hispano76’s message [19:40:29] ok [19:40:31] !log MariaDB [mhglobal]> delete from mw_namespaces where ns_dbname = 'privadowiki' and ns_namespace_id = 1633; [19:40:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:42:33] :) [19:42:49] paladox: see PM for a way to do it fot every wiki. You probably can automate it somehow [19:43:46] ok, well that is time consuming not to mention *could* be error prone [19:44:21] Since MW could create the NS under that i think? [19:44:32] paladox: personally, it’s not worth it - they can report if it’s spotted [19:45:06] yup [19:45:17] !log ManageWikiCDB::changes( 'namespaces' ); - privadowiki [19:45:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:45:41] !log ManageWikiCDB::changes( 'namespaces' ); - hispanowiki [19:45:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:56:55] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 2.01, 3.16, 1.78 [19:57:56] PROBLEM - wiki.udia.ca - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Certificate 'wiki.udia.ca' expired on Wed 28 Aug 2019 06:02:11 PM GMT +0000. [19:58:55] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.17, 1.48, 1.40 [20:49:30] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.82, 1.71, 1.55 [20:51:24] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 5.04, 3.33, 2.22 [21:04:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.35, 1.06, 1.78 [21:06:55] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.35, 0.67, 1.46 [21:33:27] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 4.99, 3.52, 2.30 [21:45:07] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.82, 1.43, 1.88 [21:47:02] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 2.43, 3.40, 2.75 [22:24:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.29, 0.53, 1.97 [22:28:55] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 10.55, 3.83, 2.64 [22:34:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.58, 1.18, 1.81 [22:36:55] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 3.40, 2.20, 2.07 [22:50:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.58, 0.97, 1.99 [22:54:55] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.16, 0.60, 1.43 [23:00:55] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 1.11, 2.78, 2.21 [23:02:55] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 0.43, 1.67, 1.91 [23:03:50] paladox: ^ [23:04:55] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 1.52, 1.32, 1.68 [23:41:45] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 3.47, 2.66, 1.65 [23:43:39] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.76, 1.65, 1.45