[00:03:05] PROBLEM - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is UNKNOWN: UNKNOWN - NGINX Error Rate is UNKNOWN [00:03:35] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 50%, RTA = 31.30 ms [00:05:15] RECOVERY - cp36 Disk Space on cp36 is OK: DISK OK - free space: / 21341MiB (24% inode=98%); [00:07:41] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.36 ms [00:16:51] RECOVERY - cp37 Disk Space on cp37 is OK: DISK OK - free space: / 52062MiB (11% inode=99%); [00:17:05] RECOVERY - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is OK: OK - NGINX Error Rate is 2% [00:31:04] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 28%, RTA = 31.39 ms [00:35:07] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.36 ms [00:47:51] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [00:56:04] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.42 ms [00:57:34] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 21.87, 18.35, 10.29 [01:00:23] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 60%, RTA = 31.42 ms [01:04:27] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.40 ms [01:07:33] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 9.80, 18.22, 14.90 [01:18:51] PROBLEM - cp37 Disk Space on cp37 is WARNING: DISK WARNING - free space: / 49822MiB (10% inode=99%); [01:40:33] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 37%, RTA = 31.38 ms [01:44:36] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.38 ms [02:06:03] [02CreateWiki] 07Universal-Omega pushed 1 new commit to 03master 13https://github.com/miraheze/CreateWiki/commit/62df6bf07ac3dc643a195237c507ba224bb61623 [02:06:03] 02CreateWiki/03master 07CosmicAlpha 0362df6bf Simplify comments [02:10:32] [02CreateWiki] 07Universal-Omega pushed 1 new commit to 03master 13https://github.com/miraheze/CreateWiki/commit/f235f3e850880e4aca6779be2ef4ac694d645a88 [02:10:32] 02CreateWiki/03master 07CosmicAlpha 03f235f3e Use readonly [02:11:29] [02CreateWiki] 07Universal-Omega pushed 1 new commit to 03master 13https://github.com/miraheze/CreateWiki/commit/f7a7897a983036c0c7403b6ba0db2dff2104f19b [02:11:29] 02CreateWiki/03master 07CosmicAlpha 03f7a7897 Fix tabbing [02:18:33] RECOVERY - guia.esporo.net - Cloudflare on sslhost is OK: OK - Certificate 'guia.esporo.net' will expire on Wed 26 Mar 2025 02:54:55 PM GMT +0000. [02:23:03] miraheze/CreateWiki - Universal-Omega the build passed. [02:23:51] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [02:25:50] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.62 ms [02:30:09] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 50%, RTA = 31.42 ms [02:40:25] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.39 ms [04:22:07] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [04:26:10] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.35 ms [04:33:27] PROBLEM - emmytherobot.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address emmytherobot.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:33:38] PROBLEM - cp36 Nginx Backend for swiftproxy171 on cp36 is CRITICAL: connect to address localhost and port 8207: Connection refused [04:33:44] PROBLEM - allthetropes.org - LetsEncrypt on sslhost is CRITICAL: connect to address allthetropes.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:33:44] PROBLEM - pso2ngs.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address pso2ngs.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:33:50] PROBLEM - cp36 Nginx Backend for mwtask161 on cp36 is CRITICAL: connect to address localhost and port 8163: Connection refused [04:33:50] PROBLEM - cp36 Nginx Backend for mwtask151 on cp36 is CRITICAL: connect to address localhost and port 8162: Connection refused [04:33:51] PROBLEM - cp36 Nginx Backend for mwtask181 on cp36 is CRITICAL: connect to address localhost and port 8160: Connection refused [04:33:54] PROBLEM - cp36 Nginx Backend for phorge171 on cp36 is CRITICAL: connect to address localhost and port 8202: Connection refused [04:33:54] PROBLEM - knifepointhorror.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address knifepointhorror.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:33:56] PROBLEM - cp36 Nginx Backend for puppet181 on cp36 is CRITICAL: connect to address localhost and port 8204: Connection refused [04:33:56] PROBLEM - ecole.science - LetsEncrypt on sslhost is CRITICAL: connect to address ecole.science and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:33:58] PROBLEM - cp36 Nginx Backend for mw163 on cp36 is CRITICAL: connect to address localhost and port 8123: Connection refused [04:34:01] PROBLEM - cp36 Nginx Backend for mw161 on cp36 is CRITICAL: connect to address localhost and port 8115: Connection refused [04:34:04] PROBLEM - thegreatwar.uk - LetsEncrypt on sslhost is CRITICAL: connect to address thegreatwar.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:04] PROBLEM - burnout.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address burnout.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:10] PROBLEM - cp36 Nginx Backend for mw184 on cp36 is CRITICAL: connect to address localhost and port 8128: Connection refused [04:34:10] PROBLEM - baligawiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address baligawiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:10] PROBLEM - holocron.net - LetsEncrypt on sslhost is CRITICAL: connect to address holocron.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:13] PROBLEM - cp36 Nginx Backend for mw181 on cp36 is CRITICAL: connect to address localhost and port 8119: Connection refused [04:34:24] PROBLEM - ourlifewiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address ourlifewiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:25] PROBLEM - cp36 Nginx Backend for mw154 on cp36 is CRITICAL: connect to address localhost and port 8122: Connection refused [04:34:30] PROBLEM - cp36 Nginx Backend for mw174 on cp36 is CRITICAL: connect to address localhost and port 8126: Connection refused [04:34:31] PROBLEM - cp36 Nginx Backend for swiftproxy161 on cp36 is CRITICAL: connect to address localhost and port 8206: Connection refused [04:34:32] PROBLEM - cp36 Nginx Backend for mw164 on cp36 is CRITICAL: connect to address localhost and port 8124: Connection refused [04:34:34] 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 3 ms: Couldn't connect to server [04:34:35] PROBLEM - cp36 Nginx Backend for mw173 on cp36 is CRITICAL: connect to address localhost and port 8125: Connection refused [04:34:37] PROBLEM - cp36 Nginx Backend for mw152 on cp36 is CRITICAL: connect to address localhost and port 8114: Connection refused [04:34:37] PROBLEM - z1r.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address z1r.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:34:57] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is CRITICAL: CRITICAL - NGINX Error Rate is 94% [04:34:57] PROBLEM - cp36 Nginx Backend for mw162 on cp36 is CRITICAL: connect to address localhost and port 8116: Connection refused [04:34:57] PROBLEM - cp36 Nginx Backend for mw182 on cp36 is CRITICAL: connect to address localhost and port 8120: Connection refused [04:34:58] PROBLEM - cp36 Nginx Backend for mw151 on cp36 is CRITICAL: connect to address localhost and port 8113: Connection refused [04:34:58] PROBLEM - cp36 Nginx Backend for mw172 on cp36 is CRITICAL: connect to address localhost and port 8118: Connection refused [04:35:01] PROBLEM - osrwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address osrwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:01] PROBLEM - project-patterns.com - LetsEncrypt on sslhost is CRITICAL: connect to address project-patterns.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:02] PROBLEM - mh142.com - LetsEncrypt on sslhost is CRITICAL: connect to address mh142.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:02] PROBLEM - looneypyramids.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address looneypyramids.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:02] PROBLEM - exmormon.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address exmormon.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:02] PROBLEM - xomnipedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address xomnipedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:04] PROBLEM - cp36 Nginx Backend for mon181 on cp36 is CRITICAL: connect to address localhost and port 8201: Connection refused [04:35:06] PROBLEM - ncuwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address ncuwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:08] PROBLEM - cp36 Nginx Backend for reports171 on cp36 is CRITICAL: connect to address localhost and port 8205: Connection refused [04:35:12] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 38.46.223.205/cpweb, 2602:294:0:b13::110/cpweb [04:35:13] PROBLEM - cp36 Nginx Backend for mwtask171 on cp36 is CRITICAL: connect to address localhost and port 8161: Connection refused [04:35:13] 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 [04:35:16] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 2 datacenters are down: 38.46.223.205/cpweb, 2602:294:0:b13::110/cpweb [04:35:18] PROBLEM - cp36 Nginx Backend for mw153 on cp36 is CRITICAL: connect to address localhost and port 8121: Connection refused [04:35:26] PROBLEM - cp36 Nginx Backend for test151 on cp36 is CRITICAL: connect to address localhost and port 8181: Connection refused [04:35:26] PROBLEM - cp36 Nginx Backend for matomo151 on cp36 is CRITICAL: connect to address localhost and port 8203: Connection refused [04:35:26] PROBLEM - mwtask151 Current Load on mwtask151 is WARNING: LOAD WARNING - total load average: 21.65, 14.72, 6.83 [04:35:26] PROBLEM - cp36 Nginx Backend for mw171 on cp36 is CRITICAL: connect to address localhost and port 8117: Connection refused [04:35:31] PROBLEM - cp36 Nginx Backend for mw183 on cp36 is CRITICAL: connect to address localhost and port 8127: Connection refused [04:35:32] Oh for fuck sake [04:35:33] PROBLEM - darkwaterswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address darkwaterswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:38] PROBLEM - metroidpedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address metroidpedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:35:43] PROBLEM - johanloopmans.nl - LetsEncrypt on sslhost is CRITICAL: connect to address johanloopmans.nl and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:00] PROBLEM - yepedia.xyz - LetsEncrypt on sslhost is CRITICAL: connect to address yepedia.xyz and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:00] PROBLEM - persist.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address persist.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:03] PROBLEM - edapedia.net - LetsEncrypt on sslhost is CRITICAL: connect to address edapedia.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:04] PROBLEM - aryavartpedia.online - LetsEncrypt on sslhost is CRITICAL: connect to address aryavartpedia.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:04] 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 [04:36:04] PROBLEM - nonciclopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address nonciclopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:36:46] PROBLEM - ssbuniverses.com - LetsEncrypt on sslhost is CRITICAL: connect to address ssbuniverses.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:37:23] PROBLEM - partopedia.ru - LetsEncrypt on sslhost is CRITICAL: connect to address partopedia.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:37:42] PROBLEM - rodzinka.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rodzinka.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:37:44] PROBLEM - spiceandwolf.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address spiceandwolf.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:06] PROBLEM - crashspyrowiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address crashspyrowiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:13] PROBLEM - worldsanskrit.net - LetsEncrypt on sslhost is CRITICAL: connect to address worldsanskrit.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:13] PROBLEM - rippaversewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rippaversewiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:24] PROBLEM - hololive.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hololive.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:24] PROBLEM - echoes-wiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address echoes-wiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:28] PROBLEM - maxcapacity.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address maxcapacity.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:32] PROBLEM - annapolishistorywiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address annapolishistorywiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:37] PROBLEM - permanentfuturelab.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address permanentfuturelab.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:54] PROBLEM - comprehensibleinputwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address comprehensibleinputwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:38:59] PROBLEM - decimatedrive.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address decimatedrive.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:39:03] PROBLEM - osdev.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address osdev.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:39:05] PROBLEM - dccomicswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address dccomicswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:39:13] PROBLEM - pokemonwiki.info - LetsEncrypt on sslhost is CRITICAL: connect to address pokemonwiki.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:39:19] PROBLEM - apeirology.com - LetsEncrypt on sslhost is CRITICAL: connect to address apeirology.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:39:19] PROBLEM - dragdown.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address dragdown.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:21] PROBLEM - rct.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rct.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:21] PROBLEM - vesc.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vesc.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:21] PROBLEM - squareenixwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address squareenixwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:32] PROBLEM - geeu.org - LetsEncrypt on sslhost is CRITICAL: connect to address geeu.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:42] PROBLEM - neurologiahpm.com - LetsEncrypt on sslhost is CRITICAL: connect to address neurologiahpm.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:40:42] PROBLEM - pyramidgames.wiki - Cloudflare on sslhost is CRITICAL: connect to address pyramidgames.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:02] PROBLEM - phighting.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address phighting.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:04] PROBLEM - puzzles.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address puzzles.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:27] PROBLEM - kingdomdeath.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kingdomdeath.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:27] PROBLEM - encyclopediarobotica.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediarobotica.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:34] PROBLEM - rarewarewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rarewarewiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:35] PROBLEM - trollpasta.com - LetsEncrypt on sslhost is CRITICAL: connect to address trollpasta.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:41:37] PROBLEM - binrayarchives.com - LetsEncrypt on sslhost is CRITICAL: connect to address binrayarchives.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:42:48] PROBLEM - kagaga.jp - LetsEncrypt on sslhost is CRITICAL: connect to address kagaga.jp and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:07] PROBLEM - vylet.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vylet.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:07] PROBLEM - terraforming.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address terraforming.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:09] PROBLEM - fairytail.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fairytail.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:18] PROBLEM - bristolstudenthousingcoop.org - LetsEncrypt on sslhost is CRITICAL: connect to address bristolstudenthousingcoop.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:19] PROBLEM - mariopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address mariopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:19] PROBLEM - clubpenguinfanon.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address clubpenguinfanon.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:32] PROBLEM - voecwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address voecwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:42] PROBLEM - fnafmw.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fnafmw.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:42] PROBLEM - hardcore.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hardcore.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:43:54] PROBLEM - gimkit.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address gimkit.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:12] PROBLEM - wikimoma.art - LetsEncrypt on sslhost is CRITICAL: connect to address wikimoma.art and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:13] PROBLEM - podpedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address podpedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:13] PROBLEM - hellowhirled.org - LetsEncrypt on sslhost is CRITICAL: connect to address hellowhirled.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:21] PROBLEM - sdiy.info - LetsEncrypt on sslhost is CRITICAL: connect to address sdiy.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:48] PROBLEM - beyondtheveilrp.com - LetsEncrypt on sslhost is CRITICAL: connect to address beyondtheveilrp.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:48] PROBLEM - worldtriggerwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address worldtriggerwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:50] PROBLEM - grayzonewarfare.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address grayzonewarfare.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:44:50] PROBLEM - rainverse.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rainverse.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:45:15] PROBLEM - lotrmc.ru - LetsEncrypt on sslhost is CRITICAL: connect to address lotrmc.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:45:53] PROBLEM - yokaiwatchwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address yokaiwatchwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:46:12] PROBLEM - ff8.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address ff8.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:46:12] PROBLEM - theenglishlakes.uk - LetsEncrypt on sslhost is CRITICAL: connect to address theenglishlakes.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:46:29] PROBLEM - mappingwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address mappingwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:46:48] PROBLEM - wikappedia.cc - LetsEncrypt on sslhost is CRITICAL: connect to address wikappedia.cc and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:09] PROBLEM - landofliberos.com - LetsEncrypt on sslhost is CRITICAL: connect to address landofliberos.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:10] PROBLEM - hoseki.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hoseki.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:26] RECOVERY - mwtask151 Current Load on mwtask151 is OK: LOAD OK - total load average: 5.88, 16.31, 13.37 [04:47:35] PROBLEM - corru.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address corru.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:47] PROBLEM - mockgovernments.com - LetsEncrypt on sslhost is CRITICAL: connect to address mockgovernments.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:49] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: connect to address thelonsdalebattalion.co.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:52] PROBLEM - poupedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address poupedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:47:55] PROBLEM - vilexia.com - LetsEncrypt on sslhost is CRITICAL: connect to address vilexia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:48:37] PROBLEM - lotr.su - LetsEncrypt on sslhost is CRITICAL: connect to address lotr.su and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [04:48:57] RECOVERY - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is OK: OK - NGINX Error Rate is 24% [04:48:57] RECOVERY - cp36 Nginx Backend for mw162 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8116 [04:48:57] RECOVERY - cp36 Nginx Backend for mw182 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8120 [04:48:58] RECOVERY - cp36 Nginx Backend for mw151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8113 [04:48:58] RECOVERY - cp36 Nginx Backend for mw172 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8118 [04:49:04] RECOVERY - cp36 Nginx Backend for mon181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8201 [04:49:08] RECOVERY - cp36 Nginx Backend for reports171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8205 [04:49:11] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [04:49:13] RECOVERY - cp36 Nginx Backend for mwtask171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8161 [04:49:16] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [04:49:18] RECOVERY - cp36 Nginx Backend for mw153 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8121 [04:49:26] RECOVERY - cp36 Nginx Backend for test151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8181 [04:49:26] RECOVERY - cp36 Nginx Backend for matomo151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8203 [04:49:26] RECOVERY - cp36 Nginx Backend for mw171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8117 [04:49:30] RECOVERY - cp36 Nginx Backend for mw183 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8127 [04:49:38] RECOVERY - cp36 Nginx Backend for swiftproxy171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8207 [04:49:50] RECOVERY - cp36 Nginx Backend for mwtask161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8163 [04:49:50] RECOVERY - cp36 Nginx Backend for mwtask151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8162 [04:49:51] RECOVERY - cp36 Nginx Backend for mwtask181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8160 [04:49:54] RECOVERY - cp36 Nginx Backend for phorge171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8202 [04:49:56] RECOVERY - cp36 Nginx Backend for puppet181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8204 [04:49:58] RECOVERY - cp36 Nginx Backend for mw163 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8123 [04:50:01] RECOVERY - cp36 Nginx Backend for mw161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8115 [04:50:10] RECOVERY - cp36 Nginx Backend for mw184 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8128 [04:50:13] RECOVERY - cp36 Nginx Backend for mw181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8119 [04:50:25] RECOVERY - cp36 Nginx Backend for mw154 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8122 [04:50:30] RECOVERY - cp36 Nginx Backend for mw174 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8126 [04:50:31] RECOVERY - cp36 Nginx Backend for swiftproxy161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8206 [04:50:32] RECOVERY - cp36 Nginx Backend for mw164 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8124 [04:50:35] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4114 bytes in 0.054 second response time [04:50:35] RECOVERY - cp36 Nginx Backend for mw173 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8125 [04:50:37] RECOVERY - cp36 Nginx Backend for mw152 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8114 [04:51:13] RECOVERY - cp36 Varnish Backends on cp36 is OK: All 29 backends are healthy [04:54:03] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 16%, RTA = 31.44 ms [04:58:06] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.35 ms [05:02:28] RECOVERY - pso2ngs.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'pso2ngs.wiki' will expire on Thu 03 Apr 2025 10:53:33 AM GMT +0000. [05:02:28] RECOVERY - allthetropes.org - LetsEncrypt on sslhost is OK: OK - Certificate 'allthetropes.org' will expire on Thu 06 Mar 2025 08:38:36 PM GMT +0000. [05:02:48] RECOVERY - knifepointhorror.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'knifepointhorror.wiki' will expire on Sat 08 Mar 2025 11:30:15 PM GMT +0000. [05:02:51] RECOVERY - ecole.science - LetsEncrypt on sslhost is OK: OK - Certificate 'ecole.science' will expire on Sat 08 Mar 2025 12:02:35 AM GMT +0000. [05:03:07] 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. [05:03:08] RECOVERY - burnout.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'burnout.wiki' will expire on Tue 18 Mar 2025 03:16:41 PM GMT +0000. [05:03:18] RECOVERY - emmytherobot.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'emmytherobot.wiki' will expire on Sun 30 Mar 2025 12:33:00 PM GMT +0000. [05:03:20] RECOVERY - baligawiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'baligawiki.org' will expire on Fri 04 Apr 2025 06:57:58 PM GMT +0000. [05:03:20] RECOVERY - holocron.net - LetsEncrypt on sslhost is OK: OK - Certificate 'holocron.net' will expire on Sat 10 May 2025 02:45:38 AM GMT +0000. [05:03:33] 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. [05:03:33] RECOVERY - project-patterns.com - LetsEncrypt on sslhost is OK: OK - Certificate 'project-patterns.com' will expire on Tue 22 Apr 2025 01:04:41 AM GMT +0000. [05:03:33] RECOVERY - mh142.com - LetsEncrypt on sslhost is OK: OK - Certificate 'mh142.com' will expire on Fri 07 Mar 2025 07:39:12 AM GMT +0000. [05:03:33] RECOVERY - osrwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'osrwiki.org' will expire on Mon 07 Apr 2025 07:37:52 PM GMT +0000. [05:03:35] RECOVERY - exmormon.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'exmormon.wiki' will expire on Thu 24 Apr 2025 01:56:43 PM GMT +0000. [05:03:35] 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. [05:03:41] 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. [05:03:48] RECOVERY - ourlifewiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'ourlifewiki.org' will expire on Fri 11 Apr 2025 05:41:16 PM GMT +0000. [05:04:14] RECOVERY - z1r.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'z1r.wiki' will expire on Tue 18 Mar 2025 02:46:25 AM GMT +0000. [05:04:36] RECOVERY - darkwaterswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'darkwaterswiki.com' will expire on Mon 24 Mar 2025 03:09:45 PM GMT +0000. [05:04:47] 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. [05:04:57] RECOVERY - johanloopmans.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'johanloopmans.nl' will expire on Tue 08 Apr 2025 10:23:34 PM GMT +0000. [05:05:29] 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. [05:05:29] RECOVERY - yepedia.xyz - LetsEncrypt on sslhost is OK: OK - Certificate 'yepedia.xyz' will expire on Thu 24 Apr 2025 02:10:34 PM GMT +0000. [05:05:33] RECOVERY - ssbuniverses.com - LetsEncrypt on sslhost is OK: OK - Certificate 'ssbuniverses.com' will expire on Mon 10 Mar 2025 06:31:05 PM GMT +0000. [05:05:37] RECOVERY - edapedia.net - LetsEncrypt on sslhost is OK: OK - Certificate 'edapedia.net' will expire on Mon 07 Apr 2025 01:52:00 AM GMT +0000. [05:05:37] RECOVERY - aryavartpedia.online - LetsEncrypt on sslhost is OK: OK - Certificate 'aryavartpedia.online' will expire on Fri 04 Apr 2025 11:24:02 PM GMT +0000. [05:05:38] RECOVERY - issue-tracker.wikitide.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.org' will expire on Sat 12 Apr 2025 07:36:30 PM GMT +0000. [05:05:38] RECOVERY - nonciclopedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'nonciclopedia.org' will expire on Fri 07 Mar 2025 06:52:20 AM GMT +0000. [05:06:42] RECOVERY - crashspyrowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'crashspyrowiki.com' will expire on Sun 09 Mar 2025 03:37:17 PM GMT +0000. [05:06:56] RECOVERY - rippaversewiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'rippaversewiki.com' will expire on Sun 30 Mar 2025 12:37:22 PM GMT +0000. [05:06:57] RECOVERY - worldsanskrit.net - LetsEncrypt on sslhost is OK: OK - Certificate 'worldsanskrit.net' will expire on Fri 14 Mar 2025 02:35:17 PM GMT +0000. [05:07:09] RECOVERY - partopedia.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'partopedia.ru' will expire on Wed 07 May 2025 07:48:43 PM GMT +0000. [05:07:17] 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. [05:07:17] RECOVERY - echoes-wiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'echoes-wiki.com' will expire on Thu 20 Mar 2025 04:41:07 PM GMT +0000. [05:07:23] RECOVERY - rodzinka.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'rodzinka.wiki' will expire on Mon 28 Apr 2025 07:14:12 PM GMT +0000. [05:07:26] RECOVERY - maxcapacity.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'maxcapacity.wiki' will expire on Sun 04 May 2025 02:42:43 PM GMT +0000. [05:07:28] RECOVERY - spiceandwolf.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'spiceandwolf.wiki' will expire on Mon 21 Apr 2025 02:41:45 AM GMT +0000. [05:07:33] RECOVERY - annapolishistorywiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'annapolishistorywiki.org' will expire on Fri 18 Apr 2025 08:26:48 AM GMT +0000. [05:07:43] RECOVERY - permanentfuturelab.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'permanentfuturelab.wiki' will expire on Tue 18 Mar 2025 03:37:16 PM GMT +0000. [05:08:19] RECOVERY - comprehensibleinputwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'comprehensibleinputwiki.org' will expire on Sun 27 Apr 2025 01:44:26 PM GMT +0000. [05:08:36] RECOVERY - osdev.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'osdev.wiki' will expire on Wed 23 Apr 2025 09:23:35 PM GMT +0000. [05:08:40] RECOVERY - decimatedrive.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'decimatedrive.wiki' will expire on Fri 21 Mar 2025 09:50:10 PM GMT +0000. [05:08:55] RECOVERY - pokemonwiki.info - LetsEncrypt on sslhost is OK: OK - Certificate 'pokemonwiki.info' will expire on Tue 18 Mar 2025 03:39:57 PM GMT +0000. [05:09:05] PROBLEM - dccomicswiki.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'dccomicswiki.com' expires in 12 day(s) (Fri 28 Feb 2025 11:41:34 PM GMT +0000). [05:09:08] RECOVERY - dragdown.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'dragdown.wiki' will expire on Mon 17 Mar 2025 03:23:49 PM GMT +0000. [05:09:09] 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. [05:09:34] RECOVERY - phighting.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'phighting.wiki' will expire on Sun 30 Mar 2025 06:24:57 PM GMT +0000. [05:09:38] RECOVERY - puzzles.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'puzzles.wiki' will expire on Tue 08 Apr 2025 10:21:57 PM GMT +0000. [05:09:41] 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. [05:09:41] 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. [05:09:41] 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. [05:10:04] RECOVERY - geeu.org - LetsEncrypt on sslhost is OK: OK - Certificate 'geeu.org' will expire on Sun 27 Apr 2025 02:05:19 PM GMT +0000. [05:10:24] 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. [05:10:24] RECOVERY - encyclopediarobotica.org - LetsEncrypt on sslhost is OK: OK - Certificate 'encyclopediarobotica.org' will expire on Fri 25 Apr 2025 02:16:23 PM GMT +0000. [05:10:24] RECOVERY - pyramidgames.wiki - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [05:10:25] RECOVERY - neurologiahpm.com - LetsEncrypt on sslhost is OK: OK - Certificate 'neurologiahpm.com' will expire on Sun 11 May 2025 11:05:08 AM GMT +0000. [05:10:37] 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. [05:10:39] RECOVERY - trollpasta.com - LetsEncrypt on sslhost is OK: OK - Certificate 'trollpasta.com' will expire on Tue 18 Mar 2025 03:42:24 PM GMT +0000. [05:10:43] RECOVERY - binrayarchives.com - LetsEncrypt on sslhost is OK: OK - Certificate 'binrayarchives.com' will expire on Fri 25 Apr 2025 09:14:14 PM GMT +0000. [05:11:35] RECOVERY - kagaga.jp - LetsEncrypt on sslhost is OK: OK - Certificate 'kagaga.jp' will expire on Thu 20 Mar 2025 04:51:28 PM GMT +0000. [05:12:13] RECOVERY - terraforming.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'terraforming.wiki' will expire on Wed 07 May 2025 06:27:23 PM GMT +0000. [05:12:13] RECOVERY - vylet.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'vylet.wiki' will expire on Tue 22 Apr 2025 02:04:34 AM GMT +0000. [05:12:18] RECOVERY - fairytail.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'fairytail.wiki' will expire on Thu 20 Mar 2025 09:03:07 PM GMT +0000. [05:12:37] RECOVERY - clubpenguinfanon.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'clubpenguinfanon.wiki' will expire on Tue 25 Mar 2025 11:01:22 PM GMT +0000. [05:12:37] RECOVERY - bristolstudenthousingcoop.org - LetsEncrypt on sslhost is OK: OK - Certificate 'bristolstudenthousingcoop.org' will expire on Fri 07 Mar 2025 10:39:11 AM GMT +0000. [05:12:37] RECOVERY - mariopedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'mariopedia.org' will expire on Sat 08 Mar 2025 10:39:11 PM GMT +0000. [05:12:55] RECOVERY - hellowhirled.org - LetsEncrypt on sslhost is OK: OK - Certificate 'hellowhirled.org' will expire on Sun 30 Mar 2025 04:36:12 PM GMT +0000. [05:12:55] 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. [05:12:55] 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. [05:13:03] RECOVERY - voecwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'voecwiki.com' will expire on Tue 25 Mar 2025 12:53:32 AM GMT +0000. [05:13:12] RECOVERY - sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Fri 16 May 2025 02:15:56 PM GMT +0000. [05:13:23] RECOVERY - fnafmw.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'fnafmw.wiki' will expire on Thu 15 May 2025 11:15:17 PM GMT +0000. [05:13:23] RECOVERY - hardcore.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'hardcore.wiki' will expire on Fri 09 May 2025 07:38:37 PM GMT +0000. [05:13:47] RECOVERY - gimkit.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'gimkit.wiki' will expire on Wed 05 Mar 2025 02:35:49 PM GMT +0000. [05:14:06] RECOVERY - beyondtheveilrp.com - LetsEncrypt on sslhost is OK: OK - Certificate 'beyondtheveilrp.com' will expire on Wed 07 May 2025 06:56:31 PM GMT +0000. [05:14:06] RECOVERY - worldtriggerwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'worldtriggerwiki.com' will expire on Sun 16 Mar 2025 12:03:12 AM GMT +0000. [05:14:11] RECOVERY - rainverse.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'rainverse.wiki' will expire on Mon 21 Apr 2025 12:52:28 AM GMT +0000. [05:14:31] RECOVERY - grayzonewarfare.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'grayzonewarfare.wiki' will expire on Mon 07 Apr 2025 07:26:26 PM GMT +0000. [05:14:46] RECOVERY - yokaiwatchwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'yokaiwatchwiki.com' will expire on Fri 14 Mar 2025 02:31:09 PM GMT +0000. [05:15:00] RECOVERY - lotrmc.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'lotrmc.ru' will expire on Fri 18 Apr 2025 04:19:35 PM GMT +0000. [05:15:24] RECOVERY - ff8.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'ff8.wiki' will expire on Thu 01 May 2025 12:35:59 AM GMT +0000. [05:15:24] RECOVERY - theenglishlakes.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'theenglishlakes.uk' will expire on Thu 17 Apr 2025 05:44:53 PM GMT +0000. [05:15:49] RECOVERY - landofliberos.com - LetsEncrypt on sslhost is OK: OK - Certificate 'landofliberos.com' will expire on Sun 09 Mar 2025 08:42:53 AM GMT +0000. [05:15:49] RECOVERY - hoseki.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'hoseki.wiki' will expire on Sat 08 Mar 2025 01:09:01 PM GMT +0000. [05:15:58] RECOVERY - mappingwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'mappingwiki.org' will expire on Mon 12 May 2025 09:09:10 PM GMT +0000. [05:16:29] RECOVERY - wikappedia.cc - LetsEncrypt on sslhost is OK: OK - Certificate 'wikappedia.cc' will expire on Sun 23 Mar 2025 01:58:38 PM GMT +0000. [05:17:04] RECOVERY - mockgovernments.com - LetsEncrypt on sslhost is OK: OK - Certificate 'mockgovernments.com' will expire on Tue 01 Apr 2025 05:55:36 PM GMT +0000. [05:17:09] RECOVERY - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thelonsdalebattalion.co.uk' will expire on Thu 06 Mar 2025 09:28:33 PM GMT +0000. [05:17:14] 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. [05:17:15] RECOVERY - poupedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'poupedia.com' will expire on Mon 28 Apr 2025 01:12:42 PM GMT +0000. [05:17:15] RECOVERY - corru.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'corru.wiki' will expire on Mon 07 Apr 2025 02:27:02 AM GMT +0000. [05:17:19] RECOVERY - vilexia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'vilexia.com' will expire on Thu 01 May 2025 05:08:25 PM GMT +0000. [05:56:10] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [05:58:08] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.33 ms [06:06:42] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 60%, RTA = 31.34 ms [06:10:45] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.37 ms [06:29:22] [02mw-config] 07winstonsung opened pull request #5828: Fix "Re-apply T12526: Add redundent langs to DisabledLanguages on meta (#5823)" (07miraheze:03master...07winstonsung:03dev-5828) 13https://github.com/miraheze/mw-config/pull/5828 [06:30:21] miraheze/mw-config - winstonsung the build passed. [06:53:26] PROBLEM - mwtask151 Current Load on mwtask151 is WARNING: LOAD WARNING - total load average: 21.68, 14.97, 7.33 [06:55:26] RECOVERY - mwtask151 Current Load on mwtask151 is OK: LOAD OK - total load average: 9.94, 13.89, 7.93 [07:12:02] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [07:14:01] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.37 ms [07:18:20] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 80%, RTA = 31.41 ms [07:22:23] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.40 ms [07:26:43] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 60%, RTA = 31.39 ms [07:30:46] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.90 ms [08:07:27] PROBLEM - matomo151 HTTPS on matomo151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to matomo151.wikitide.net port 443 after 0 ms: Couldn't connect to server [08:21:37] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is WARNING: WARNING - NGINX Error Rate is 43% [08:23:34] RECOVERY - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is OK: OK - NGINX Error Rate is 39% [08:25:28] RECOVERY - matomo151 HTTPS on matomo151 is OK: HTTP OK: HTTP/2 200 - 553 bytes in 1.206 second response time [08:53:34] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 22.37, 16.60, 9.19 [08:59:34] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 12.89, 18.53, 12.79 [09:44:28] PROBLEM - cp36 Current Load on cp36 is CRITICAL: LOAD CRITICAL - total load average: 56.06, 110.50, 53.01 [09:56:09] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 44%, RTA = 31.35 ms [09:57:48] PROBLEM - wiki.10key.plus - Cloudflare on sslhost is CRITICAL: No address associated with hostnameHTTP CRITICAL - Unable to open TCP socket [10:00:13] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.34 ms [10:03:26] PROBLEM - mwtask151 Current Load on mwtask151 is CRITICAL: LOAD CRITICAL - total load average: 24.37, 15.62, 7.04 [10:09:26] RECOVERY - mwtask151 Current Load on mwtask151 is OK: LOAD OK - total load average: 14.06, 19.70, 12.07 [10:10:28] PROBLEM - cp36 Current Load on cp36 is WARNING: LOAD WARNING - total load average: 3.02, 2.88, 11.33 [10:14:28] RECOVERY - cp36 Current Load on cp36 is OK: LOAD OK - total load average: 1.43, 2.28, 9.17 [10:56:11] PROBLEM - mwtask171 Current Load on mwtask171 is CRITICAL: LOAD CRITICAL - total load average: 24.80, 15.75, 7.99 [10:57:17] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [11:03:25] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.35 ms [11:04:11] RECOVERY - mwtask171 Current Load on mwtask171 is OK: LOAD OK - total load average: 8.48, 18.51, 13.30 [11:07:47] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [11:11:50] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.36 ms [11:39:59] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [11:41:58] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.32 ms [11:50:30] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 50%, RTA = 32.05 ms [11:52:29] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.43 ms [12:12:17] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 18.42, 12.43, 6.12 [12:14:17] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 4.30, 9.00, 5.62 [12:22:17] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 19.40, 11.86, 7.62 [12:28:51] PROBLEM - cp37 Disk Space on cp37 is CRITICAL: DISK CRITICAL - free space: / 27219MiB (5% inode=99%); [12:39:05] PROBLEM - dccomicswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address dccomicswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:39:56] 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 [12:40:38] 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 [12:40:57] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is CRITICAL: CRITICAL - NGINX Error Rate is 92% [12:40:57] PROBLEM - cp36 Nginx Backend for mw162 on cp36 is CRITICAL: connect to address localhost and port 8116: Connection refused [12:40:57] PROBLEM - cp36 Nginx Backend for mw182 on cp36 is CRITICAL: connect to address localhost and port 8120: Connection refused [12:40:58] PROBLEM - cp36 Nginx Backend for mw151 on cp36 is CRITICAL: connect to address localhost and port 8113: Connection refused [12:40:58] PROBLEM - cp36 Nginx Backend for mw172 on cp36 is CRITICAL: connect to address localhost and port 8118: Connection refused [12:41:02] PROBLEM - phighting.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address phighting.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:04] PROBLEM - cp36 Nginx Backend for mon181 on cp36 is CRITICAL: connect to address localhost and port 8201: Connection refused [12:41:04] PROBLEM - puzzles.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address puzzles.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:08] PROBLEM - cp36 Nginx Backend for reports171 on cp36 is CRITICAL: connect to address localhost and port 8205: Connection refused [12:41:12] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 38.46.223.205/cpweb, 2602:294:0:b13::110/cpweb [12:41:13] PROBLEM - cp36 Nginx Backend for mwtask171 on cp36 is CRITICAL: connect to address localhost and port 8161: Connection refused [12:41:17] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 2 datacenters are down: 38.46.223.205/cpweb, 2602:294:0:b13::110/cpweb [12:41:18] PROBLEM - cp36 Nginx Backend for mw153 on cp36 is CRITICAL: connect to address localhost and port 8121: Connection refused [12:41:25] PROBLEM - cp36 Nginx Backend for test151 on cp36 is CRITICAL: connect to address localhost and port 8181: Connection refused [12:41:26] PROBLEM - cp36 Nginx Backend for matomo151 on cp36 is CRITICAL: connect to address localhost and port 8203: Connection refused [12:41:26] PROBLEM - cp36 Nginx Backend for mw171 on cp36 is CRITICAL: connect to address localhost and port 8117: Connection refused [12:41:27] PROBLEM - kingdomdeath.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kingdomdeath.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:27] PROBLEM - encyclopediarobotica.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediarobotica.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:30] PROBLEM - cp36 Nginx Backend for mw183 on cp36 is CRITICAL: connect to address localhost and port 8127: Connection refused [12:41:34] PROBLEM - rarewarewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rarewarewiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:34] PROBLEM - trollpasta.com - LetsEncrypt on sslhost is CRITICAL: connect to address trollpasta.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:37] PROBLEM - binrayarchives.com - LetsEncrypt on sslhost is CRITICAL: connect to address binrayarchives.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:38] PROBLEM - cp36 Nginx Backend for swiftproxy171 on cp36 is CRITICAL: connect to address localhost and port 8207: Connection refused [12:41:48] PROBLEM - grayzonewarfare.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address grayzonewarfare.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:41:50] PROBLEM - cp36 Nginx Backend for mwtask161 on cp36 is CRITICAL: connect to address localhost and port 8163: Connection refused [12:41:50] PROBLEM - cp36 Nginx Backend for mwtask151 on cp36 is CRITICAL: connect to address localhost and port 8162: Connection refused [12:41:51] PROBLEM - cp36 Nginx Backend for mwtask181 on cp36 is CRITICAL: connect to address localhost and port 8160: Connection refused [12:41:54] PROBLEM - cp36 Nginx Backend for phorge171 on cp36 is CRITICAL: connect to address localhost and port 8202: Connection refused [12:41:56] PROBLEM - cp36 Nginx Backend for puppet181 on cp36 is CRITICAL: connect to address localhost and port 8204: Connection refused [12:41:58] PROBLEM - cp36 Nginx Backend for mw163 on cp36 is CRITICAL: connect to address localhost and port 8123: Connection refused [12:41:58] aaaaaaaaaaaaaaa [12:42:01] PROBLEM - cp36 Nginx Backend for mw161 on cp36 is CRITICAL: connect to address localhost and port 8115: Connection refused [12:42:02] the apocalypse [12:42:10] it jsut happens y'know [12:42:10] PROBLEM - cp36 Nginx Backend for mw184 on cp36 is CRITICAL: connect to address localhost and port 8128: Connection refused [12:42:13] PROBLEM - cp36 Nginx Backend for mw181 on cp36 is CRITICAL: connect to address localhost and port 8119: Connection refused [12:42:17] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 5.25, 8.95, 11.27 [12:42:25] PROBLEM - cp36 Nginx Backend for mw154 on cp36 is CRITICAL: connect to address localhost and port 8122: Connection refused [12:42:30] PROBLEM - cp36 Nginx Backend for mw174 on cp36 is CRITICAL: connect to address localhost and port 8126: Connection refused [12:42:31] PROBLEM - cp36 Nginx Backend for swiftproxy161 on cp36 is CRITICAL: connect to address localhost and port 8206: Connection refused [12:42:32] PROBLEM - cp36 Nginx Backend for mw164 on cp36 is CRITICAL: connect to address localhost and port 8124: Connection refused [12:42:35] PROBLEM - cp36 Nginx Backend for mw173 on cp36 is CRITICAL: connect to address localhost and port 8125: Connection refused [12:42:37] PROBLEM - cp36 Nginx Backend for mw152 on cp36 is CRITICAL: connect to address localhost and port 8114: Connection refused [12:42:47] I just didn't know the apocalypse would be upon us so soon, I didn't prepare [12:42:48] PROBLEM - kagaga.jp - LetsEncrypt on sslhost is CRITICAL: connect to address kagaga.jp and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:42:59] it happened earlier today btw [12:43:07] PROBLEM - vylet.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vylet.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:07] PROBLEM - terraforming.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address terraforming.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:09] PROBLEM - fairytail.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fairytail.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:17] Oh, I were asleep [12:43:19] PROBLEM - bristolstudenthousingcoop.org - LetsEncrypt on sslhost is CRITICAL: connect to address bristolstudenthousingcoop.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket PROBLEM - clubpenguinfanon.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address clubpenguinfanon.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:19] PROBLEM - mariopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address mariopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:32] PROBLEM - voecwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address voecwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:42] PROBLEM - fnafmw.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fnafmw.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:42] PROBLEM - hardcore.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hardcore.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:43:44] guess surviving two apocalypses per day is not a terrible score [12:43:58] fair enough ^_^ [12:44:01] RECOVERY - cp36 Nginx Backend for mw161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8115 [12:44:10] RECOVERY - cp36 Nginx Backend for mw184 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8128 [12:44:13] RECOVERY - cp36 Nginx Backend for mw181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8119 [12:44:25] RECOVERY - cp36 Nginx Backend for mw154 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8122 [12:44:30] RECOVERY - cp36 Nginx Backend for mw174 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8126 [12:44:31] RECOVERY - cp36 Nginx Backend for swiftproxy161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8206 [12:44:32] RECOVERY - cp36 Nginx Backend for mw164 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8124 [12:44:35] RECOVERY - cp36 Nginx Backend for mw173 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8125 [12:44:35] RECOVERY - cp36 HTTPS on cp36 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4114 bytes in 0.273 second response time [12:44:37] RECOVERY - cp36 Nginx Backend for mw152 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8114 [12:44:57] RECOVERY - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is OK: OK - NGINX Error Rate is 6% [12:44:57]