[00:05:27] PROBLEM - misc4 Prometheus on misc4 is CRITICAL: connect to address 185.52.3.121 and port 9090: Connection refused [00:07:27] RECOVERY - misc4 Prometheus on misc4 is OK: TCP OK - 0.001 second response time on 185.52.3.121 port 9090 [00:33:01] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 212 failures. Last run 2 minutes ago with 212 failures. Failed resources (up to 3 shown) [00:33:04] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:07] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:09] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:10] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:10] PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:19] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:20] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:22] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:22] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:33:34] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:34:02] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 18 failures. Last run 3 minutes ago with 18 failures. Failed resources (up to 3 shown) [00:34:08] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 3 minutes ago with 16 failures. Failed resources (up to 3 shown) [00:34:28] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [00:34:31] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:34:34] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:34:35] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [00:35:03] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Puppet has 227 failures. Last run 4 minutes ago with 227 failures. Failed resources (up to 3 shown) [00:43:01] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [00:43:04] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [00:43:11] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [00:43:12] RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [00:43:29] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [00:43:56] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:03] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:28] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:29] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:30] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:31] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [00:44:51] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:44:56] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:45:08] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:45:13] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:45:25] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:45:26] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:45:29] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [03:40:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeVUg [03:40:09] [02miraheze/services] 07MirahezeSSLBot 030f35160 - BOT: Updating services config for wikis [06:26:25] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2821 MB (11% inode=94%); [06:42:21] .time Zppix [06:42:21] 2019-11-08 - 00:42:21CST [06:55:01] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown): Package[php7.3-apcu],Package[php7.3-redis] [07:03:01] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [10:34:28] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2649 MB (10% inode=94%); [13:10:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeVOL [13:10:08] [02miraheze/services] 07MirahezeSSLBot 037bfc333 - BOT: Updating services config for wikis [14:27:25] hey there yall [17:15:26] PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is WARNING: WARNING - NGINX Error Rate is 42% [17:16:14] heyo [17:16:55] just asking for me wiki [17:17:26] RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 29% [18:15:29] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php7.3-redis] [18:23:28] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [20:30:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeVlV [20:30:09] [02miraheze/services] 07MirahezeSSLBot 0302454c9 - BOT: Updating services config for wikis [20:33:20] Hey Voidwalker [20:35:29] hi [20:37:03] Hey apap [20:38:18] hi [21:05:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeV8U [21:05:08] [02miraheze/services] 07MirahezeSSLBot 03ad1ef35 - BOT: Updating services config for wikis [22:03:18] !log delete from mw_namespaces where ns_namespace_name = 'Forum_talk' and ns_dbname = 'csydeswiki'; on db4 - https://meta.miraheze.org/w/index.php?title=Stewards%27_noticeboard&oldid=88031#Issue_with_the_redundant_Forum_talk_namespace_which_hasn.27t_been_deleted_properly [22:03:20] [ Stewards' noticeboard - Miraheze Meta ] - meta.miraheze.org [22:03:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master