[00:01:07] RECOVERY - swiftac1 Puppet on swiftac1 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [00:01:18] PROBLEM - cp1 HTTP 4xx/5xx ERROR Rate on cp1 is UNKNOWN: UNKNOWN - NGINX Error Rate is UNKNOWN [00:02:28] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [00:03:18] PROBLEM - cp1 HTTP 4xx/5xx ERROR Rate on cp1 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [00:05:59] RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:05:59] RECOVERY - graylog1 Puppet on graylog1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:06:45] RECOVERY - mem1 Puppet on mem1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:08:45] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:10:22] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:10:29] RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [00:11:57] RECOVERY - phorge1 Puppet on phorge1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:03] RECOVERY - prometheus1 Puppet on prometheus1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:43] RECOVERY - ldap1 Puppet on ldap1 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [00:14:32] RECOVERY - swiftobject1 Puppet on swiftobject1 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [00:17:13] RECOVERY - jobchron1 Puppet on jobchron1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [00:19:09] RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:19:40] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [00:19:44] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [00:19:51] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:20:30] RECOVERY - bots1 Puppet on bots1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:21:13] RECOVERY - matomo1 Puppet on matomo1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:22:15] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [00:23:27] RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:25:52] RECOVERY - db1 Puppet on db1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:26:08] RECOVERY - cp1 Puppet on cp1 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [00:26:27] RECOVERY - bast1 Puppet on bast1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [00:29:54] RECOVERY - swiftproxy1 Puppet on swiftproxy1 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [00:45:52] PROBLEM - wiki.burning.art - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.burning.art All nameservers failed to answer the query. [01:15:52] PROBLEM - wiki.burning.art - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.burning.art could not be found [04:42:29] PROBLEM - mon1 Puppet on mon1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [04:43:57] PROBLEM - phorge1 Puppet on phorge1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [04:44:43] PROBLEM - ldap1 Puppet on ldap1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:07:58] PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:07:58] PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:07:59] PROBLEM - graylog1 Puppet on graylog1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:08:45] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:12:04] PROBLEM - prometheus1 Puppet on prometheus1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:12:25] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:36:45] PROBLEM - mem1 Puppet on mem1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:40:23] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:46:31] PROBLEM - swiftobject1 Puppet on swiftobject1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:49:14] PROBLEM - jobchron1 Puppet on jobchron1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:49:15] PROBLEM - cp6 Puppet on cp6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:49:51] PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:50:30] PROBLEM - bots1 Puppet on bots1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:51:40] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:51:44] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:53:13] PROBLEM - matomo1 Puppet on matomo1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:54:15] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:54:54] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:57:52] PROBLEM - db1 Puppet on db1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:58:08] PROBLEM - cp1 Puppet on cp1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [05:58:28] PROBLEM - bast1 Puppet on bast1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [06:01:54] PROBLEM - swiftproxy1 Puppet on swiftproxy1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [06:03:07] PROBLEM - swiftac1 Puppet on swiftac1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [06:04:28] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [06:12:25] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [14:47:23] PROBLEM - newcascadia.net - reverse DNS on sslhost is WARNING: LifetimeTimeout: The resolution lifetime expired after 5.405 seconds: Server 1.1.1.1 UDP port 53 answered The DNS operation timed out.; Server 1.1.1.1 UDP port 53 answered The DNS operation timed out.; Server 1.1.1.1 UDP port 53 answered The DNS operation timed out. [15:17:20] PROBLEM - newcascadia.net - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - newcascadia.net All nameservers failed to answer the query. [17:23:09] PROBLEM - wc.wikitide.org on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [17:24:51] PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:25:25] PROBLEM - cp3 HTTPS on cp3 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp3.wikitide.net port 443 after 103 ms: Couldn't connect to server [17:25:30] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:25:45] PROBLEM - cp3 Nginx Backend for mw2 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:25:46] PROBLEM - cp3 PowerDNS Recursor on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:25:53] PROBLEM - cp3 Nginx Backend for phorge1 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:02] PROBLEM - cp3 Current Load on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:05] PROBLEM - cp3 Nginx Backend for mw1 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:07] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:07] PROBLEM - cp3 Nginx Backend for matomo1 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:13] PROBLEM - cp3 Nginx Backend for test1 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:15] PROBLEM - cp3 Nginx Backend for puppet1 on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:26] PROBLEM - cp3 NTP time on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:38] PROBLEM - cp3 ferm_active on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:26:40] PROBLEM - cp3 conntrack_table_size on cp3 is CRITICAL: connect to address 51.75.170.66 port 5666: Connection refusedconnect to host 51.75.170.66 port 5666: Connection refused [17:27:06] PROBLEM - wc.wikitide.org on sslhost is WARNING: WARNING - Certificate 'wikitide.org' expires in 21 day(s) (Tue 20 Feb 2024 12:20:10 PM GMT +0000). [18:55:41] [02puppet] 07Universal-Omega closed pull request 03#15: Add phpldapadmin module - 13https://github.com/WikiTideOrg/puppet/pull/15 [18:55:43] [02WikiTideOrg/puppet] 07Universal-Omega deleted branch 03phpldapadmin [18:55:44] [02puppet] 07Universal-Omega deleted branch 03phpldapadmin - 13https://github.com/WikiTideOrg/puppet [22:30:13] [02WikiTideOrg/WikiTideMagic] 07dependabot[bot] pushed 031 commit to 03dependabot/composer/mediawiki/mediawiki-codesniffer-43.0.0 [+0/-0/±1] 13https://github.com/WikiTideOrg/WikiTideMagic/commit/75667c6af169 [22:30:16] [02WikiTideOrg/WikiTideMagic] 07dependabot[bot] 0375667c6 - Update mediawiki/mediawiki-codesniffer requirement from 42.0.0 to 43.0.0 Updates the requirements on [mediawiki/mediawiki-codesniffer](https://github.com/wikimedia/mediawiki-tools-codesniffer) to permit the latest version. - [Changelog](https://github.com/wikimedia/mediawiki-tools-codesniffer/blob/master/HISTORY.md) - [Commits](https://github.com/wikimedia/mediawiki-tools-codesnif [22:30:17] [02WikiTideMagic] 07dependabot[bot] labeled pull request 03#9: Update mediawiki/mediawiki-codesniffer requirement from 42.0.0 to 43.0.0 - 13https://github.com/WikiTideOrg/WikiTideMagic/pull/9 [22:30:19] [02WikiTideMagic] 07dependabot[bot] labeled pull request 03#9: Update mediawiki/mediawiki-codesniffer requirement from 42.0.0 to 43.0.0 - 13https://github.com/WikiTideOrg/WikiTideMagic/pull/9 [22:30:20] [02WikiTideMagic] 07dependabot[bot] opened pull request 03#9: Update mediawiki/mediawiki-codesniffer requirement from 42.0.0 to 43.0.0 - 13https://github.com/WikiTideOrg/WikiTideMagic/pull/9 [22:30:22] [02WikiTideMagic] 07dependabot[bot] created branch 03dependabot/composer/mediawiki/mediawiki-codesniffer-43.0.0 - 13https://github.com/WikiTideOrg/WikiTideMagic [22:32:16] WikiTideOrg/WikiTideMagic - dependabot[bot] the build has errored.