[00:04:11] Hello mirahezebots! If you have any questions feel free to ask and someone should answer soon. [00:04:18] bah [00:04:49] 21:52 PM GMT +0000. [00:05:11] +0000. [00:10:37] 0 seconds [00:10:43] ah here we go :) [00:11:39] s [00:11:53] 29:34 PM GMT +0000. [00:12:32] GMT +0000. [00:21:37] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±4] 13https://git.io/fphuD [00:21:39] [02miraheze/puppet] 07paladox 0323c2c5a - fix ircecho [00:25:23] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fphup [00:25:24] [02miraheze/puppet] 07paladox 03bf16638 - Fix path to ircecho_password [00:26:44] 05:32:44 PM GMT +0000. [00:26:58] woo! [00:27:58] [02puppet] 07paladox created branch 03paladox-patch-4 - 13https://git.io/vbiAS [00:27:59] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fphzW [00:28:01] [02miraheze/puppet] 07paladox 034381d80 - Fix support for ircecho in icinga2 irc scripts [00:28:02] [02puppet] 07paladox opened pull request 03#938: Fix support for ircecho in icinga2 irc scripts - 13https://git.io/fphzl [00:28:22] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fphz4 [00:28:24] [02miraheze/puppet] 07paladox 03248823e - Update irc-service-notification.sh [00:28:25] [02puppet] 07paladox synchronize pull request 03#938: Fix support for ircecho in icinga2 irc scripts - 13https://git.io/fphzl [00:29:30] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fphzE [00:29:32] [02miraheze/puppet] 07paladox 0335cdc95 - Update ircecho.pp [00:29:33] [02puppet] 07paladox synchronize pull request 03#938: Fix support for ircecho in icinga2 irc scripts - 13https://git.io/fphzl [00:30:00] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+1/-0/±0] 13https://git.io/fphzu [00:30:02] [02miraheze/puppet] 07paladox 0381845f4 - Create ircecho_logrotate.conf [00:30:03] [02puppet] 07paladox synchronize pull request 03#938: Fix support for ircecho in icinga2 irc scripts - 13https://git.io/fphzl [00:30:10] [02puppet] 07paladox closed pull request 03#938: Fix support for ircecho in icinga2 irc scripts - 13https://git.io/fphzl [00:30:11] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±3] 13https://git.io/fphzz [00:30:13] [02miraheze/puppet] 07paladox 0340986b5 - Fix support for ircecho in icinga2 irc scripts (#938) * Fix support for ircecho in icinga2 irc scripts * Update irc-service-notification.sh * Update ircecho.pp * Create ircecho_logrotate.conf [00:30:14] [02puppet] 07paladox deleted branch 03paladox-patch-4 - 13https://git.io/vbiAS [00:30:16] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-4 [00:30:23] . [00:32:16] ate 'wiki.macc.nyc' will expire on Fri 01 Mar 2019 04:51:03 PM GMT +0000. paladox test [00:32:16] CUSTOM - wiki.macc.nyc - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.macc.nyc' will expire on Fri 01 Mar 2019 04:51:03 PM GMT +0000. paladox test [00:32:16] CUSTOM - wiki.macc.nyc - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.macc.nyc' will expire on Fri 01 Mar 2019 04:51:03 PM GMT +0000. paladox test [00:32:16] CUSTOM - wiki.macc.nyc - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.macc.nyc' will expire on Fri 01 Mar 2019 04:51:03 PM GMT +0000. paladox test [00:32:16] CUSTOM - wiki.macc.nyc - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.macc.nyc' will expire on Fri 01 Mar 2019 04:51:03 PM GMT +0000. paladox test [00:32:28] great works now! [00:32:49] CUSTOM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds paladox test [00:32:49] CUSTOM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds paladox test [00:32:49] CUSTOM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds paladox test [00:32:49] CUSTOM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds paladox test [00:32:49] CUSTOM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds paladox test [00:33:00] why 5? [00:33:06] 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. 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. [00:33:06] 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. 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. [00:33:06] 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. [00:33:10] RECOVERY - russopedia.info - LetsEncrypt on sslhost is OK: OK - Certificate 'russopedia.info' will expire on Fri 01 Mar 2019 07:16:41 PM GMT +0000. [00:33:11] RECOVERY - russopedia.info - LetsEncrypt on sslhost is OK: OK - Certificate 'russopedia.info' will expire on Fri 01 Mar 2019 07:16:41 PM GMT +0000. [00:33:11] RECOVERY - russopedia.info - LetsEncrypt on sslhost is OK: OK - Certificate 'russopedia.info' will expire on Fri 01 Mar 2019 07:16:41 PM GMT +0000. [00:33:11] RECOVERY - russopedia.info - LetsEncrypt on sslhost is OK: OK - Certificate 'russopedia.info' will expire on Fri 01 Mar 2019 07:16:41 PM GMT +0000. [00:33:11] RECOVERY - russopedia.info - LetsEncrypt on sslhost is OK: OK - Certificate 'russopedia.info' will expire on Fri 01 Mar 2019 07:16:41 PM GMT +0000. [00:35:46] conds [00:36:03] 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. [00:36:03] 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. [00:36:03] 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. [00:36:03] 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. [00:36:03] 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. [00:36:07] 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. [00:36:07] 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. [00:36:07] 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. [00:36:07] 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. [00:36:07] 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. [00:36:15] 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. [00:36:15] 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. [00:36:15] 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. [00:36:15] 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. [00:36:15] 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. [00:36:17] 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. [00:36:17] 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. [00:36:17] 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. [00:36:17] 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. [00:36:17] 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. [00:36:39] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:39] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:39] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:39] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:39] PROBLEM - drag.lgbt - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:40] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:40] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:40] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:40] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:36:41] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:37:39] RECOVERY - cornetto.online - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [00:37:39] RECOVERY - cornetto.online - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [00:37:39] RECOVERY - cornetto.online - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [00:37:39] RECOVERY - cornetto.online - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [00:37:39] RECOVERY - cornetto.online - LetsEncrypt on sslhost is OK: OK - Certificate 'garrettcountyguide.com' will expire on Fri 01 Mar 2019 06:13:53 PM GMT +0000. [00:39:03] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:39:03] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:39:03] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:39:03] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:39:03] PROBLEM - garrettcountyguide.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:39:49] RECOVERY - newsnow.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'newsnow.wiki' will expire on Fri 01 Mar 2019 10:35:39 PM GMT +0000. [00:39:49] RECOVERY - newsnow.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'newsnow.wiki' will expire on Fri 01 Mar 2019 10:35:39 PM GMT +0000. [00:39:49] RECOVERY - newsnow.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'newsnow.wiki' will expire on Fri 01 Mar 2019 10:35:39 PM GMT +0000. [00:39:49] RECOVERY - newsnow.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'newsnow.wiki' will expire on Fri 01 Mar 2019 10:35:39 PM GMT +0000. [00:39:49] RECOVERY - newsnow.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'newsnow.wiki' will expire on Fri 01 Mar 2019 10:35:39 PM GMT +0000. [00:40:06] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:06] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:06] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:06] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:06] PROBLEM - kkutu.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:26] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:26] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:26] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:26] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:26] PROBLEM - hgwiki.ga - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:27] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:28] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:28] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:28] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:29] PROBLEM - pc-architect.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:35] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:35] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:35] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:35] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:35] PROBLEM - disabled.life - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:40:48] 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. [00:40:48] 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. [00:40:48] 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. [00:40:48] 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. [00:40:48] 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. [00:41: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. [00:41:03] 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. [00:41:03] 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. [00:41:03] 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. [00:41:03] 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. [00:41:16] PROBLEM - wikiverte.pl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:16] PROBLEM - wikiverte.pl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:16] PROBLEM - wikiverte.pl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:16] PROBLEM - wikiverte.pl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:16] PROBLEM - wikiverte.pl - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:26] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:26] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:26] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:26] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:41:27] PROBLEM - eerstelijnszones.be - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:42:23] 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. [00:42:23] 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. [00:42:23] 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. [00:42:23] 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. [00:42:23] 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. [00:42:24] 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. [00:42:24] 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. [00:42:24] 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. [00:42:24] 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. [00:42: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. [00:42:29] 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. [00:42:30] 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. [00:42:30] 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. [00:42:30] 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. [00:42:30] 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. [00:42:31] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:42:31] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:42:31] PROBLEM - reviwiki.info - PositiveSSLDV on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:42:51] 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. [00:42:51] 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. [00:42:51] 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. [00:42:51] 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. [00:42:51] 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. [00:43:13] RECOVERY - wikiverte.pl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiverte.pl' will expire on Fri 01 Mar 2019 10:36:29 PM GMT +0000. [00:43:13] RECOVERY - wikiverte.pl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiverte.pl' will expire on Fri 01 Mar 2019 10:36:29 PM GMT +0000. [00:43:13] RECOVERY - wikiverte.pl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiverte.pl' will expire on Fri 01 Mar 2019 10:36:29 PM GMT +0000. [00:43:14] RECOVERY - wikiverte.pl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiverte.pl' will expire on Fri 01 Mar 2019 10:36:29 PM GMT +0000. [00:43:14] RECOVERY - wikiverte.pl - LetsEncrypt on sslhost is OK: OK - Certificate 'wikiverte.pl' will expire on Fri 01 Mar 2019 10:36:29 PM GMT +0000. [00:43: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. [00:43: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. [00:43: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. [00:43: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. [00:43: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. [00:44:43] PROBLEM - nonbinary.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:44:43] PROBLEM - nonbinary.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:44:43] PROBLEM - nonbinary.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:44:43] PROBLEM - nonbinary.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:44:43] PROBLEM - nonbinary.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:45:50] 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. [00:45:50] 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. [00:45:50] 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. [00:45:50] 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. [00:45:50] 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. [00:46:23] 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. [00:46:23] 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. [00:46:23] 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. [00:46:23] 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. [00:46:23] 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. [00:46:25] 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. [00:46:25] 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. [00:46:25] 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. [00:46:25] 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. [00:46:25] 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. [00:46:31] 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. [00:46:31] 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. [00:46:31] 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. [00:46:31] 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. [00:46:31] 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. [00:46:38] RECOVERY - nonbinary.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'nonbinary.wiki' will expire on Sun 24 Feb 2019 07:36:04 PM GMT +0000. [00:46:38] RECOVERY - nonbinary.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'nonbinary.wiki' will expire on Sun 24 Feb 2019 07:36:04 PM GMT +0000. [00:46:38] RECOVERY - nonbinary.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'nonbinary.wiki' will expire on Sun 24 Feb 2019 07:36:04 PM GMT +0000. [00:46:38] RECOVERY - nonbinary.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'nonbinary.wiki' will expire on Sun 24 Feb 2019 07:36:04 PM GMT +0000. [00:46:38] RECOVERY - nonbinary.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'nonbinary.wiki' will expire on Sun 24 Feb 2019 07:36:04 PM GMT +0000. [00:47:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:47:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:47:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:47:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:47:19] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:47:22] huh [00:47:30] why is the quiet not working? [00:49:20] paladox: i am used to mode +m for that [00:49:41] to ensure nobody can talk without + ? [00:49:45] +m means unvoiced users carn't speak [00:49:51] yea [00:53:53] CUSTOM - Host cp4 is UP: PING OK - Packet loss = 0%, RTA = 1.57 ms paladox test [00:53:56] ah [00:54:00] i know the fix [00:54:07] will commit later after more testing [00:54:20] or maybe i can do that now [00:54:21] hmm [00:55:42] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fph2T [00:55:43] [02miraheze/puppet] 07paladox 03367a936 - Fix icinga2 hosts/service irc messages to not send more then once [00:55:45] [02puppet] 07paladox created branch 03paladox-patch-4 - 13https://git.io/vbiAS [00:55:46] [02puppet] 07paladox opened pull request 03#939: Fix icinga2 hosts/service irc messages to not send more then once - 13https://git.io/fph2k [00:56:46] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fph2q [00:56:48] [02miraheze/puppet] 07paladox 032674b48 - Update notifications.conf [00:56:49] [02puppet] 07paladox synchronize pull request 03#939: Fix icinga2 hosts/service irc messages to not send more then once - 13https://git.io/fph2k [00:57:18] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/fph2O [00:57:19] [02miraheze/puppet] 07paladox 03eeb7827 - Update hosts.conf [00:57:21] [02puppet] 07paladox synchronize pull request 03#939: Fix icinga2 hosts/service irc messages to not send more then once - 13https://git.io/fph2k [00:57:34] [02puppet] 07paladox closed pull request 03#939: Fix icinga2 hosts/service irc messages to not send more then once - 13https://git.io/fph2k [00:57:36] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fph2s [00:57:37] [02miraheze/puppet] 07paladox 03555e8e9 - Fix icinga2 hosts/service irc messages to not send more then once (#939) * Fix icinga2 hosts/service irc messages to not send more then once * Update notifications.conf * Update hosts.conf [00:59:34] CUSTOM - 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. paladox test [01:01:03] CUSTOM - docs.websmart.media - LetsEncrypt on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket paladox test [01:01:55] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 697 [01:01:55] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 56864 MB (15% inode=96%); [01:01:55] PROBLEM - docs.websmart.media - LetsEncrypt on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [08:26:30] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw1 mw2 [08:26:33] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw1 mw2 [08:26:50] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [08:29:06] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [08:29:10] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [08:32:30] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [08:32:33] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [08:32:50] RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy [08:33:06] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [08:33:10] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [12:50:57] [02miraheze/landing] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjkL [12:50:59] [02miraheze/landing] 07paladox 032f8d833 - fix typo was reported on discord [12:51:39] [02miraheze/landing] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjkq [12:51:41] [02miraheze/landing] 07paladox 03fafb9c6 - Update fontawesome to 5.6.1 [14:55:34] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjZ8 [14:55:35] [02miraheze/mw-config] 07paladox 03c947be1 - Set all wiki's to read only [14:57:54] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjZo [14:57:56] [02miraheze/puppet] 07paladox 03a6cb530 - Raise table-definition-cache and table-open-cache to 800 (#936) [14:57:57] [02puppet] 07paladox closed pull request 03#936: Raise table-definition-cache and table-open-cache to 800 - 13https://git.io/fphnP [14:58:01] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [14:58:02] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [14:58:27] [02puppet] 07paladox closed pull request 03#937: Increase max-allowed-packet to 64M - 13https://git.io/fphWp [14:58:28] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjZ1 [14:58:30] [02miraheze/puppet] 07paladox 032fa1312 - Increase max-allowed-packet to 64M (#937) [14:58:31] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-3 [14:58:33] [02puppet] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/vbiAS [15:01:08] PROBLEM - db4 Puppet on db4 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 10 minutes ago with 0 failures [15:01:53] !log upgrading db4 to debian 9.6 and also mariadb to 10.2.19 [15:03:08] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:04:22] PROBLEM - db4 MySQL on db4 is CRITICAL: Can't connect to MySQL server on '81.4.109.166' (111 "Connection refused") [15:04:30] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [15:04:33] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [15:04:50] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [15:05:08] PROBLEM - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is CRITICAL: CRITICAL - NGINX Error Rate is 92% [15:05:10] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [15:05:17] PROBLEM - cp2 HTTPS on cp2 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3803 bytes in 0.402 second response time [15:05:20] PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is CRITICAL: CRITICAL - NGINX Error Rate is 95% [15:05:29] PROBLEM - misc4 phabricator.miraheze.org HTTPS on misc4 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 4195 bytes in 0.040 second response time [15:05:54] PROBLEM - misc1 webmail.miraheze.org HTTPS on misc1 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 200 OK [15:05:56] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb [15:06:03] PROBLEM - misc2 HTTPS on misc2 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 2271 bytes in 0.069 second response time [15:07:14] PROBLEM - cp5 HTTPS on cp5 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3814 bytes in 1.068 second response time [15:07:19] PROBLEM - cp4 HTTPS on cp4 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3801 bytes in 0.011 second response time [15:07:29] RECOVERY - misc4 phabricator.miraheze.org HTTPS on misc4 is OK: HTTP OK: HTTP/1.1 200 OK - 18358 bytes in 0.119 second response time [15:07:54] 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.044 second response time [15:08:01] PROBLEM - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is CRITICAL: CRITICAL - NGINX Error Rate is 62% [15:10:34] RECOVERY - db4 MySQL on db4 is OK: Uptime: 132 Threads: 46 Questions: 3139 Slow queries: 0 Opens: 162 Flush tables: 1 Open tables: 156 Queries per second avg: 23.780 [15:11:08] PROBLEM - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is WARNING: WARNING - NGINX Error Rate is 54% [15:11:10] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [15:11:15] RECOVERY - cp5 HTTPS on cp5 is OK: HTTP OK: HTTP/1.1 200 OK - 23718 bytes in 2.146 second response time [15:11:17] RECOVERY - cp2 HTTPS on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 23729 bytes in 0.505 second response time [15:11:19] RECOVERY - cp4 HTTPS on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 23695 bytes in 0.021 second response time [15:11:20] RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 10% [15:11:54] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [15:12:01] PROBLEM - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is WARNING: WARNING - NGINX Error Rate is 40% [15:12:30] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [15:12:33] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [15:12:50] RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy [15:13:08] RECOVERY - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is OK: OK - NGINX Error Rate is 18% [15:14:01] RECOVERY - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is OK: OK - NGINX Error Rate is 9% [15:14:10] RECOVERY - misc2 HTTPS on misc2 is OK: HTTP OK: HTTP/1.1 200 OK - 44907 bytes in 0.156 second response time [15:14:13] !log [15:01:53] <@paladox> !log upgrading db4 to debian 9.6 and also mariadb to 10.2.19 [15:15:42] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjcS [15:15:43] [02miraheze/mw-config] 07paladox 031b03c51 - Revert "Set all wiki's to read only" This reverts commit c947be13d8883e2bce73ebf25bbaacd27787ecca. [15:16:32] !log [15:01:53] <@paladox> !log upgrading db4 to debian 9.6 and also mariadb to 10.2.19 [15:16:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:42:38] PROBLEM - misc1 Current Load on misc1 is CRITICAL: CRITICAL - load average: 1.72, 2.23, 1.14 [15:44:38] RECOVERY - misc1 Current Load on misc1 is OK: OK - load average: 0.24, 1.50, 1.00 [15:53:28] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [16:03:28] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:33:28] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [16:41:28] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:49:42] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjgg [16:49:43] [02miraheze/puppet] 07paladox 0354ac7f6 - update matomo to 3.8.0-b5 [17:04:11] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjai [17:04:12] [02miraheze/mw-config] 07paladox 0330205ca - Remove some configuration per T3895 [18:15:14] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpj61 [18:15:15] [02miraheze/services] 07MirahezeSSLBot 035c1f97e - BOT: Updating services config for wikis [18:33:28] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [18:43:28] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [18:53:28] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [19:03:28] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:13:42] !log dropping puppetdb on postgresql (on db4) [19:13:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:15:07] !log stopping puppetdb on puppet1 [19:15:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:27:58] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 56648 MB (15% inode=96%); [19:28:22] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 782 [19:37:47] how can I enable the TemplateData extension? [19:47:27] unmannedkite, if you create a task on Phabricator (https://phabricator.miraheze.org) a sysadmin should be able to get you sorted. [19:50:50] unmannedkite: hi, I'm a system administrator. for which wiki is this request? [19:54:20] TemplateData is enabled alongside VisualEditor iirc [19:54:36] I did enable visualeditor [19:55:02] but I get a json syntax error in templates that include TemplateData [19:55:46] link? [20:01:09] sorry, link to what? [20:01:24] a template with a json error [20:01:37] oh, right [20:01:41] just a sec [20:02:21] @penguinstyles hi! [20:02:31] Heya Reception [20:02:45] welcome back :D [20:03:08] Thanks! Sorry I left so suddenly. I've had a lot going on in my personal life [20:03:19] There is no problem [20:03:21] I'm so excited to see that Miraheze is still doing so well [20:03:24] Just glad to see you around again :) [20:03:30] Wikia is a total shitstorm right now [20:03:32] @penguinstyles Yes, me too [20:03:35] Heh, I've heard stuff yes [20:04:42] @penguinstyles We've got many new things too [20:04:50] I noticed! [20:04:54] Like thanks to John ManageWiki is finally fully functional [20:05:08] (well not fully, there's still quite a few things to implement) [20:05:14] but most things that users had to request are now there [20:05:30] Yeah, I noticed when I logged in on kingkillerwiki [20:05:42] Awesome that you can manage your own extensions, etc. now [20:06:23] Yeah [20:23:58] I've actually created a few for Yugipedia over the last few months. [20:24:17] One big one was integrating card prices into all TCG card pages [20:24:20] That one was fun [20:27:03] sounds interesting :) [22:01:51] [02miraheze/MirahezeMagic] 07JohnFLewis pushed 031 commit to 03master [+2/-0/±2] 13https://git.io/fpjAd [22:01:52] [02miraheze/MirahezeMagic] 07JohnFLewis 03d8907d5 - add all GNF code [22:02:32] [02miraheze/MirahezeMagic] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjAx [22:02:34] [02miraheze/MirahezeMagic] 07JohnFLewis 0318fef44 - add i18n [22:04:14] [02miraheze/mw-config] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjxL [22:04:15] [02miraheze/mw-config] 07JohnFLewis 03ce90e39 - add new blacklisted right [22:05:55] JohnLewis https://github.com/miraheze/MirahezeMagic/compare/531059ff2283...d8907d54aba9#diff-a614c414d2a2715b3d06e0e4dc54204bL16 [22:05:56] Title: [ Comparing 531059ff2283...d8907d54aba9 · miraheze/MirahezeMagic · GitHub ] - github.com [22:05:57] needs a global [22:06:58] [02miraheze/MirahezeMagic] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fpjxc [22:06:59] [02miraheze/MirahezeMagic] 07JohnFLewis 03c3d1001 - add i18n [22:07:27] [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_31 [+0/-0/±1] 13https://git.io/fpjxl [22:07:28] [02miraheze/mediawiki] 07JohnFLewis 03d88e0c4 - update MM [22:08:29] Is it possible to change the name of the main page to something else on my Wiki? [22:08:32] (eg. "Home")? [22:09:31] you can either edit MediaWiki:Mainpagename, or just move the main page to that title [22:15:10] how do I edit it? [22:15:14] sorry if thats a stupid question [22:15:47] PROBLEM - mw2 Puppet on mw2 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] [22:15:55] PROBLEM - mw3 Puppet on mw3 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] [22:17:05] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [22:18:23] when i go to https://maiasongcontest.miraheze.org/wiki/MediaWiki:Mainpagename its empty [22:18:24] Title: [ MediaWiki:Mainpagename - Maia Song Contest ] - maiasongcontest.miraheze.org [22:18:27] which makes me think i've misunderstood [22:22:16] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpjpE [22:22:17] [02miraheze/puppet] 07paladox 0319ac8a1 - Set PassengerMaxPoolSize based on ram usage [22:22:46] https://commonswiki.miraheze.org/wiki/Special:GlobalNewFiles [22:22:48] Title: [ Gobal New Files - Miraheze Commons ] - commonswiki.miraheze.org [22:23:03] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [22:23:27] joshhh :) [22:23:33]