[00:02:29] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:53] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:02:55] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:07] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:11] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:17] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:23] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:27] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:35] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:37] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:55] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:59] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:03] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:13] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:04:15] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:10:56] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [00:11:06] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3403 [00:11:08] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [00:11:12] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [00:11:28] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [00:11:36] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [00:11:56] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [00:12:00] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:04] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [00:12:14] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:16] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:30] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:54] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:13:18] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:13:24] RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [00:13:33] !log deleted maiascwiki in line with Content Policy [00:13:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [00:15:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbi5 [00:15:13] [02miraheze/services] 07MirahezeSSLBot 03dccaac7 - BOT: Updating services config for wikis [00:42:33] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbPA [00:42:35] [02miraheze/mw-config] 07paladox 03b6a4010 - Fix path to Poll sql file [00:48:47] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbXt [00:48:48] [02miraheze/puppet] 07paladox 03ca92f0f - Update php.pp [00:50:45] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpbXY [00:50:47] [02miraheze/puppet] 07paladox 038ccab86 - Set fpm error_log [00:50:48] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [00:50:50] [02puppet] 07paladox opened pull request 03#932: Set fpm error_log - 13https://git.io/fpbXO [00:51:27] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpbXZ [00:51:29] [02miraheze/puppet] 07paladox 03c85fb34 - Update php_fpm.pp [00:51:30] [02puppet] 07paladox synchronize pull request 03#932: Set fpm error_log - 13https://git.io/fpbXO [00:51:42] [02puppet] 07paladox closed pull request 03#932: Set fpm error_log - 13https://git.io/fpbXO [00:51:43] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fpbXC [00:51:45] [02miraheze/puppet] 07paladox 035641fff - Set fpm error_log (#932) * Set fpm error_log * Update php_fpm.pp [00:51:46] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [00:51:48] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [00:57:19] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [00:57:21] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpbXV [00:57:22] [02miraheze/puppet] 07paladox 0383cd52c - Set php error_log config [00:57:23] [02puppet] 07paladox opened pull request 03#933: Set php error_log config - 13https://git.io/fpbXw [01:00:55] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+1/-0/±0] 13https://git.io/fpbXP [01:00:56] [02miraheze/puppet] 07paladox 0323d8c08 - Create php-fpm-logrotate.conf [01:00:58] [02puppet] 07paladox synchronize pull request 03#933: Set php error_log config - 13https://git.io/fpbXw [01:04:00] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpbXQ [01:04:02] [02miraheze/puppet] 07paladox 034959383 - Update php_fpm.pp [01:04:03] [02puppet] 07paladox synchronize pull request 03#933: Set php error_log config - 13https://git.io/fpbXw [01:05:13] [02puppet] 07paladox closed pull request 03#933: Set php error_log config - 13https://git.io/fpbXw [01:05:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fpbXF [01:05:16] [02miraheze/puppet] 07paladox 031c0ee0a - Set php error_log config (#933) [01:05:18] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [01:05:19] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [01:12:18] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-1/±2] 13https://git.io/fpb1Z [01:12:19] [02miraheze/puppet] 07paladox 032e1666b - Migrate icingaweb2/grafana to the new php module [01:15:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fpb14 [01:15:16] [02miraheze/puppet] 07paladox 0375a40ac - migrate roundcubemail to the new php module [01:15:18] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [01:24:12] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fpb1Q [01:24:13] [02miraheze/puppet] 07paladox 03a381614 - fix loading php::php_fpm [01:25:18] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:26:41] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fpb1x [01:26:42] [02miraheze/puppet] 07paladox 033089c3d - icingaweb2/grafana/roundcubemail fix location of php sock [01:27:38] PROBLEM - misc1 webmail.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway [01:32:03] PROBLEM - misc1 icinga.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 309 bytes in 0.016 second response time [01:33:31] RECOVERY - misc1 icinga.miraheze.org HTTPS on misc1 is OK: HTTP OK: HTTP/1.1 302 Found - 347 bytes in 0.008 second response time [01:33:35] RECOVERY - misc1 webmail.miraheze.org HTTPS on misc1 is OK: HTTP OK: Status line output matched "HTTP/1.1 401 Unauthorized" - 5681 bytes in 0.122 second response time [01:37:27] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-2/±2] 13https://git.io/fpbM4 [01:37:29] [02miraheze/puppet] 07paladox 03ec0133a - matomo: Migrate to the new php module [01:51:04] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbM7 [01:51:05] [02miraheze/puppet] 07paladox 0316bc844 - Update pool.pp [02:04:19] PROBLEM - misc1 webmail.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Internal Server Error [02:04:34] PROBLEM - misc2 HTTPS on misc2 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 480 bytes in 0.039 second response time [02:06:20] uh [02:09:46] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fpbDG [02:09:48] [02miraheze/puppet] 07paladox 031fad758 - Fix path to php error log [02:13:19] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:47:19] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [02:51:39] RECOVERY - misc1 webmail.miraheze.org HTTPS on misc1 is OK: HTTP OK: Status line output matched "HTTP/1.1 401 Unauthorized" - 5681 bytes in 0.127 second response time [02:54:33] RECOVERY - misc2 HTTPS on misc2 is OK: HTTP OK: HTTP/1.1 200 OK - 44907 bytes in 0.115 second response time [02:55:17] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [03:02:10] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+24/-24/±26] 13https://git.io/fpbyz [03:02:11] [02miraheze/puppet] 07paladox 03f8d2113 - Rename mlib to vmlib [03:04:16] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbyw [03:04:17] [02miraheze/puppet] 07paladox 038617b8c - Update init.pp [03:07:18] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:09:38] PROBLEM - misc1 webmail.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway [03:11:10] PROBLEM - misc1 icinga.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 309 bytes in 0.017 second response time [03:11:38] RECOVERY - misc1 webmail.miraheze.org HTTPS on misc1 is OK: HTTP OK: Status line output matched "HTTP/1.1 401 Unauthorized" - 5681 bytes in 0.106 second response time [03:13:07] RECOVERY - misc1 icinga.miraheze.org HTTPS on misc1 is OK: HTTP OK: HTTP/1.1 302 Found - 347 bytes in 0.106 second response time [03:13:09] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php-pdo_mysql] [03:13:29] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php-pdo_mysql] [03:14:15] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php-pdo_mysql] [03:16:05] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [03:21:11] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [03:21:15] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [03:21:19] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [03:22:28] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpbSI [03:22:30] [02miraheze/puppet] 07paladox 03a630827 - fix pdo_mysql/mysqlnd priority [03:40:15] hey paladox, working late? what are you doing if I may ask [03:41:09] still upgrading PHP to 7.3? [03:49:19] I’m moving us to a php module that will make it easy to switch to php 7.3 [03:49:30] I’ve stopped working though :) [03:49:34] Watching some tv [03:49:35] Now [04:00:32] nice [06:02:25] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 2a00:d880:5:8ea::ebc7/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [06:02:27] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:29] PROBLEM - papelor.io - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:31] PROBLEM - poserdazfreebies.orain.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:35] PROBLEM - ahmsaqib.cf - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:39] PROBLEM - wiki.drones4nature.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:41] PROBLEM - www.reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:59] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:03:01] PROBLEM - phab.miraheze.wiki on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:03:13] PROBLEM - holonet.pw - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:03:27] PROBLEM - www.guiasdobrasil.com.br - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:04:03] PROBLEM - meregos.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:04:11] PROBLEM - astrapedia.ru - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:04:15] PROBLEM - savage-wiki.com - RapidSSL on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:04:17] PROBLEM - miraheze.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:04:23] RECOVERY - eerstelijnszones.be - LetsEncrypt on sslhost is OK: OK - Certificate 'eerstelijnszones.be' will expire on Sat 23 Feb 2019 12:11:01 AM GMT +0000. [06:04:27] RECOVERY - papelor.io - LetsEncrypt on sslhost is OK: OK - Certificate 'papelor.io' will expire on Fri 01 Mar 2019 05:25:27 PM GMT +0000. [06:04:31] RECOVERY - poserdazfreebies.orain.org - LetsEncrypt on sslhost is OK: OK - Certificate 'orain.org' will expire on Fri 22 Feb 2019 06:35:03 PM GMT +0000. [06:04:33] RECOVERY - ahmsaqib.cf - LetsEncrypt on sslhost is OK: OK - Certificate 'ahmsaqib.cf' will expire on Fri 01 Mar 2019 07:20:59 PM GMT +0000. [06:04:39] RECOVERY - www.reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [06:04:57] RECOVERY - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thelonsdalebattalion.co.uk' will expire on Mon 25 Feb 2019 09:33:46 PM GMT +0000. [06:05:25] PROBLEM - froggy.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:05:59] RECOVERY - meregos.com - LetsEncrypt on sslhost is OK: OK - Certificate 'meregos.com' will expire on Fri 01 Mar 2019 06:12:33 PM GMT +0000. [06:06:03] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:06:09] PROBLEM - wiki.warfra.ml - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:06:11] RECOVERY - savage-wiki.com - RapidSSL on sslhost is OK: OK - Certificate 'savage-wiki.com' will expire on Fri 04 Dec 2020 12:00:00 PM GMT +0000. [06:06:17] RECOVERY - miraheze.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.wiki' will expire on Sat 23 Feb 2019 12:32:15 AM GMT +0000. [06:06:23] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:06:37] RECOVERY - wiki.drones4nature.info - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.drones4nature.info' will expire on Mon 25 Feb 2019 09:45:23 PM GMT +0000. [06:06:55] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:07:03] PROBLEM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:07:05] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:07:21] RECOVERY - froggy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'froggy.info' will expire on Sun 24 Feb 2019 07:41:25 PM GMT +0000. [06:08:05] RECOVERY - wiki.warfra.ml - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.warfra.ml' will expire on Fri 01 Mar 2019 10:27:13 PM GMT +0000. [06:08:15] RECOVERY - astrapedia.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'astrapedia.ru' will expire on Tue 26 Feb 2019 11:29:34 PM GMT +0000. [06:09:01] RECOVERY - speleo.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'speleo.wiki' will expire on Mon 25 Feb 2019 10:12:52 PM GMT +0000. [06:09:15] RECOVERY - holonet.pw - LetsEncrypt on sslhost is OK: OK - Certificate 'holonet.pw' will expire on Fri 01 Mar 2019 06:48:36 PM GMT +0000. [06:09:55] PROBLEM - permanentfuturelab.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:10:25] RECOVERY - reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [06:11:03] RECOVERY - disabled.life - LetsEncrypt on sslhost is OK: OK - Certificate 'disabled.life' will expire on Mon 25 Feb 2019 10:14:43 PM GMT +0000. [06:11:13] RECOVERY - pc-architect.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'pc-architect.tk' will expire on Fri 01 Mar 2019 04:34:06 PM GMT +0000. [06:11:55] RECOVERY - permanentfuturelab.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'permanentfuturelab.wiki' will expire on Fri 22 Feb 2019 11:11:54 PM GMT +0000. [06:14:15] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:14:25] RECOVERY - hgwiki.ga - LetsEncrypt on sslhost is OK: OK - Certificate 'hgwiki.ga' will expire on Fri 01 Mar 2019 10:30:23 PM GMT +0000. [06:14:27] PROBLEM - savage-wiki.com - RapidSSL on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:14:39] PROBLEM - wiki.dobots.nl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:16:33] PROBLEM - nenawiki.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:16:37] RECOVERY - wiki.dobots.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.dobots.nl' will expire on Fri 01 Mar 2019 07:01:45 PM GMT +0000. [06:17:09] PROBLEM - wiki.lbcomms.co.za - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:18:28] RECOVERY - nenawiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'nenawiki.org' will expire on Wed 27 Feb 2019 12:11:11 AM GMT +0000. [06:18:32] RECOVERY - savage-wiki.com - RapidSSL on sslhost is OK: OK - Certificate 'savage-wiki.com' will expire on Fri 04 Dec 2020 12:00:00 PM GMT +0000. [06:19:08] RECOVERY - wiki.lbcomms.co.za - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.lbcomms.co.za' will expire on Mon 25 Feb 2019 09:41:28 PM GMT +0000. [06:20:26] RECOVERY - kkutu.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'kkutu.wiki' will expire on Fri 01 Mar 2019 10:28:50 PM GMT +0000. [06:20:28] RECOVERY - wiki.make717.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.make717.org' will expire on Sun 24 Feb 2019 07:44:11 PM GMT +0000. [06:20:34] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:20:36] PROBLEM - sdiy.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:20:42] PROBLEM - papelor.io - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:20:50] PROBLEM - miraheze.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:22:32] RECOVERY - sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Fri 22 Feb 2019 11:44:22 PM GMT +0000. [06:22:34] RECOVERY - disabled.life - LetsEncrypt on sslhost is OK: OK - Certificate 'disabled.life' will expire on Mon 25 Feb 2019 10:14:43 PM GMT +0000. [06:22:40] RECOVERY - papelor.io - LetsEncrypt on sslhost is OK: OK - Certificate 'papelor.io' will expire on Fri 01 Mar 2019 05:25:27 PM GMT +0000. [06:22:44] RECOVERY - miraheze.com - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.com' will expire on Sat 23 Feb 2019 01:28:32 PM GMT +0000. [06:22:58] PROBLEM - give.effectively.to - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:23:04] PROBLEM - www.zenbuddhism.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:23:24] PROBLEM - spiral.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:24:04] PROBLEM - wiki.zymonic.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:24:46] PROBLEM - programming.red - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:24:54] RECOVERY - give.effectively.to - LetsEncrypt on sslhost is OK: OK - Certificate 'give.effectively.to' will expire on Fri 01 Mar 2019 06:16:46 PM GMT +0000. [06:25:00] RECOVERY - www.zenbuddhism.info - LetsEncrypt on sslhost is OK: OK - Certificate 'www.zenbuddhism.info' will expire on Mon 25 Feb 2019 09:38:43 PM GMT +0000. [06:25:18] RECOVERY - spiral.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'spiral.wiki' will expire on Sat 23 Feb 2019 10:43:09 PM GMT +0000. [06:25:54] PROBLEM - infectowiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:25:58] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:26:00] RECOVERY - wiki.zymonic.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.zymonic.com' will expire on Fri 01 Mar 2019 05:59:08 PM GMT +0000. [06:26:44] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:26:58] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:27:02] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:27:26] PROBLEM - froggy.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:27:54] RECOVERY - infectowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'infectowiki.com' will expire on Fri 01 Mar 2019 07:20:06 PM GMT +0000. [06:28:28] PROBLEM - prfm.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:28:48] RECOVERY - programming.red - LetsEncrypt on sslhost is OK: OK - Certificate 'programming.red' will expire on Fri 22 Feb 2019 11:47:07 PM GMT +0000. [06:29:50] PROBLEM - holonet.pw - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:30:26] RECOVERY - prfm.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'prfm.wiki' will expire on Fri 01 Mar 2019 10:28:04 PM GMT +0000. [06:30:48] RECOVERY - kkutu.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'kkutu.wiki' will expire on Fri 01 Mar 2019 10:28:50 PM GMT +0000. [06:30:52] RECOVERY - pc-architect.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'pc-architect.tk' will expire on Fri 01 Mar 2019 04:34:06 PM GMT +0000. [06:31:06] RECOVERY - disabled.life - LetsEncrypt on sslhost is OK: OK - Certificate 'disabled.life' will expire on Mon 25 Feb 2019 10:14:43 PM GMT +0000. [06:31:10] RECOVERY - hgwiki.ga - LetsEncrypt on sslhost is OK: OK - Certificate 'hgwiki.ga' will expire on Fri 01 Mar 2019 10:30:23 PM GMT +0000. [06:31:24] RECOVERY - froggy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'froggy.info' will expire on Sun 24 Feb 2019 07:41:25 PM GMT +0000. [06:31:44] RECOVERY - holonet.pw - LetsEncrypt on sslhost is OK: OK - Certificate 'holonet.pw' will expire on Fri 01 Mar 2019 06:48:36 PM GMT +0000. [06:31:48] PROBLEM - miraheze.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:32:04] RECOVERY - reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [06:35:19] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:35:33] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:35:34] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:35:59] RECOVERY - miraheze.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.wiki' will expire on Sat 23 Feb 2019 12:32:15 AM GMT +0000. [06:36:21] PROBLEM - astrapedia.ru - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:36:27] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:37:21] PROBLEM - tensegritywiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:38:19] RECOVERY - astrapedia.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'astrapedia.ru' will expire on Tue 26 Feb 2019 11:29:34 PM GMT +0000. [06:40:09] PROBLEM - docs.websmart.media - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:40:27] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:40:37] PROBLEM - ahmsaqib.cf - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:41:21] PROBLEM - wiki.consentcraft.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:41:27] RECOVERY - tensegritywiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'tensegritywiki.com' will expire on Fri 01 Mar 2019 07:23:02 PM GMT +0000. [06:41:33] PROBLEM - savage-wiki.com - RapidSSL on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:42:07] RECOVERY - docs.websmart.media - LetsEncrypt on sslhost is OK: OK - Certificate 'docs.websmart.media' will expire on Fri 01 Mar 2019 04:35:34 PM GMT +0000. [06:42:15] PROBLEM - spiral.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:42:21] RECOVERY - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thelonsdalebattalion.co.uk' will expire on Mon 25 Feb 2019 09:33:46 PM GMT +0000. [06:42:35] RECOVERY - ahmsaqib.cf - LetsEncrypt on sslhost is OK: OK - Certificate 'ahmsaqib.cf' will expire on Fri 01 Mar 2019 07:20:59 PM GMT +0000. [06:43:19] RECOVERY - wiki.consentcraft.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.consentcraft.uk' will expire on Fri 01 Mar 2019 05:33:43 PM GMT +0000. [06:43:31] RECOVERY - savage-wiki.com - RapidSSL on sslhost is OK: OK - Certificate 'savage-wiki.com' will expire on Fri 04 Dec 2020 12:00:00 PM GMT +0000. [06:43:43] RECOVERY - pc-architect.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'pc-architect.tk' will expire on Fri 01 Mar 2019 04:34:06 PM GMT +0000. [06:43:57] RECOVERY - hgwiki.ga - LetsEncrypt on sslhost is OK: OK - Certificate 'hgwiki.ga' will expire on Fri 01 Mar 2019 10:30:23 PM GMT +0000. [06:44:13] RECOVERY - spiral.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'spiral.wiki' will expire on Sat 23 Feb 2019 10:43:09 PM GMT +0000. [06:44:39] RECOVERY - reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [06:46:43] PROBLEM - permanentfuturelab.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:47:41] PROBLEM - wikipuk.cl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:48:07] PROBLEM - stablestate.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:48:47] PROBLEM - monarchists.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:49:37] RECOVERY - wikipuk.cl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikipuk.cl' will expire on Mon 25 Feb 2019 09:46:36 PM GMT +0000. [06:49:49] PROBLEM - www.eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:50:07] RECOVERY - stablestate.org - LetsEncrypt on sslhost is OK: OK - Certificate 'stablestate.org' will expire on Fri 01 Mar 2019 10:39:34 PM GMT +0000. [06:50:31] PROBLEM - wikibase.revi.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:50:45] RECOVERY - monarchists.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'monarchists.wiki' will expire on Fri 01 Mar 2019 10:38:50 PM GMT +0000. [06:51:54] PROBLEM - holonet.pw - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:52:30] RECOVERY - wikibase.revi.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'wikibase.revi.wiki' will expire on Fri 01 Mar 2019 04:53:08 PM GMT +0000. [06:52:52] RECOVERY - permanentfuturelab.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'permanentfuturelab.wiki' will expire on Fri 22 Feb 2019 11:11:54 PM GMT +0000. [06:53:10] PROBLEM - meregos.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:53:44] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:53:48] RECOVERY - holonet.pw - LetsEncrypt on sslhost is OK: OK - Certificate 'holonet.pw' will expire on Fri 01 Mar 2019 06:48:36 PM GMT +0000. [06:53:52] RECOVERY - www.eerstelijnszones.be - LetsEncrypt on sslhost is OK: OK - Certificate 'eerstelijnszones.be' will expire on Sat 23 Feb 2019 12:11:01 AM GMT +0000. [06:54:18] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:54:20] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:54:50] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:55:06] RECOVERY - meregos.com - LetsEncrypt on sslhost is OK: OK - Certificate 'meregos.com' will expire on Fri 01 Mar 2019 06:12:33 PM GMT +0000. [06:55:10] PROBLEM - studynotekr.miraheze.org - GlobalSign on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:55:14] PROBLEM - antiguabarbudacalypso.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:56:06] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:56:32] PROBLEM - www.wikiescola.com.br - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:57:08] RECOVERY - studynotekr.miraheze.org - GlobalSign on sslhost is OK: OK - Certificate '*.miraheze.org' will expire on Wed 23 Oct 2019 08:12:13 PM GMT +0000. [06:57:12] RECOVERY - antiguabarbudacalypso.com - LetsEncrypt on sslhost is OK: OK - Certificate 'antiguabarbudacalypso.com' will expire on Sat 02 Mar 2019 10:00:34 PM GMT +0000. [06:57:46] RECOVERY - drag.lgbt - LetsEncrypt on sslhost is OK: OK - Certificate 'drag.lgbt' will expire on Fri 01 Mar 2019 10:34:49 PM GMT +0000. [06:57:56] PROBLEM - tensegritywiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:58:06] PROBLEM - holonet.pw - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:58:26] RECOVERY - hgwiki.ga - LetsEncrypt on sslhost is OK: OK - Certificate 'hgwiki.ga' will expire on Fri 01 Mar 2019 10:30:23 PM GMT +0000. [06:58:32] RECOVERY - www.wikiescola.com.br - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiescola.com.br' will expire on Fri 22 Feb 2019 11:16:00 PM GMT +0000. [06:58:52] RECOVERY - reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [06:58:58] PROBLEM - wiki.exnihilolinux.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:59:54] RECOVERY - tensegritywiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'tensegritywiki.com' will expire on Fri 01 Mar 2019 07:23:02 PM GMT +0000. [07:00:00] RECOVERY - holonet.pw - LetsEncrypt on sslhost is OK: OK - Certificate 'holonet.pw' will expire on Fri 01 Mar 2019 06:48:36 PM GMT +0000. [07:00:06] PROBLEM - sdiy.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:00:12] PROBLEM - electowiki.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:00:34] RECOVERY - disabled.life - LetsEncrypt on sslhost is OK: OK - Certificate 'disabled.life' will expire on Mon 25 Feb 2019 10:14:43 PM GMT +0000. [07:00:52] RECOVERY - wiki.exnihilolinux.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.exnihilolinux.org' will expire on Fri 01 Mar 2019 05:26:17 PM GMT +0000. [07:01:14] PROBLEM - give.effectively.to - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:02:04] RECOVERY - sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Fri 22 Feb 2019 11:44:22 PM GMT +0000. [07:02:08] RECOVERY - electowiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'electowiki.org' will expire on Fri 01 Mar 2019 10:32:01 PM GMT +0000. [07:02:48] PROBLEM - www.programming.red - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:02:50] PROBLEM - www.splat-teams.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:03:04] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [07:03:10] RECOVERY - give.effectively.to - LetsEncrypt on sslhost is OK: OK - Certificate 'give.effectively.to' will expire on Fri 01 Mar 2019 06:16:46 PM GMT +0000. [07:04:00] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:04:30] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:04:44] RECOVERY - www.splat-teams.com - LetsEncrypt on sslhost is OK: OK - Certificate 'www.splat-teams.com' will expire on Fri 01 Mar 2019 05:24:29 PM GMT +0000. [07:04:50] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:05:00] PROBLEM - infectowiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:05:18] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:05:30] PROBLEM - miraheze.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:05:34] PROBLEM - wikitranslate.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:06:32] PROBLEM - www.sdiy.info - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:06:44] RECOVERY - www.guiasdobrasil.com.br - LetsEncrypt on sslhost is OK: OK - Certificate 'sni61771.cloudflaressl.com' will expire on Sun 02 Jun 2019 11:59:59 PM GMT +0000. [07:06:48] RECOVERY - hgwiki.ga - LetsEncrypt on sslhost is OK: OK - Certificate 'hgwiki.ga' will expire on Fri 01 Mar 2019 10:30:23 PM GMT +0000. [07:06:56] RECOVERY - www.programming.red - LetsEncrypt on sslhost is OK: OK - Certificate 'programming.red' will expire on Fri 22 Feb 2019 11:47:07 PM GMT +0000. [07:06:58] RECOVERY - infectowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'infectowiki.com' will expire on Fri 01 Mar 2019 07:20:06 PM GMT +0000. [07:07:14] RECOVERY - reviwiki.info - PositiveSSLDV on sslhost is OK: OK - Certificate 'reviwiki.info' will expire on Wed 03 Feb 2021 11:59:59 PM GMT +0000. [07:07:28] RECOVERY - miraheze.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.wiki' will expire on Sat 23 Feb 2019 12:32:15 AM GMT +0000. [07:07:32] RECOVERY - wikitranslate.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitranslate.tk' will expire on Sat 23 Feb 2019 06:47:53 PM GMT +0000. [07:07:54] RECOVERY - phab.miraheze.wiki on sslhost is OK: OK - Certificate 'miraheze.wiki' will expire on Sat 23 Feb 2019 12:32:15 AM GMT +0000. [07:08:02] RECOVERY - garrettcountyguide.com - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [07:08:25] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [07:08:33] RECOVERY - www.sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Fri 22 Feb 2019 11:44:22 PM GMT +0000. [07:08:39] RECOVERY - pc-architect.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'pc-architect.tk' will expire on Fri 01 Mar 2019 04:34:06 PM GMT +0000. [10:25:06] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3271 [11:13:19] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [11:23:17] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [11:35:04] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [12:21:07] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3297 [14:14:01] Hello placebo! If you have any questions feel free to ask and someone should answer soon. [14:44:15] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [14:52:16] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:13:18] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fpNkL [16:13:20] [02miraheze/puppet] 07paladox 035bb5c79 - Migrate phabricator to new php module [16:20:40] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+1/-0/±0] 13https://git.io/fpNkg [16:20:42] [02miraheze/puppet] 07paladox 03bddbed6 - Redirect mail.miraheze.org to webmail.miraheze.org [16:20:43] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [16:20:45] [02puppet] 07paladox opened pull request 03#934: Redirect mail.miraheze.org to webmail.miraheze.org - 13https://git.io/fpNk2 [16:21:11] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpNkw [16:21:13] [02miraheze/puppet] 07paladox 0321dfbc4 - Update init.pp [16:21:14] [02puppet] 07paladox synchronize pull request 03#934: Redirect mail.miraheze.org to webmail.miraheze.org - 13https://git.io/fpNk2 [16:21:42] [02puppet] 07paladox closed pull request 03#934: Redirect mail.miraheze.org to webmail.miraheze.org - 13https://git.io/fpNk2 [16:21:43] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fpNko [16:21:45] [02miraheze/puppet] 07paladox 03635950a - Redirect mail.miraheze.org to webmail.miraheze.org (#934) * Redirect mail.miraheze.org to webmail.miraheze.org * Update init.pp [16:21:46] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [16:21:48] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [16:22:04] paladox: phab is down [16:22:15] oh [16:22:16] And yes I saw your commit [16:22:33] and it's back [16:22:53] Ok [16:34:04] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [16:54:31] PROBLEM - misc4 phd on misc4 is CRITICAL: PROCS CRITICAL: 0 processes with args 'phd' [16:57:22] known ^^ [16:57:37] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[phd] [16:58:15] PROBLEM - mw2 Puppet on mw2 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 7 minutes ago with 0 failures [16:58:31] RECOVERY - misc4 phd on misc4 is OK: PROCS OK: 1 process with args 'phd' [16:58:53] PROBLEM - mw1 Puppet on mw1 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 7 minutes ago with 0 failures [16:59:35] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [17:00:36] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNLL [17:00:37] [02miraheze/puppet] 07paladox 03c3cac1a - Fix loading mysqlnd and pdo_mysql in php [17:00:58] HTTP CRITICAL - Unable to open TCP socket [17:01:03] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [17:03:18] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [17:06:04] PROBLEM - misc1 icinga.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 309 bytes in 0.017 second response time [17:07:18] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [17:08:04] RECOVERY - misc1 icinga.miraheze.org HTTPS on misc1 is OK: HTTP OK: HTTP/1.1 302 Found - 347 bytes in 0.028 second response time [17:11:14] !log depool mw1 [17:11:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:12:54] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [17:13:52] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 1 backends are down. mw1 [17:14:06] !log repool mw1 [17:14:15] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:15:52] RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy [17:16:36] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [17:18:58] !log depool mw2 [17:19:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:20:15] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [17:20:33] HTTP CRITICAL - Unable to open TCP socket [17:21:26] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNtv [17:21:27] [02miraheze/puppet] 07paladox 03d460dc3 - reload php-fpm if any php extensions are changed or installed [17:21:53] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 1 backends are down. mw2 [17:22:07] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw2 [17:23:43] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNtq [17:23:44] [02miraheze/puppet] 07paladox 03b19a6ce - Revert "reload php-fpm if any php extensions are changed or installed" This reverts commit d460dc3bee86fad558e820b75b29da5aa8ce3b10. Needs to be restarted for it to work not reloaded. [17:23:53] RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy [17:24:07] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [17:24:14] !log repool mw2 [17:24:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:25:45] !log depool mw3 [17:25:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:28:15] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [17:28:46] !log repool mw3 [17:28:52] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:30:15] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [17:34:19] HTTP CRITICAL - Unable to open TCP socket [17:42:08] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [17:55:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNqs [17:55:13] [02miraheze/services] 07MirahezeSSLBot 03b0fa33a - BOT: Updating services config for wikis [17:58:47] HTTP CRITICAL - Unable to open TCP socket [18:00:43] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [18:04:37] HTTP CRITICAL - Unable to open TCP socket [18:12:20] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [18:21:04] HTTP CRITICAL - Unable to open TCP socket [18:26:53] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [18:38:31] HTTP CRITICAL - Unable to open TCP socket [18:42:21] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [18:54:58] HTTP CRITICAL - Unable to open TCP socket [19:02:43] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [19:42:28] hey guys [19:43:11] paladox, sup dude [19:43:15] hi [19:43:38] may I ask you another noob question [19:45:14] yup [19:57:06] HTTP CRITICAL - Unable to open TCP socket [19:58:19] very helpful icinga [19:59:00] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [19:59:26] Voidwalker the bot is stripping the message :) [19:59:27] as it has a newline [19:59:28] im going to replace the bot source code with something better. [20:06:11] hi psiconauta [20:06:16] what's the question? :P [20:10:20] oh, I'm trying to hack MW... right now I'm messing with skins [20:10:40] and would like to create a new one [20:11:13] what would be the best way to accomplish that? [20:11:46] already customized Tweeki skin [20:12:02] ah if it's dev stuff count me out :P [20:12:10] though there are useful guides on MediaWiki.org [20:17:29] HTTP CRITICAL - Unable to open TCP socket [20:20:06] yeah, I already the 3 part tutorial [20:20:20] *read [20:22:26] Reception123, do you admin miraheze's dns? [20:22:43] I created a task on ph for a custom domain [20:24:31] already configured DNS records [20:25:28] right now, psiconauta.pt points to miraheze's land page [20:26:22] psiconauta: yes [20:26:24] I'll take a look [20:26:40] psiconauta: you can also make pull requests using GitHub :) [20:27:05] yeah, not comfortable yet [20:27:19] lots of things to learn still [20:27:39] ok :) [20:27:45] though that is how I learned [20:28:23] yeah, learn by doing [20:28:27] best way for sure [20:30:49] hummm, perhaps I could try to figure it out [20:31:34] probably just need to update dns records and in mw-config [20:32:34] psiconauta: first yes, second no since it's done in ManageWiki and third also the SSL repo [20:32:56] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 01 Mar 2019 07:07:29 PM GMT +0000. [20:33:06] oh, ok ok [20:33:16] [02miraheze/dns] 07Reception123 pushed 031 commit to 03master [+1/-0/±0] 13https://git.io/fpN36 [20:33:17] [02miraheze/dns] 07Reception123 0323cda33 - add psiconauta.pt zone [20:33:20] ^ psiconauta :) [20:34:13] that's I <3 open-source software... lots to learn from the experts :) [20:35:25] heh, I'm far from being an expert :P [20:35:43] paladox: heh first time generating a cert with the new script [20:35:50] Reception123 :) [20:35:55] it's awesome ain't it :D [20:36:14] paladox: does the process with the private keys stay the same? [20:36:23] Reception123 what do you mean? [20:36:32] remember to do -p [20:36:37] paladox: I mean I generated a cert and I don't see one [20:36:38] paladox: ah [20:36:47] paladox: I mean't the steps for puppet1 are the same as always? [20:36:51] Yup [20:37:07] the private key is in /etc/letsencrypt/live// [20:37:19] paladox: There is no -p mentioned in the docs! https://meta.miraheze.org/wiki/Tech:SSL_certificates [20:37:20] Title: [ Tech:SSL certificates - Miraheze Meta ] - meta.miraheze.org [20:37:39] some people actually read those :P [20:37:40] jk [20:37:48] Reception123 but /root/ssl-certificate -h documents it :D [20:38:08] paladox: well yeah, but if you have docs you might as well add that [20:38:58] done [20:39:07] thanks :) [20:40:16] ok, "see" you later :) [20:40:47] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fpN3d [20:40:49] [02miraheze/ssl] 07Reception123 03cbb347f - add wiki.hanaoto.me cert [20:40:54] psiconauta: ok, by the time you're back your domain will be set up :) [20:42:44] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fpN3p [20:42:46] [02miraheze/ssl] 07Reception123 038ba40b2 - add psiconauta.pt certificate [20:50:16] services.yaml is updated manually or once I add my domain through ManageWiki [20:50:18] ? [20:50:37] *or auto [20:50:47] psiconauta: done :) [20:51:01] psiconauta: automatically by a bot (when changing VE/Flow) [20:51:11] or the domain [20:51:42] so I don't need to add the domain on ManageWiki [20:51:44] ? [20:51:49] !log depool mw1 [20:51:51] psiconauta: No, you can't even [20:51:53] I've done it [20:51:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [20:51:57] Only sysadmins can add domains [20:53:19] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [20:54:42] hummm, just trying to understand... if it was possible to set up a custom domain just by use only ManageWiki, how would that work? [20:54:57] *just using [20:55:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNsn [20:55:13] [02miraheze/services] 07MirahezeSSLBot 03e05964b - BOT: Updating services config for wikis [21:00:56] probably would be necessary to create a sh script (to create the cert, add dns records and updating services and certs.yaml) that would have to be executed after or using queues + cron [21:03:18] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:06:48] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [21:07:37] !log repool mw1 [21:07:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:18:25] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:21:30] you cant automate it, theres too many moving parts [21:24:19] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [21:25:50] hey JohnLewis [21:30:29] hey [21:30:46] well I have to disagree but this is just a noob opinion... there has to be a way to automate it by creating a maintenance script or using a bot [21:32:01] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [21:33:04] oh btw, regard using guided tours on ManageWiki... I think that would be a simplier way to users learn how to use it, especially ManageWikiPermissions [21:33:38] *for [21:33:48] psiconauta there may be a way, but that would mean introducing a "security issue" by allowing you to touch the dns from mw* [21:35:57] But as JohnLewis says too many moving parts :) [21:45:05] paladox, just thinking loud... perhaps would have to work like CreateWiki (requiring admins to approve requests) [21:45:29] But underneeth it would have to push to github. [21:45:29] wouldn't change it tbh [21:45:33] Which would be dangerous [21:45:54] ah, neverminf [21:46:05] just a noob talking [21:46:43] paladox, how comfortable are you with skins? [21:46:53] Depends. [21:49:36] imagine I want to create a skin for miraheze (perhaps using some UX framework) [21:54:02] basically, would be easier to customize some skin (would be possible to completely change the UI?) or create one (using Skin:Example as base) [22:05:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpNGN [22:05:13] [02miraheze/services] 07MirahezeSSLBot 03cb9a7ab - BOT: Updating services config for wikis [22:11:55] Hello phoenix_! If you have any questions feel free to ask and someone should answer soon. [22:12:06] hi slovenes [22:13:40] sup phoenix :) [23:27:10] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3418 [23:40:12] Can you make https://ildril.miraheze.org/wiki/Main_Page not needing edits to stay open due to being unable to get people to write for it [23:40:13] Title: [ Ildril ] - ildril.miraheze.org