[01:18:07] PROBLEM - phorge171 Disk Space on phorge171 is CRITICAL: DISK CRITICAL - free space: / 2557MiB (5% inode=93%); [02:11:29] PROBLEM - phorge171 Puppet on phorge171 is WARNING: WARNING: Puppet last ran 1 hour ago [06:39:29] RECOVERY - phorge171 Puppet on phorge171 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:12:11] PROBLEM - xomnipedia.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'xomnipedia.org' expires in 14 day(s) (Mon 30 Dec 2024 08:58:46 AM GMT +0000). [09:12:22] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/5a5e97c9991fb9a1f6b7cd2c868ce4bd455dcc6f [09:12:22] 02ssl/03master 07WikiTideSSLBot 035a5e97c Bot: Update SSL cert for xomnipedia.org [09:41:51] RECOVERY - xomnipedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'xomnipedia.org' will expire on Sat 15 Mar 2025 08:13:47 AM GMT +0000. [11:33:36] !log [alex@phorge171] destroyed F3430549 (bignatecomments_pages_full.xml) [11:33:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:37:28] !log [alex@phorge171] destroyed F4053887 (deathbattle_pages_full.xml) [11:37:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [11:44:00] !log [alex@phorge171] attempted to destroy F1559000 (monstergirlencyclopedia_pages_full.xml.7z), throwed an exception but it isn't visible on web frontend anymore [11:44:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:04:52] PROBLEM - caverncrusher.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'caverncrusher.com' expires in 14 day(s) (Mon 30 Dec 2024 02:49:34 PM GMT +0000). [15:05:03] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/34bf4aba2e4982c8e317474f581daeb9f410581e [15:05:05] 02ssl/03master 07WikiTideSSLBot 0334bf4ab Bot: Update SSL cert for caverncrusher.com [15:12:52] PROBLEM - christipedia.nl - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'christipedia.nl' expires in 14 day(s) (Mon 30 Dec 2024 02:46:33 PM GMT +0000). [15:13:08] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/ef6535191473f978a9ccf00cd635a916d12e3300 [15:13:08] 02ssl/03master 07WikiTideSSLBot 03ef65351 Bot: Update SSL cert for christipedia.nl [15:34:45] RECOVERY - caverncrusher.com - LetsEncrypt on sslhost is OK: OK - Certificate 'caverncrusher.com' will expire on Sat 15 Mar 2025 02:06:28 PM GMT +0000. [15:55:13] PROBLEM - projdet.ariosodev.com - Cloudflare on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [16:10:52] RECOVERY - christipedia.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'christipedia.nl' will expire on Sat 15 Mar 2025 02:14:33 PM GMT +0000. [16:21:56] !log increase phorge171 disk by 30g [16:22:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:22:07] RECOVERY - phorge171 Disk Space on phorge171 is OK: DISK OK - free space: / 26610MiB (36% inode=95%); [16:35:27] [02puppet] 07paladox pushed 1 new commit to 03master 13https://github.com/miraheze/puppet/commit/38a8ea064d4499f80c6173e6db4ca6aa370727b3 [16:35:27] 02puppet/03master 07paladox 0338a8ea0 phorge: set phd.garbage-collection to 15 days [16:52:08] PROBLEM - swiftobject181 Disk Space on swiftobject181 is CRITICAL: DISK CRITICAL - free space: / 80117MiB (5% inode=85%); [16:53:49] PROBLEM - swiftobject171 Disk Space on swiftobject171 is CRITICAL: DISK CRITICAL - free space: / 80123MiB (5% inode=85%); [18:41:36] [02puppet] 07paladox created 03paladox-patch-1 (+1 new commit) 13https://github.com/miraheze/puppet/commit/69a9088068de [18:41:36] 02puppet/03paladox-patch-1 07paladox 0369a9088 phorge: convert cron to systemd timer [18:41:40] [02puppet] 07paladox opened pull request #4120: phorge: convert cron to systemd timer (03master...03paladox-patch-1) 13https://github.com/miraheze/puppet/pull/4120 [18:41:50] [02puppet] 07coderabbitai[bot] commented on pull request #4120: --- […] 13https://github.com/miraheze/puppet/pull/4120#issuecomment-2543996288 [18:42:19] [02puppet] 07github-actions[bot] pushed 1 new commit to 03paladox-patch-1 13https://github.com/miraheze/puppet/commit/30f2abc4eb568d277f4a893ad00b1b10fe1a9f60 [18:42:19] 02puppet/03paladox-patch-1 07github-actions 0330f2abc CI: lint puppet code to standards… [18:43:34] [02puppet] 07paladox pushed 1 new commit to 03paladox-patch-1 13https://github.com/miraheze/puppet/commit/def756c67ee3125acb03adcf5db3d2d725bbc20d [18:43:34] 02puppet/03paladox-patch-1 07paladox 03def756c Update init.pp [18:44:07] [02puppet] 07paladox merged pull request #4120: phorge: convert cron to systemd timer (03master...03paladox-patch-1) 13https://github.com/miraheze/puppet/pull/4120 [18:44:08] [02puppet] 07paladox pushed 1 new commit to 03master 13https://github.com/miraheze/puppet/commit/72f8af72f6b4a385075a49636da2f39a7db81a70 [18:44:08] 02puppet/03master 07paladox 0372f8af7 phorge: convert cron to systemd timer (#4120)… [18:44:09] [02puppet] 07paladox 04deleted 03paladox-patch-1 at 03def756c 13https://github.com/miraheze/puppet/commit/def756c [19:02:19] [02puppet] 07paladox created 03paladox-patch-1 (+1 new commit) 13https://github.com/miraheze/puppet/commit/ee79756e52b3 [19:02:19] 02puppet/03paladox-patch-1 07paladox 03ee79756 wikitide-backup: fix phorge compressed sql dump file name [19:02:23] [02puppet] 07paladox opened pull request #4121: wikitide-backup: fix phorge compressed sql dump file name (03master...03paladox-patch-1) 13https://github.com/miraheze/puppet/pull/4121 [19:02:29] [02puppet] 07coderabbitai[bot] commented on pull request #4121: --- […] 13https://github.com/miraheze/puppet/pull/4121#issuecomment-2544005376 [19:06:18] [02puppet] 07paladox pushed 1 new commit to 03paladox-patch-1 13https://github.com/miraheze/puppet/commit/6416e82acf7a07d6528d74c23ad9e56f5e873ce8 [19:06:18] 02puppet/03paladox-patch-1 07paladox 036416e82 Update init.pp [19:08:23] [02puppet] 07paladox pushed 1 new commit to 03paladox-patch-1 13https://github.com/miraheze/puppet/commit/e1ca1128be122e5a0c68b5b64f1a1327ca58c7d4 [19:08:23] 02puppet/03paladox-patch-1 07paladox 03e1ca112 Update wikitide-backup.py.erb [19:08:40] [02puppet] 07paladox commented on pull request #4121: @coderabbitai review 13https://github.com/miraheze/puppet/pull/4121#issuecomment-2544007433 [19:08:44] [02puppet] 07coderabbitai[bot] commented on pull request #4121:
[…] 13https://github.com/miraheze/puppet/pull/4121#issuecomment-2544007452 [19:15:00] [02ssl] 07paladox pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/858670504a67d0ee48804fab99900b6b88c06b63 [19:15:00] 02ssl/03master 07paladox 038586705 Fix "pizzatowerwiki" duplicate yaml key [19:15:33] [02puppet] 07coderabbitai[bot] left a review on pull request #4121: **Actionable comments posted: 3** […] 13https://github.com/miraheze/puppet/pull/4121#pullrequestreview-2504656847 [19:15:33] [02puppet] 07coderabbitai[bot] left a file comment in pull request #4121 03e1ca112: _:warning: Potential issue_ […] 13https://github.com/miraheze/puppet/pull/4121#discussion_r1885815407 [19:15:33] [02puppet] 07coderabbitai[bot] left a file comment in pull request #4121 03e1ca112: _:warning: Potential issue_ […] 13https://github.com/miraheze/puppet/pull/4121#discussion_r1885815408 [19:15:33] [02puppet] 07coderabbitai[bot] left a file comment in pull request #4121 03e1ca112: _:hammer_and_wrench: Refactor suggestion_ […] 13https://github.com/miraheze/puppet/pull/4121#discussion_r1885815409 [19:18:42] [02ssl] 07RhinosF1 opened pull request #813: Update .yamllint.yml (07miraheze:03master...07RhinosF1:03patch-20) 13https://github.com/miraheze/ssl/pull/813 [19:18:58] PROBLEM - pizzatower.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Certificate 'pizzatower.wiki' expired on Sun 15 Dec 2024 03:05:36 PM GMT +0000. [19:19:23] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/9dd3b79b5c94571dc34b1d4b733a28159abfc274 [19:19:23] 02ssl/03master 07WikiTideSSLBot 039dd3b79 Bot: Update SSL cert for pizzatower.wiki [19:19:32] [02ssl] 07coderabbitai[bot] commented on pull request #813: The pull request modifies the `.yamllint.yml` configuration file to adjust YAML linting rules. The changes involve enabling the `key-duplicates` rule, which will now flag duplicate keys as errors, and disabling the `line-length` rule, which […] 13https://github.com/miraheze/ssl/pull/813#issuecomment-2544011197 [19:19:49] [02ssl] 07paladox merged 07RhinosF1's pull request #813: Update .yamllint.yml (07miraheze:03master...07RhinosF1:03patch-20) 13https://github.com/miraheze/ssl/pull/813 [19:19:49] [02ssl] 07paladox pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/c34547e8f8cc677a24b8107c81bb683a3c69e841 [19:19:49] 02ssl/03master 07RhinosF1 03c34547e Update .yamllint.yml (#813) [19:20:16] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/b9883b341a2eba7a3d735222b3d2659e637469e4 [19:20:17] 02ssl/03master 07WikiTideSSLBot 03b9883b3 Bot: Update SSL cert for segawiki.com [19:48:36] RECOVERY - pizzatower.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'pizzatower.wiki' will expire on Sat 15 Mar 2025 06:20:47 PM GMT +0000. [20:04:52] RECOVERY - segawiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'segawiki.com' will expire on Sat 15 Mar 2025 06:21:40 PM GMT +0000. [20:28:26] [02puppet] 07paladox merged pull request #4121: wikitide-backup: fix phorge compressed sql dump file name (03master...03paladox-patch-1) 13https://github.com/miraheze/puppet/pull/4121 [20:28:26] [02puppet] 07paladox pushed 1 new commit to 03master 13https://github.com/miraheze/puppet/commit/7aa82ab5769a5e09519fa8c0cdbe602c5ba89b8c [20:28:26] 02puppet/03master 07paladox 037aa82ab wikitide-backup: fix phorge compressed sql dump file name (#4121)… [20:28:27] [02puppet] 07paladox 04deleted 03paladox-patch-1 at 03e1ca112 13https://github.com/miraheze/puppet/commit/e1ca112 [22:05:37] PROBLEM - cp37 Current Load on cp37 is CRITICAL: LOAD CRITICAL - total load average: 13.45, 12.42, 5.39 [22:05:43] PROBLEM - cp36 Nginx Backend for swiftproxy161 on cp36 is CRITICAL: connect to address localhost and port 8206: Connection refused [22:05:46] PROBLEM - cp37 Nginx Backend for swiftproxy161 on cp37 is CRITICAL: connect to address localhost and port 8206: Connection refused [22:05:46] PROBLEM - cp37 Nginx Backend for mw154 on cp37 is CRITICAL: connect to address localhost and port 8122: Connection refused [22:05:49] PROBLEM - cp36 Nginx Backend for mw181 on cp36 is CRITICAL: connect to address localhost and port 8119: Connection refused [22:05:49] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 17 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw154 mw163 mw164 mw173 mw174 mw183 mw184 mediawiki [22:05:50] PROBLEM - cp37 Nginx Backend for mw171 on cp37 is CRITICAL: connect to address localhost and port 8117: Connection refused [22:05:51] PROBLEM - cp37 Nginx Backend for swiftproxy171 on cp37 is CRITICAL: connect to address localhost and port 8207: Connection refused [22:05:53] PROBLEM - cp37 Nginx Backend for mwtask171 on cp37 is CRITICAL: connect to address localhost and port 8161: Connection refused PROBLEM - cp37 Nginx Backend for mw181 on cp37 is CRITICAL: connect to address localhost and port 8119: Connection refused [22:05:53] PROBLEM - cp36 Nginx Backend for mw184 on cp36 is CRITICAL: connect to address localhost and port 8128: Connection refused [22:05:53] PROBLEM - cp36 Nginx Backend for mon181 on cp36 is CRITICAL: connect to address localhost and port 8201: Connection refused [22:05:55] PROBLEM - magistro.co - LetsEncrypt on sslhost is CRITICAL: connect to address magistro.co and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:05:55] PROBLEM - cp37 Nginx Backend for reports171 on cp37 is CRITICAL: connect to address localhost and port 8205: Connection refused [22:05:55] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 4 datacenters are down: 38.46.223.205/cpweb, 38.46.223.206/cpweb, 2602:294:0:b13::110/cpweb, 2602:294:0:b23::112/cpweb [22:06:01] PROBLEM - cp37 Nginx Backend for phorge171 on cp37 is CRITICAL: connect to address localhost and port 8202: Connection refused [22:06:02] PROBLEM - cp37 Nginx Backend for mw161 on cp37 is CRITICAL: connect to address localhost and port 8115: Connection refused [22:06:02] PROBLEM - cp37 Nginx Backend for matomo151 on cp37 is CRITICAL: connect to address localhost and port 8203: Connection refused [22:06:02] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 17 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw154 mw163 mw164 mw173 mw174 mw183 mw184 mediawiki [22:06:06] PROBLEM - cp36 Nginx Backend for mw164 on cp36 is CRITICAL: connect to address localhost and port 8124: Connection refused [22:06:11] PROBLEM - cp36 Nginx Backend for mw172 on cp36 is CRITICAL: connect to address localhost and port 8118: Connection refused [22:06:11] PROBLEM - cp36 Nginx Backend for reports171 on cp36 is CRITICAL: connect to address localhost and port 8205: Connection refused [22:06:14] PROBLEM - cp36 Nginx Backend for test151 on cp36 is CRITICAL: connect to address localhost and port 8181: Connection refused [22:06:16] PROBLEM - cp36 Nginx Backend for phorge171 on cp36 is CRITICAL: connect to address localhost and port 8202: Connection refused [22:06:16] PROBLEM - cp37 Nginx Backend for mw172 on cp37 is CRITICAL: connect to address localhost and port 8118: Connection refused [22:06:17] PROBLEM - segawiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address segawiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:18] PROBLEM - wikappedia.cc - LetsEncrypt on sslhost is CRITICAL: connect to address wikappedia.cc and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:18] PROBLEM - cp36 Nginx Backend for mwtask181 on cp36 is CRITICAL: connect to address localhost and port 8160: Connection refused [22:06:18] PROBLEM - neurologiahpm.com - LetsEncrypt on sslhost is CRITICAL: connect to address neurologiahpm.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:21] PROBLEM - cp36 Nginx Backend for mw182 on cp36 is CRITICAL: connect to address localhost and port 8120: Connection refused [22:06:22] PROBLEM - cp37 Nginx Backend for mwtask151 on cp37 is CRITICAL: connect to address localhost and port 8162: Connection refused [22:06:22] PROBLEM - cp36 Nginx Backend for mw173 on cp36 is CRITICAL: connect to address localhost and port 8125: Connection refused [22:06:28] PROBLEM - cnidaria.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address cnidaria.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:30] PROBLEM - cp37 Nginx Backend for puppet181 on cp37 is CRITICAL: connect to address localhost and port 8204: Connection refused [22:06:31] PROBLEM - cp37 Nginx Backend for mwtask181 on cp37 is CRITICAL: connect to address localhost and port 8160: Connection refused [22:06:33] PROBLEM - cp36 Nginx Backend for mw154 on cp36 is CRITICAL: connect to address localhost and port 8122: Connection refused [22:06:33] PROBLEM - cp36 Nginx Backend for mwtask151 on cp36 is CRITICAL: connect to address localhost and port 8162: Connection refused [22:06:34] PROBLEM - edapedia.net - LetsEncrypt on sslhost is CRITICAL: connect to address edapedia.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:35] PROBLEM - cp36 Nginx Backend for mw161 on cp36 is CRITICAL: connect to address localhost and port 8115: Connection refused [22:06:38] PROBLEM - cp36 Nginx Backend for mw151 on cp36 is CRITICAL: connect to address localhost and port 8113: Connection refused [22:06:40] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp37.wikitide.net port 443 after 3 ms: Couldn't connect to server [22:06:42] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp36.wikitide.net port 443 after 0 ms: Couldn't connect to server [22:06:42] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 4 datacenters are down: 38.46.223.205/cpweb, 38.46.223.206/cpweb, 2602:294:0:b13::110/cpweb, 2602:294:0:b23::112/cpweb [22:06:46] PROBLEM - cp36 Nginx Backend for mw174 on cp36 is CRITICAL: connect to address localhost and port 8126: Connection refused [22:06:47] PROBLEM - cp37 Nginx Backend for mw163 on cp37 is CRITICAL: connect to address localhost and port 8123: Connection refused [22:06:47] PROBLEM - cp36 Nginx Backend for mwtask161 on cp36 is CRITICAL: connect to address localhost and port 8163: Connection refused [22:06:48] PROBLEM - exordium.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address exordium.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:49] PROBLEM - cp37 Nginx Backend for mw182 on cp37 is CRITICAL: connect to address localhost and port 8120: Connection refused [22:06:49] PROBLEM - hololive.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hololive.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:49] PROBLEM - cp36 Nginx Backend for mwtask171 on cp36 is CRITICAL: connect to address localhost and port 8161: Connection refused [22:06:54] PROBLEM - voecwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address voecwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:55] PROBLEM - cp37 Nginx Backend for mw174 on cp37 is CRITICAL: connect to address localhost and port 8126: Connection refused [22:06:57] PROBLEM - decimatedrive.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address decimatedrive.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:06:58] PROBLEM - cp36 Nginx Backend for mw183 on cp36 is CRITICAL: connect to address localhost and port 8127: Connection refused [22:07:01] PROBLEM - evilgeniuswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address evilgeniuswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:02] PROBLEM - cp36 Nginx Backend for mw163 on cp36 is CRITICAL: connect to address localhost and port 8123: Connection refused [22:07:02] PROBLEM - cp36 Nginx Backend for matomo151 on cp36 is CRITICAL: connect to address localhost and port 8203: Connection refused [22:07:05] PROBLEM - cp37 Nginx Backend for mw162 on cp37 is CRITICAL: connect to address localhost and port 8116: Connection refused [22:07:06] PROBLEM - cp37 Nginx Backend for mw152 on cp37 is CRITICAL: connect to address localhost and port 8114: Connection refused [22:07:07] PROBLEM - vesc.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vesc.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:07] PROBLEM - rct.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rct.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:09] PROBLEM - geeu.org - LetsEncrypt on sslhost is CRITICAL: connect to address geeu.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:09] PROBLEM - az-wiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address az-wiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:10] PROBLEM - cp37 Nginx Backend for mw164 on cp37 is CRITICAL: connect to address localhost and port 8124: Connection refused [22:07:10] PROBLEM - cp37 Nginx Backend for mw153 on cp37 is CRITICAL: connect to address localhost and port 8121: Connection refused [22:07:13] PROBLEM - cp36 Nginx Backend for puppet181 on cp36 is CRITICAL: connect to address localhost and port 8204: Connection refused [22:07:17] PROBLEM - crocwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address crocwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:20] PROBLEM - cp37 Nginx Backend for mw173 on cp37 is CRITICAL: connect to address localhost and port 8125: Connection refused [22:07:20] PROBLEM - cp36 Nginx Backend for mw171 on cp36 is CRITICAL: connect to address localhost and port 8117: Connection refused [22:07:21] PROBLEM - cp37 Nginx Backend for mwtask161 on cp37 is CRITICAL: connect to address localhost and port 8163: Connection refused [22:07:23] PROBLEM - cp37 Nginx Backend for mon181 on cp37 is CRITICAL: connect to address localhost and port 8201: Connection refused [22:07:23] PROBLEM - cp36 Nginx Backend for mw153 on cp36 is CRITICAL: connect to address localhost and port 8121: Connection refused [22:07:27] PROBLEM - kodiak.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kodiak.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:29] PROBLEM - vilexia.com - LetsEncrypt on sslhost is CRITICAL: connect to address vilexia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:30] PROBLEM - cp36 Nginx Backend for mw152 on cp36 is CRITICAL: connect to address localhost and port 8114: Connection refused [22:07:31] PROBLEM - cp36 Nginx Backend for mw162 on cp36 is CRITICAL: connect to address localhost and port 8116: Connection refused [22:07:31] PROBLEM - cp37 Nginx Backend for test151 on cp37 is CRITICAL: connect to address localhost and port 8181: Connection refused [22:07:33] PROBLEM - cp37 Nginx Backend for mw184 on cp37 is CRITICAL: connect to address localhost and port 8128: Connection refused [22:07:34] PROBLEM - cp37 Nginx Backend for mw183 on cp37 is CRITICAL: connect to address localhost and port 8127: Connection refused [22:07:35] PROBLEM - cp36 Nginx Backend for swiftproxy171 on cp36 is CRITICAL: connect to address localhost and port 8207: Connection refused [22:07:42] PROBLEM - grayzonewarfare.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address grayzonewarfare.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:42] PROBLEM - cp37 Nginx Backend for mw151 on cp37 is CRITICAL: connect to address localhost and port 8113: Connection refused [22:07:50] PROBLEM - webkinzguide.com - LetsEncrypt on sslhost is CRITICAL: connect to address webkinzguide.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:55] PROBLEM - sdiy.info - LetsEncrypt on sslhost is CRITICAL: connect to address sdiy.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:55] PROBLEM - androidwiki.info - LetsEncrypt on sslhost is CRITICAL: connect to address androidwiki.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:07:58] PROBLEM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address speleo.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:06] PROBLEM - apeirology.com - LetsEncrypt on sslhost is CRITICAL: connect to address apeirology.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:21] PROBLEM - kingdomdeath.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kingdomdeath.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:26] PROBLEM - binrayarchives.com - LetsEncrypt on sslhost is CRITICAL: connect to address binrayarchives.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:40] PROBLEM - journeytheword.wiki - Cloudflare on sslhost is CRITICAL: connect to address journeytheword.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:55] PROBLEM - aryavartpedia.online - LetsEncrypt on sslhost is CRITICAL: connect to address aryavartpedia.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:08:58] PROBLEM - psycho.engineering - LetsEncrypt on sslhost is CRITICAL: connect to address psycho.engineering and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:09:14] PROBLEM - stablestate.org - LetsEncrypt on sslhost is CRITICAL: connect to address stablestate.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:09:15] PROBLEM - podpedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address podpedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:09:17] PROBLEM - hastursnotebook.org - LetsEncrypt on sslhost is CRITICAL: connect to address hastursnotebook.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:09:37] RECOVERY - cp37 Current Load on cp37 is OK: LOAD OK - total load average: 0.25, 5.56, 4.15 [22:09:58] PROBLEM - patternarchive.online - LetsEncrypt on sslhost is CRITICAL: connect to address patternarchive.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:03] PROBLEM - yepedia.xyz - LetsEncrypt on sslhost is CRITICAL: connect to address yepedia.xyz and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:04] PROBLEM - wikimoma.art - LetsEncrypt on sslhost is CRITICAL: connect to address wikimoma.art and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:05] PROBLEM - oxboxtra.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address oxboxtra.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:09] PROBLEM - archivesofhavnor.org - LetsEncrypt on sslhost is CRITICAL: connect to address archivesofhavnor.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:18] PROBLEM - metroidpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address metroidpedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:54] PROBLEM - urbanshade.org - LetsEncrypt on sslhost is CRITICAL: connect to address urbanshade.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:10:55] PROBLEM - baharna.org - Cloudflare on sslhost is CRITICAL: connect to address baharna.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:03] PROBLEM - xomnipedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address xomnipedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:04] PROBLEM - farthestfrontier.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address farthestfrontier.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:10] PROBLEM - emmytherobot.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address emmytherobot.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:17] PROBLEM - encyclopediarobotica.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediarobotica.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:17] PROBLEM - trollpasta.com - LetsEncrypt on sslhost is CRITICAL: connect to address trollpasta.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:26] PROBLEM - christipedia.nl - LetsEncrypt on sslhost is CRITICAL: connect to address christipedia.nl and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:50] PROBLEM - vylet.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vylet.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:57] PROBLEM - beyondtheveilrp.com - LetsEncrypt on sslhost is CRITICAL: connect to address beyondtheveilrp.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:11:57] PROBLEM - squareenixwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address squareenixwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:00] PROBLEM - opendatascot.org - LetsEncrypt on sslhost is CRITICAL: connect to address opendatascot.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:05] PROBLEM - icclopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address icclopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:05] PROBLEM - fanonpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address fanonpedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:21] PROBLEM - ief.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address ief.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:31] PROBLEM - burnout.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address burnout.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:44] PROBLEM - johanloopmans.nl - Cloudflare on sslhost is CRITICAL: connect to address johanloopmans.nl and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:12:56] PROBLEM - darkwaterswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address darkwaterswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:00] PROBLEM - looneypyramids.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address looneypyramids.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:07] PROBLEM - pokemonwiki.info - LetsEncrypt on sslhost is CRITICAL: connect to address pokemonwiki.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:08] PROBLEM - cpmusicwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address cpmusicwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:10] PROBLEM - corru.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address corru.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:15] PROBLEM - lostmediawiki.ru - LetsEncrypt on sslhost is CRITICAL: connect to address lostmediawiki.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:31] PROBLEM - lovebullet.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address lovebullet.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:36] PROBLEM - clubpenguinfanon.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address clubpenguinfanon.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:13:54] PROBLEM - wonderfuleveryday.org - LetsEncrypt on sslhost is CRITICAL: connect to address wonderfuleveryday.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:03] PROBLEM - otherkin.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address otherkin.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:05] PROBLEM - royal-wiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address royal-wiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:06] PROBLEM - annapolishistorywiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address annapolishistorywiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:17] PROBLEM - isocasg.org - LetsEncrypt on sslhost is CRITICAL: connect to address isocasg.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:18] PROBLEM - richterian.com - LetsEncrypt on sslhost is CRITICAL: connect to address richterian.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:21] PROBLEM - dkpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address dkpedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:25] PROBLEM - balloonfightwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address balloonfightwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:29] PROBLEM - sytbay.site - LetsEncrypt on sslhost is CRITICAL: connect to address sytbay.site and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:37] PROBLEM - bobobay.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address bobobay.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:40] PROBLEM - lotr.su - LetsEncrypt on sslhost is CRITICAL: connect to address lotr.su and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:14:51] PROBLEM - comprehensibleinputwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address comprehensibleinputwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:15:03] PROBLEM - *.wikitide.org - LetsEncrypt on sslhost is CRITICAL: connect to address wikitide.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:15:08] PROBLEM - rarewarewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rarewarewiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:15:31] PROBLEM - ncuwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address ncuwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:15:31] PROBLEM - kalons-reverie.com - LetsEncrypt on sslhost is CRITICAL: connect to address kalons-reverie.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:00] PROBLEM - theenglishlakes.uk - LetsEncrypt on sslhost is CRITICAL: connect to address theenglishlakes.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:10] PROBLEM - persist.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address persist.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:18] PROBLEM - ourlifewiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address ourlifewiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:21] PROBLEM - maxcapacity.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address maxcapacity.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:35] PROBLEM - fashiondreamer.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fashiondreamer.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:42] PROBLEM - n64brew.dev - LetsEncrypt on sslhost is CRITICAL: connect to address n64brew.dev and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:46] PROBLEM - thegreatwar.uk - LetsEncrypt on sslhost is CRITICAL: connect to address thegreatwar.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:16:53] PROBLEM - holocron.net - LetsEncrypt on sslhost is CRITICAL: connect to address holocron.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:12] PROBLEM - runzeppelin.ru - LetsEncrypt on sslhost is CRITICAL: connect to address runzeppelin.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:16] PROBLEM - blackmagic.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address blackmagic.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:34] PROBLEM - rosettacode.org - LetsEncrypt on sslhost is CRITICAL: connect to address rosettacode.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:37] PROBLEM - iol.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address iol.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:49] PROBLEM - weavefarers.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address weavefarers.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:17:53] PROBLEM - acuralegendwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address acuralegendwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:18:08] PROBLEM - issue-tracker.wikitide.org - LetsEncrypt on sslhost is CRITICAL: connect to address issue-tracker.wikitide.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:18:23] We know shut up [22:18:24] PROBLEM - sptwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address sptwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:18:26] PROBLEM - lads.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address lads.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [22:18:47] RECOVERY - cp36 Nginx Backend for mw174 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8126 [22:18:47] RECOVERY - cp37 Nginx Backend for mw163 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8123 [22:18:47] RECOVERY - cp36 Nginx Backend for mwtask161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8163 [22:18:49] RECOVERY - cp37 Nginx Backend for mw182 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8120 [22:18:49] RECOVERY - cp36 Nginx Backend for mwtask171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8161 [22:18:55] RECOVERY - cp37 Nginx Backend for mw174 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8126 [22:18:58] RECOVERY - cp36 Nginx Backend for mw183 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8127 [22:19:02] RECOVERY - cp36 Nginx Backend for mw163 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8123 [22:19:02] RECOVERY - cp36 Nginx Backend for matomo151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8203 [22:19:05] RECOVERY - cp37 Nginx Backend for mw162 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8116 [22:19:05] RECOVERY - cp37 Nginx Backend for mw152 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8114 [22:19:10] RECOVERY - cp37 Nginx Backend for mw153 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8121 [22:19:10] RECOVERY - cp37 Nginx Backend for mw164 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8124 [22:19:13] RECOVERY - cp36 Nginx Backend for puppet181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8204 [22:19:20] RECOVERY - cp37 Nginx Backend for mw173 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8125 [22:19:20] RECOVERY - cp36 Nginx Backend for mw171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8117 [22:19:21] RECOVERY - cp37 Nginx Backend for mwtask161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8163 [22:19:23] RECOVERY - cp36 Nginx Backend for mw153 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8121 [22:19:23] RECOVERY - cp37 Nginx Backend for mon181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8201 [22:19:30] RECOVERY - cp36 Nginx Backend for mw152 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8114 [22:19:31] RECOVERY - cp36 Nginx Backend for mw162 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8116 [22:19:31] RECOVERY - cp37 Nginx Backend for test151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8181 [22:19:33] RECOVERY - cp37 Nginx Backend for mw184 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8128 [22:19:34] RECOVERY - cp37 Nginx Backend for mw183 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8127 [22:19:35] RECOVERY - cp36 Nginx Backend for swiftproxy171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8207 [22:19:42] RECOVERY - cp37 Nginx Backend for mw151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8113 [22:19:43] RECOVERY - cp36 Nginx Backend for swiftproxy161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8206 [22:19:46] RECOVERY - cp36 Nginx Backend for mw184 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8128 [22:19:46] RECOVERY - cp37 Nginx Backend for swiftproxy161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8206 [22:19:46] RECOVERY - cp37 Nginx Backend for mw154 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8122 [22:19:46] RECOVERY - cp37 Nginx Backend for mw171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8117 [22:19:49] RECOVERY - cp36 Nginx Backend for mw181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8119 [22:19:49] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [22:19:51] RECOVERY - cp37 Nginx Backend for swiftproxy171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8207 [22:19:53] RECOVERY - cp37 Nginx Backend for mwtask171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8161 [22:19:53] RECOVERY - cp37 Nginx Backend for mw181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8119 [22:19:53] RECOVERY - cp36 Nginx Backend for mon181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8201 [22:19:54] RECOVERY - cp37 Nginx Backend for phorge171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8202 [22:19:55] RECOVERY - cp37 Nginx Backend for reports171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8205 [22:19:56] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [22:20:02] RECOVERY - cp37 Nginx Backend for mw161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8115 [22:20:02] RECOVERY - cp37 Nginx Backend for matomo151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8203 [22:20:02] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [22:20:06] RECOVERY - cp36 Nginx Backend for mw164 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8124 [22:20:11] RECOVERY - cp36 Nginx Backend for mw172 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8118 [22:20:11] RECOVERY - cp36 Nginx Backend for reports171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8205 [22:20:13] RECOVERY - cp36 Nginx Backend for test151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8181 [22:20:16] RECOVERY - cp36 Nginx Backend for phorge171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8202 [22:20:16] RECOVERY - cp37 Nginx Backend for mw172 on cp37 is OK: TCP OK - 0.001 second response time on localhost port 8118 [22:20:18] RECOVERY - cp36 Nginx Backend for mwtask181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8160 [22:20:21] RECOVERY - cp36 Nginx Backend for mw182 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8120 [22:20:22] RECOVERY - cp37 Nginx Backend for mwtask151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8162 [22:20:22] RECOVERY - cp36 Nginx Backend for mw173 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8125 [22:20:30] RECOVERY - cp37 Nginx Backend for puppet181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8204 [22:20:31] RECOVERY - cp37 Nginx Backend for mwtask181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8160 [22:20:33] RECOVERY - cp36 Nginx Backend for mw154 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8122 [22:20:33] RECOVERY - cp36 Nginx Backend for mwtask151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8162 [22:20:35] RECOVERY - cp36 Nginx Backend for mw161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8115 [22:20:38] RECOVERY - cp36 Nginx Backend for mw151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8113 [22:20:40] RECOVERY - cp37 HTTPS on cp37 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4138 bytes in 0.197 second response time [22:20:42] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4139 bytes in 0.056 second response time [22:20:42] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [22:21:19] There we go [22:34:59] RECOVERY - wikappedia.cc - LetsEncrypt on sslhost is OK: OK - Certificate 'wikappedia.cc' will expire on Tue 07 Jan 2025 02:53:39 PM GMT +0000. [22:35:19] RECOVERY - edapedia.net - LetsEncrypt on sslhost is OK: OK - Certificate 'edapedia.net' will expire on Wed 22 Jan 2025 02:47:33 AM GMT +0000. [22:35:37] RECOVERY - magistro.co - LetsEncrypt on sslhost is OK: OK - Certificate 'magistro.co' will expire on Tue 31 Dec 2024 04:48:12 PM GMT +0000. [22:35:39] RECOVERY - cnidaria.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'cnidaria.wiki' will expire on Tue 18 Feb 2025 05:57:37 PM GMT +0000. [22:35:47] RECOVERY - voecwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'voecwiki.com' will expire on Thu 09 Jan 2025 01:23:53 AM GMT +0000. [22:36:02] RECOVERY - evilgeniuswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'evilgeniuswiki.com' will expire on Tue 11 Mar 2025 12:24:51 PM GMT +0000. [22:36:03] RECOVERY - segawiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'segawiki.com' will expire on Sat 15 Mar 2025 06:21:40 PM GMT +0000. [22:36:05] RECOVERY - neurologiahpm.com - LetsEncrypt on sslhost is OK: OK - Certificate 'neurologiahpm.com' will expire on Tue 25 Feb 2025 11:32:58 AM GMT +0000. [22:36:14] RECOVERY - rct.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'rct.wiki' will expire on Sat 08 Mar 2025 09:57:02 AM GMT +0000. [22:36:26] RECOVERY - hololive.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'hololive.wiki' will expire on Fri 07 Mar 2025 06:05:48 PM GMT +0000. [22:36:36] RECOVERY - decimatedrive.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'decimatedrive.wiki' will expire on Sun 05 Jan 2025 10:46:22 PM GMT +0000. [22:36:37] RECOVERY - geeu.org - LetsEncrypt on sslhost is OK: OK - Certificate 'geeu.org' will expire on Tue 11 Feb 2025 02:36:30 PM GMT +0000. [22:36:40] RECOVERY - exordium.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'exordium.wiki' will expire on Wed 12 Feb 2025 08:08:49 PM GMT +0000. [22:36:40] RECOVERY - webkinzguide.com - LetsEncrypt on sslhost is OK: OK - Certificate 'webkinzguide.com' will expire on Sun 09 Mar 2025 11:01:02 AM GMT +0000. [22:36:42] RECOVERY - vilexia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'vilexia.com' will expire on Sat 15 Feb 2025 05:40:59 PM GMT +0000. [22:36:48] RECOVERY - sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Sun 02 Mar 2025 02:53:50 PM GMT +0000. [22:36:54] RECOVERY - az-wiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'az-wiki.com' will expire on Tue 31 Dec 2024 04:48:36 PM GMT +0000. [22:36:57] RECOVERY - vesc.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'vesc.wiki' will expire on Tue 11 Mar 2025 01:54:22 PM GMT +0000. [22:37:00] RECOVERY - kodiak.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'kodiak.wiki' will expire on Fri 24 Jan 2025 03:23:25 AM GMT +0000. [22:37:12] RECOVERY - kingdomdeath.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'kingdomdeath.wiki' will expire on Fri 14 Mar 2025 08:40:52 AM GMT +0000. [22:37:13] RECOVERY - crocwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'crocwiki.com' will expire on Sat 08 Mar 2025 03:13:41 PM GMT +0000. [22:37:22] RECOVERY - binrayarchives.com - LetsEncrypt on sslhost is OK: OK - Certificate 'binrayarchives.com' will expire on Sun 09 Feb 2025 09:53:22 PM GMT +0000. [22:37:26] RECOVERY - androidwiki.info - LetsEncrypt on sslhost is OK: OK - Certificate 'androidwiki.info' will expire on Mon 27 Jan 2025 03:47:10 PM GMT +0000. [22:37:41] RECOVERY - grayzonewarfare.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'grayzonewarfare.wiki' will expire on Wed 22 Jan 2025 08:13:00 PM GMT +0000. [22:37:56] RECOVERY - speleo.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'speleo.wiki' will expire on Thu 06 Mar 2025 09:11:56 PM GMT +0000. [22:38:06] RECOVERY - apeirology.com - LetsEncrypt on sslhost is OK: OK - Certificate 'apeirology.com' will expire on Sun 09 Mar 2025 04:22:02 PM GMT +0000. [22:38:08] RECOVERY - stablestate.org - LetsEncrypt on sslhost is OK: OK - Certificate 'stablestate.org' will expire on Fri 07 Mar 2025 07:29:55 AM GMT +0000. [22:38:12] RECOVERY - aryavartpedia.online - LetsEncrypt on sslhost is OK: OK - Certificate 'aryavartpedia.online' will expire on Mon 20 Jan 2025 12:08:24 AM GMT +0000. [22:38:13] RECOVERY - psycho.engineering - LetsEncrypt on sslhost is OK: OK - Certificate 'psycho.engineering' will expire on Tue 11 Mar 2025 12:21:00 PM GMT +0000. [22:38:18] RECOVERY - hastursnotebook.org - LetsEncrypt on sslhost is OK: OK - Certificate 'hastursnotebook.org' will expire on Mon 10 Mar 2025 07:54:11 AM GMT +0000. [22:38:18] RECOVERY - journeytheword.wiki - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [22:38:56] RECOVERY - archivesofhavnor.org - LetsEncrypt on sslhost is OK: OK - Certificate 'archivesofhavnor.org' will expire on Sat 08 Feb 2025 02:39:28 PM GMT +0000. [22:39:02] RECOVERY - yepedia.xyz - LetsEncrypt on sslhost is OK: OK - Certificate 'yepedia.xyz' will expire on Sat 08 Feb 2025 02:50:34 PM GMT +0000. [22:39:07] RECOVERY - wikimoma.art - LetsEncrypt on sslhost is OK: OK - Certificate 'wikimoma.art' will expire on Fri 14 Mar 2025 02:42:04 PM GMT +0000. [22:39:12] RECOVERY - podpedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'podpedia.org' will expire on Fri 07 Mar 2025 09:06:45 AM GMT +0000. [22:39:18] RECOVERY - patternarchive.online - LetsEncrypt on sslhost is OK: OK - Certificate 'patternarchive.online' will expire on Thu 02 Jan 2025 03:56:22 PM GMT +0000. [22:39:29] RECOVERY - baharna.org - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [22:39:35] RECOVERY - farthestfrontier.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'farthestfrontier.wiki' will expire on Wed 12 Feb 2025 08:09:17 PM GMT +0000. [22:39:36] RECOVERY - metroidpedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'metroidpedia.com' will expire on Sun 09 Mar 2025 03:37:37 PM GMT +0000. [22:39:45] RECOVERY - urbanshade.org - LetsEncrypt on sslhost is OK: OK - Certificate 'urbanshade.org' will expire on Wed 08 Jan 2025 03:18:01 PM GMT +0000. [22:39:54] RECOVERY - trollpasta.com - LetsEncrypt on sslhost is OK: OK - Certificate 'trollpasta.com' will expire on Thu 02 Jan 2025 04:17:18 PM GMT +0000. [22:39:58] RECOVERY - encyclopediarobotica.org - LetsEncrypt on sslhost is OK: OK - Certificate 'encyclopediarobotica.org' will expire on Sun 09 Feb 2025 02:29:45 PM GMT +0000. [22:39:59] RECOVERY - oxboxtra.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'oxboxtra.wiki' will expire on Wed 29 Jan 2025 06:47:21 AM GMT +0000. [22:40:03] RECOVERY - emmytherobot.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'emmytherobot.wiki' will expire on Tue 14 Jan 2025 01:22:21 PM GMT +0000. [22:40:46] RECOVERY - vylet.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'vylet.wiki' will expire on Thu 06 Feb 2025 02:42:38 AM GMT +0000. [22:40:47] RECOVERY - squareenixwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'squareenixwiki.com' will expire on Sun 09 Mar 2025 12:28:04 AM GMT +0000. [22:40:49] RECOVERY - opendatascot.org - LetsEncrypt on sslhost is OK: OK - Certificate 'opendatascot.org' will expire on Wed 12 Mar 2025 08:48:09 AM GMT +0000. [22:40:50] RECOVERY - xomnipedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'xomnipedia.org' will expire on Sat 15 Mar 2025 08:13:47 AM GMT +0000. [22:41:01] RECOVERY - burnout.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'burnout.wiki' will expire on Thu 02 Jan 2025 04:09:56 PM GMT +0000. [22:41:04] RECOVERY - beyondtheveilrp.com - LetsEncrypt on sslhost is OK: OK - Certificate 'beyondtheveilrp.com' will expire on Fri 21 Feb 2025 07:24:14 PM GMT +0000. [22:41:10] RECOVERY - christipedia.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'christipedia.nl' will expire on Sat 15 Mar 2025 02:14:33 PM GMT +0000. [22:41:11] RECOVERY - fanonpedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'fanonpedia.com' will expire on Wed 15 Jan 2025 01:02:33 PM GMT +0000. [22:41:30] RECOVERY - icclopedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'icclopedia.org' will expire on Sun 09 Mar 2025 02:26:09 AM GMT +0000. [22:41:46] RECOVERY - johanloopmans.nl - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [22:41:47] RECOVERY - ief.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'ief.wiki' will expire on Sat 18 Jan 2025 10:09:32 PM GMT +0000. [22:41:58] RECOVERY - looneypyramids.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'looneypyramids.wiki' will expire on Sun 09 Mar 2025 08:29:55 AM GMT +0000. [22:42:07] RECOVERY - cpmusicwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'cpmusicwiki.com' will expire on Thu 30 Jan 2025 11:52:22 AM GMT +0000. [22:42:40] RECOVERY - royal-wiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'royal-wiki.org' will expire on Sun 09 Mar 2025 12:08:28 AM GMT +0000. [22:42:41] RECOVERY - darkwaterswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'darkwaterswiki.com' will expire on Wed 08 Jan 2025 04:02:59 PM GMT +0000. [22:42:52] RECOVERY - lostmediawiki.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'lostmediawiki.ru' will expire on Wed 22 Jan 2025 02:19:38 PM GMT +0000. [22:42:57] RECOVERY - lovebullet.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'lovebullet.wiki' will expire on Sat 01 Mar 2025 11:30:48 PM GMT +0000. [22:43:03] RECOVERY - otherkin.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'otherkin.wiki' will expire on Wed 22 Jan 2025 02:41:57 PM GMT +0000. [22:43:04] RECOVERY - isocasg.org - LetsEncrypt on sslhost is OK: OK - Certificate 'isocasg.org' will expire on Wed 29 Jan 2025 03:51:53 PM GMT +0000. [22:43:04] RECOVERY - pokemonwiki.info - LetsEncrypt on sslhost is OK: OK - Certificate 'pokemonwiki.info' will expire on Thu 02 Jan 2025 04:07:38 PM GMT +0000. [22:43:06] RECOVERY - wonderfuleveryday.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wonderfuleveryday.org' will expire on Sun 16 Feb 2025 01:46:05 AM GMT +0000. [22:43:06] RECOVERY - richterian.com - LetsEncrypt on sslhost is OK: OK - Certificate 'richterian.com' will expire on Fri 07 Feb 2025 08:52:27 PM GMT +0000. [22:43:08] RECOVERY - corru.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'corru.wiki' will expire on Wed 22 Jan 2025 02:58:47 AM GMT +0000. [22:43:19] RECOVERY - balloonfightwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'balloonfightwiki.org' will expire on Tue 21 Jan 2025 04:30:50 PM GMT +0000. [22:43:28] RECOVERY - lotr.su - LetsEncrypt on sslhost is OK: OK - Certificate 'lotr.su' will expire on Wed 12 Mar 2025 04:28:42 PM GMT +0000. [22:43:34] RECOVERY - clubpenguinfanon.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'clubpenguinfanon.wiki' will expire on Thu 09 Jan 2025 11:54:12 PM GMT +0000. [22:43:36] RECOVERY - dkpedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'dkpedia.com' will expire on Sun 09 Mar 2025 11:38:22 AM GMT +0000. [22:43:56] RECOVERY - annapolishistorywiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'annapolishistorywiki.org' will expire on Sun 02 Feb 2025 09:10:19 AM GMT +0000. [22:44:22] RECOVERY - sytbay.site - LetsEncrypt on sslhost is OK: OK - Certificate 'sytbay.site' will expire on Mon 03 Feb 2025 10:49:41 PM GMT +0000. [22:44:32] RECOVERY - bobobay.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'bobobay.wiki' will expire on Wed 12 Feb 2025 02:26:39 PM GMT +0000. [22:44:34] RECOVERY - kalons-reverie.com - LetsEncrypt on sslhost is OK: OK - Certificate 'kalons-reverie.com' will expire on Fri 10 Jan 2025 09:48:16 AM GMT +0000. [22:44:36] RECOVERY - *.wikitide.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.org' will expire on Mon 27 Jan 2025 07:57:39 PM GMT +0000. [22:44:42] RECOVERY - rarewarewiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'rarewarewiki.com' will expire on Sun 09 Mar 2025 03:52:46 PM GMT +0000. [22:44:48] RECOVERY - comprehensibleinputwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'comprehensibleinputwiki.org' will expire on Tue 11 Feb 2025 02:39:50 PM GMT +0000. [22:45:00] RECOVERY - ncuwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'ncuwiki.com' will expire on Sun 09 Mar 2025 05:24:06 PM GMT +0000. [22:45:00] RECOVERY - theenglishlakes.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'theenglishlakes.uk' will expire on Sat 01 Feb 2025 06:17:35 PM GMT +0000. [22:45:15] RECOVERY - ourlifewiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'ourlifewiki.org' will expire on Sun 26 Jan 2025 06:18:01 PM GMT +0000. [22:45:31] RECOVERY - thegreatwar.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thegreatwar.uk' will expire on Fri 14 Mar 2025 02:25:51 PM GMT +0000. [22:46:02] RECOVERY - blackmagic.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'blackmagic.wiki' will expire on Sun 23 Feb 2025 07:21:15 PM GMT +0000. [22:46:03] RECOVERY - persist.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'persist.wiki' will expire on Sat 08 Mar 2025 10:58:16 PM GMT +0000. [22:46:10] RECOVERY - fashiondreamer.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'fashiondreamer.wiki' will expire on Fri 14 Mar 2025 01:50:18 PM GMT +0000. [22:46:12] RECOVERY - runzeppelin.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'runzeppelin.ru' will expire on Fri 07 Mar 2025 06:45:22 AM GMT +0000. [22:46:13] RECOVERY - iol.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'iol.wiki' will expire on Sun 09 Mar 2025 12:04:46 AM GMT +0000. [22:46:21] RECOVERY - maxcapacity.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'maxcapacity.wiki' will expire on Tue 18 Feb 2025 03:36:47 PM GMT +0000. [22:46:34] RECOVERY - n64brew.dev - LetsEncrypt on sslhost is OK: OK - Certificate 'n64brew.dev' will expire on Fri 07 Mar 2025 06:15:58 PM GMT +0000. [22:46:37] RECOVERY - rosettacode.org - LetsEncrypt on sslhost is OK: OK - Certificate 'rosettacode.org' will expire on Tue 21 Jan 2025 01:55:49 AM GMT +0000. [22:46:42] RECOVERY - weavefarers.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'weavefarers.wiki' will expire on Wed 19 Feb 2025 12:42:15 AM GMT +0000. [22:46:45] RECOVERY - holocron.net - LetsEncrypt on sslhost is OK: OK - Certificate 'holocron.net' will expire on Mon 24 Feb 2025 03:12:55 AM GMT +0000. [22:46:53] RECOVERY - issue-tracker.wikitide.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.org' will expire on Mon 27 Jan 2025 07:57:39 PM GMT +0000. [22:47:11] RECOVERY - lads.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'lads.wiki' will expire on Thu 06 Mar 2025 04:34:20 PM GMT +0000. [22:47:35] RECOVERY - sptwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'sptwiki.org' will expire on Sun 26 Jan 2025 06:17:34 PM GMT +0000. [22:47:46] RECOVERY - acuralegendwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'acuralegendwiki.org' will expire on Sun 09 Mar 2025 02:34:56 AM GMT +0000. [23:31:20] PROBLEM - swiftobject151 Disk Space on swiftobject151 is CRITICAL: DISK CRITICAL - free space: / 80124MiB (5% inode=85%);