[00:15:35] PROBLEM - cp37 Disk Space on cp37 is WARNING: DISK WARNING - free space: / 45135MiB (9% inode=99%); [05:41:57] PROBLEM - tech.exputra.com - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [10:18:36] !log [reception@mwtask181] starting deploy of {'world': True, 'force': True, 'versions': '1.42'} to all [10:18:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:21:14] !log [reception@mwtask181] finished deploy of {'world': True, 'force': True, 'versions': '1.42'} to all - SUCCESS in 158s [10:21:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:29:39] [02mw-config] 07Reception123 merged pull request #5784: add BreadCrumbs2 per T12987 (03master...03Reception123-patch-1) 13https://github.com/miraheze/mw-config/pull/5784 [10:29:39] [02mw-config] 07Reception123 pushed 1 new commit to 03master 13https://github.com/miraheze/mw-config/commit/c1290a918cec78740bc6ea17dcbf9113f88fe8f6 [10:29:40] 02mw-config/03master 07Reception123 03c1290a9 add BreadCrumbs2 per T12987 (#5784) [10:29:42] [02mw-config] 07Reception123 04deleted 03Reception123-patch-1 at 03ed6e881 13https://github.com/miraheze/mw-config/commit/ed6e881 [10:29:47] !log [reception@mwtask181] starting deploy of {'world': True, 'l10n': True, 'versions': '1.42'} to all [10:29:49] !log [reception@mwtask181] DEPLOY ABORTED: Non-Zero Exit Code in prep, see output. [10:29:49] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:29:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:29:53] !log [reception@mwtask181] starting deploy of {'world': True, 'l10n': True, 'extension_list': True, 'versions': '1.42'} to all [10:29:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:30:35] miraheze/mw-config - Reception123 the build passed. [10:33:33] !log [reception@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [10:33:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:33:54] !log [reception@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 20s [10:33:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:39:29] !log [reception@mwtask181] finished deploy of {'world': True, 'l10n': True, 'extension_list': True, 'versions': '1.42'} to all - SUCCESS in 576s [10:39:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [10:59:41] [02mediawiki-repos] 07Reception123 pushed 1 new commit to 03master 13https://github.com/miraheze/mediawiki-repos/commit/3c940f2da8ddb99775b51976d059c735b6df318c [10:59:41] 02mediawiki-repos/03master 07Reception123 033c940f2 install NumberHeadings ext per T12989 [11:13:35] PROBLEM - cp37 Disk Space on cp37 is CRITICAL: DISK CRITICAL - free space: / 27206MiB (5% inode=99%); [11:35:25] PROBLEM - mwtask181 Puppet on mwtask181 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_clone_MediaWiki-REL1_42 NumberHeadings] [11:57:11] PROBLEM - test151 Puppet on test151 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_clone_MediaWiki-REL1_42 NumberHeadings] [12:08:08] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 10 backends are down. mw161 mw171 mw181 mw182 mw153 mw164 mw173 mw174 mw183 mw184 [12:09:05] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 4 backends are down. mw182 mw154 mw164 mw183 [12:10:32] [02MirahezeMagic] 07translatewiki pushed 1 new commit to 03master 13https://github.com/miraheze/MirahezeMagic/commit/d69085218ed248537592ff1124a18bd477ee7038 [12:10:32] 02MirahezeMagic/03master 07translatewiki.net 03d690852 Localisation updates from https://translatewiki.net. [12:15:03] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [12:18:17] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10002 milliseconds with 0 bytes received [12:19:07] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4108 bytes in 0.069 second response time [12:21:21] miraheze/MirahezeMagic - translatewiki the build passed. [12:25:14] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [12:26:30] RECOVERY - cp37 HTTPS on cp37 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4130 bytes in 1.651 second response time [12:32:34] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [12:36:00] [Grafana] FIRING: Some MediaWiki Appservers are running out of PHP-FPM workers. https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [12:36:45] RECOVERY - cp37 HTTPS on cp37 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4109 bytes in 5.230 second response time [12:41:27] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4108 bytes in 0.056 second response time [12:42:08] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [12:43:05] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [12:46:00] [Grafana] RESOLVED: PHP-FPM Worker Usage High https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [16:10:56] [02ssl] 07MacFan4000 pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/82197c15f132120c383698457f61f3bc5f372364 [16:10:56] 02ssl/03master 07MacFan4000 0382197c1 add kippuwiki.edapedia.net [16:17:56] PROBLEM - volunteerforukraine.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'volunteerforukraine.com' expires in 14 day(s) (Tue 04 Feb 2025 03:56:25 PM GMT +0000). [16:18:06] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/91aeeadff139c6d3be9455c418194dbe51c3072c [16:18:07] 02ssl/03master 07WikiTideSSLBot 0391aeead Bot: Update SSL cert for volunteerforukraine.com [16:27:38] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 7.30, 7.14, 5.34 [16:31:38] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 5.41, 6.19, 5.37 [16:47:54] RECOVERY - volunteerforukraine.com - LetsEncrypt on sslhost is OK: OK - Certificate 'volunteerforukraine.com' will expire on Sun 20 Apr 2025 03:19:31 PM GMT +0000. [17:03:01] [02puppet] 07Universal-Omega pushed 1 new commit to 03master 13https://github.com/miraheze/puppet/commit/9645e330e4361c5ea46704fa5855084e93988b1d [17:03:01] 02puppet/03master 07CosmicAlpha 039645e33 Update SSH key [17:08:29] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:08:29] PROBLEM - swiftobject161 Puppet on swiftobject161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:08:33] PROBLEM - mw152 Puppet on mw152 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:33] PROBLEM - prometheus151 Puppet on prometheus151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:08:33] PROBLEM - mw154 Puppet on mw154 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:35] PROBLEM - mw151 Puppet on mw151 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:36] PROBLEM - mw172 Puppet on mw172 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:37] PROBLEM - swiftobject181 Puppet on swiftobject181 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:08:40] PROBLEM - mw161 Puppet on mw161 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:44] PROBLEM - mw163 Puppet on mw163 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:45] PROBLEM - mwtask151 Puppet on mwtask151 is CRITICAL: CRITICAL: Puppet has 74 failures. Last run 2 minutes ago with 74 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:08:50] PROBLEM - swiftproxy171 Puppet on swiftproxy171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:08:52] PROBLEM - mw162 Puppet on mw162 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:01] PROBLEM - mw181 Puppet on mw181 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:01] PROBLEM - mem161 Puppet on mem161 is CRITICAL: CRITICAL: Puppet has 31 failures. Last run 2 minutes ago with 31 failures. Failed resources (up to 3 shown): File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf],File[authority certificates] [17:09:02] PROBLEM - mw184 Puppet on mw184 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:03] PROBLEM - swiftobject171 Puppet on swiftobject171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:05] PROBLEM - mwtask161 Puppet on mwtask161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:06] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:13] PROBLEM - reports171 Puppet on reports171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:14] PROBLEM - os162 Puppet on os162 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:15] PROBLEM - ldap171 Puppet on ldap171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:18] PROBLEM - mwtask171 Puppet on mwtask171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:20] PROBLEM - mw183 Puppet on mw183 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:21] PROBLEM - phorge171 Puppet on phorge171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:21] PROBLEM - mw153 Puppet on mw153 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 2 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:25] PROBLEM - puppet181 Puppet on puppet181 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:26] PROBLEM - mw173 Puppet on mw173 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:29] PROBLEM - swiftproxy161 Puppet on swiftproxy161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:29] PROBLEM - os161 Puppet on os161 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:42] PROBLEM - mw182 Puppet on mw182 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:43] PROBLEM - mon181 Puppet on mon181 is CRITICAL: CRITICAL: Puppet has 46 failures. Last run 3 minutes ago with 46 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.conf],File[/etc/modprobe.d/nf_conntrack.conf] [17:09:43] PROBLEM - rdb151 Puppet on rdb151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:44] PROBLEM - jobchron171 Puppet on jobchron171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:45] PROBLEM - os151 Puppet on os151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:09:49] PROBLEM - mw171 Puppet on mw171 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:09:53] PROBLEM - mw164 Puppet on mw164 is CRITICAL: CRITICAL: Puppet has 27 failures. Last run 3 minutes ago with 27 failures. Failed resources (up to 3 shown): File[/usr/local/bin/mediawiki-firejail-convert],File[/etc/firejail/mediawiki.local],File[/etc/firejail/mediawiki-converters.profile],File[/usr/local/bin/mediawiki-firejail-ghostscript] [17:10:03] PROBLEM - swiftobject151 Puppet on swiftobject151 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:10:07] PROBLEM - mw174 Puppet on mw174 is CRITICAL: CRITICAL: Puppet has 66 failures. Last run 3 minutes ago with 66 failures. Failed resources (up to 3 shown): File[/etc/apt/trusted.gpg.d/puppetlabs.gpg],File[/usr/local/bin/puppet-enabled],File[/etc/rsyslog.d],File[/etc/rsyslog.conf] [17:10:26] PROBLEM - swiftac171 Puppet on swiftac171 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [17:10:38] RECOVERY - mw161 Puppet on mw161 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [17:10:53] RECOVERY - mw162 Puppet on mw162 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [17:11:14] RECOVERY - ldap171 Puppet on ldap171 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [17:11:15] RECOVERY - os162 Puppet on os162 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [17:11:22] RECOVERY - phorge171 Puppet on phorge171 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [17:11:43] RECOVERY - jobchron171 Puppet on jobchron171 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:13:31] RECOVERY - os161 Puppet on os161 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [17:13:41] RECOVERY - mon181 Puppet on mon181 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [17:13:47] RECOVERY - os151 Puppet on os151 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [17:14:00] RECOVERY - mw174 Puppet on mw174 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [17:14:19] RECOVERY - swiftobject161 Puppet on swiftobject161 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [17:14:22] RECOVERY - swiftac171 Puppet on swiftac171 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [17:14:24] RECOVERY - prometheus151 Puppet on prometheus151 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [17:14:25] RECOVERY - mw172 Puppet on mw172 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [17:14:27] RECOVERY - mw152 Puppet on mw152 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [17:14:34] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:14:34] RECOVERY - mw151 Puppet on mw151 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [17:14:38] RECOVERY - mw154 Puppet on mw154 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [17:14:38] RECOVERY - mw163 Puppet on mw163 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [17:14:44] RECOVERY - mwtask151 Puppet on mwtask151 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [17:14:50] RECOVERY - swiftproxy171 Puppet on swiftproxy171 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [17:14:51] RECOVERY - mw184 Puppet on mw184 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [17:14:55] RECOVERY - swiftobject171 Puppet on swiftobject171 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [17:14:56] RECOVERY - mw181 Puppet on mw181 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:01] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:04] RECOVERY - mem161 Puppet on mem161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:06] RECOVERY - reports171 Puppet on reports171 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [17:15:07] RECOVERY - mwtask161 Puppet on mwtask161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:08] RECOVERY - mwtask171 Puppet on mwtask171 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:11] RECOVERY - mw153 Puppet on mw153 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:12] RECOVERY - mw183 Puppet on mw183 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:17] RECOVERY - puppet181 Puppet on puppet181 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [17:15:23] RECOVERY - mw173 Puppet on mw173 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:25] RECOVERY - swiftproxy161 Puppet on swiftproxy161 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [17:15:41] RECOVERY - rdb151 Puppet on rdb151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:45] RECOVERY - mw164 Puppet on mw164 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:45] RECOVERY - mw182 Puppet on mw182 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:15:51] RECOVERY - mw171 Puppet on mw171 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [17:16:03] RECOVERY - swiftobject151 Puppet on swiftobject151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:16:28] RECOVERY - swiftobject181 Puppet on swiftobject181 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:37:50] PROBLEM - www.satepedia.com - Cloudflare on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket