[05:24:47] PROBLEM - mh142.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:24:54] PROBLEM - antiguabarbudacalypso.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:24:58] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [05:25:02] PROBLEM - netazar.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:25:09] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [05:25:16] PROBLEM - cp4 HTTPS on cp4 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:25:33] PROBLEM - cp4 Disk Space on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [05:25:41] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [05:25:45] PROBLEM - cp4 Current Load on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [05:25:53] PROBLEM - Host cp4 is DOWN: PING CRITICAL - Packet loss = 100% [05:26:23] PROBLEM - guiasdobrasil.com.br - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:26:45] RECOVERY - mh142.com - LetsEncrypt on sslhost is OK: OK - Certificate 'mh142.com' will expire on Mon 28 Oct 2019 12:03:08 PM GMT +0000. [05:26:50] RECOVERY - antiguabarbudacalypso.com - LetsEncrypt on sslhost is OK: OK - Certificate 'antiguabarbudacalypso.com' will expire on Tue 29 Oct 2019 06:35:16 PM GMT +0000. [05:38:19] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:39:52] RECOVERY - netazar.org - LetsEncrypt on sslhost is OK: OK - Certificate 'www.netazar.org' will expire on Mon 07 Oct 2019 06:46:45 PM GMT +0000. [05:55:20] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sat 31 Aug 2019 02:47:02 PM GMT +0000. [06:02:55] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:17:48] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sat 31 Aug 2019 02:47:02 PM GMT +0000. [06:24:14] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:27:02] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2971 MB (12% inode=94%); [06:29:32] Reception123: morning, please check cp4, ns1 and misc1 as icinga was been complaining they're down. :) [06:30:16] hi [06:30:18] will do [06:31:17] From - icmp_seq=10 Destination unreachable: Address unreachable [06:31:21] well icinga is not wrong [06:31:49] Reception123: cp4 includes a disk space issue as well. Let me screenshot what I can see (or check the logs in here) [06:32:02] well can't do anything about that considering I can't ssh to the server ;) [06:32:40] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sat 31 Aug 2019 02:47:02 PM GMT +0000. [06:33:37] Reception123: Why is it refusing or you just not in a position to? [06:33:43] RhinosF1: "This virtual server has been suspended by the administrator. Please contact support" [06:33:50] Will contact RamNode to see what it's about [06:34:48] Reception123: yeah that's not good. Is that for all 3 (cp4/ns1/misc1) [06:34:56] no, only cp4... [06:35:25] RhinosF1: I am able to connect to the others, but they're probably just unhappy about cp4 being down [06:36:06] Reception123: ah, not good then. I'll let you get on to RamNode and wait for icinga to start shouting recovery [06:36:12] yeah [06:39:54] RhinosF1: my guess is it's something to do with high load [06:40:35] yeah- https://grafana.miraheze.org/d/W9MIkA7iz/miraheze-cluster?orgId=1&var-job=node&var-node=cp4.miraheze.org&var-port=9100&fullscreen&panelId=283 [06:40:36] [ Grafana ] - grafana.miraheze.org [06:41:06] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:43:05] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sat 31 Aug 2019 02:47:02 PM GMT +0000. [06:43:41] RhinosF1: looks like past reasons for servers being suspended were bandwith [06:44:41] Reception123: yeah looks like it went high at 0540 but that's 40-45 mins before icinga complained they were down but if they've done it before then even more likely it's that. Can u get it back up? [06:46:11] RhinosF1: well I can't without RamNode. and later on I'll not have access so paladox will probably have deal with it [06:46:28] (also if it is bandwidth I'd have to wait for some sort of approval from other ops before ordering more) [06:46:34] see https://phabricator.miraheze.org/T4594#87282 [06:46:35] [ ⚓ T4594 cp4 down (suspended) ] - phabricator.miraheze.org [06:47:37] Reception123: ah well that's unlucky [06:48:10] paladox: see ^ when you arrive [06:55:29] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:03:55] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sat 31 Aug 2019 02:47:02 PM GMT +0000. [07:04:40] RECOVERY - guiasdobrasil.com.br - LetsEncrypt on sslhost is OK: OK - Certificate 'guiasdobrasil.com.br' will expire on Tue 03 Sep 2019 02:35:01 PM GMT +0000. [07:05:02] RECOVERY - Host cp4 is UP: PING OK - Packet loss = 0%, RTA = 1.02 ms [07:05:03] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [07:05:09] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [07:05:10] PROBLEM - cp4 Puppet on cp4 is WARNING: WARNING: Puppet last ran 1 hour ago [07:05:11] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [07:05:27] RECOVERY - cp4 HTTPS on cp4 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 1496 bytes in 0.010 second response time [07:05:41] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [07:06:59] ^ RhinosF1 [07:07:10] Was bandwidth but they were nice and reset it [07:07:44] Reception123: Good, Do u want to close your ticket or shall I? (I'm on phab now) [07:10:32] Reception123: could you look at the figure with ShowBetaWelcome true v false for https://phabricator.miraheze.org/T4593 please [07:10:33] [ ⚓ T4593 "Welcome/Start Editing" pop-up appears every time a page is edited on AllTheTropes ] - phabricator.miraheze.org [07:10:35] I've closed [07:10:42] Reception123: seen [07:10:58] Unfortunately I can't right now, this was the last thing I could do before I leave. Just wanted to get that out of the way [07:11:02] Will look later though [07:11:22] Reception123: as that isn't first time it shows it it's constant and annoying but enjoy your day [07:14:49] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:13:02] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2650 MB (10% inode=94%); [13:45:18] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9ME [13:45:19] [02miraheze/mw-config] 07paladox 03d08c121 - Set wgArticleCountMethod to any for gfiwiki Bug: T4595 [13:46:24] !log root@mw1:/srv/mediawiki/w/maintenance# sudo -u www-data php updateArticleCount.php --wiki=gfiwiki --update - T4595 [13:46:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [13:55:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9MV [13:55:14] [02miraheze/services] 07MirahezeSSLBot 03ce1ff0c - BOT: Updating services config for wikis [13:58:58] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9MD [13:58:59] [02miraheze/mw-config] 07paladox 031e75d90 - Set wgArticleCountMethod to any for nonciclopediawiki [13:59:16] !log sudo -u www-data php updateArticleCount.php --wiki=nonciclopediawiki --update - T4312 [13:59:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:26:04] !log DELETE FROM config_entry WHERE configKey = 'phabricator.uninstalled-applications'; [14:26:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:08:07] can someone look at https://phabricator.miraheze.org/T4597? I think they mean for all namespaces by default but I can't remember whether it needs MW or a config change. [15:08:08] [ ⚓ T4597 Enable VisualEditor on https://msc.miraheze.org/wiki/Main_Page ] - phabricator.miraheze.org [15:09:41] i've wrote a comment, they doin't have VE installed. [15:10:07] paladox: Thx [15:13:02] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:13:05] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:13:14] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 17 failures. Last run 2 minutes ago with 17 failures. Failed resources (up to 3 shown) [15:13:33] PROBLEM - lizardfs3 Puppet on lizardfs3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:13:43] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:13:48] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 202 failures. Last run 2 minutes ago with 202 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.d],File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades] [15:13:58] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:03] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown) [15:14:05] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:06] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:13] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:15] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:29] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:30] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:32] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [15:14:32] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:14:33] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [15:14:48] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 3 minutes ago with 14 failures. Failed resources (up to 3 shown) [15:14:54] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:15:16] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9yI [15:15:18] [02miraheze/services] 07MirahezeSSLBot 03795ee9d - BOT: Updating services config for wikis [15:24:03] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [15:24:05] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [15:24:13] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [15:24:29] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [15:24:31] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [15:24:33] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [15:24:48] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:24:54] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [15:25:05] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [15:25:14] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:25:33] RECOVERY - lizardfs3 Puppet on lizardfs3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:25:43] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:25:58] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:26:06] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [15:26:15] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:26:30] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [15:26:32] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:27:02] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:27:45] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:49:09] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/fj9Sv [15:49:11] [02miraheze/mediawiki] 07paladox 03c8882d7 - Update PollNy [15:50:26] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/fj9SU [15:50:27] [02miraheze/mediawiki] 07paladox 036dac949 - Update ArticleFeedbackv5 [16:12:41] PROBLEM - ml.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:41] PROBLEM - pa.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:43] PROBLEM - or.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:44] PROBLEM - bn.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:49] PROBLEM - fa.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:51] PROBLEM - hi.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:12:58] PROBLEM - kn.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:02] PROBLEM - gu.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:17] PROBLEM - hif.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:21] PROBLEM - meta.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:35] PROBLEM - sa.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:37] PROBLEM - la.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:37] PROBLEM - mr.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:39] PROBLEM - mg.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:40] PROBLEM - mai.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:47] PROBLEM - en.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:50] uh [16:13:54] PROBLEM - commons.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:13:57] PROBLEM - ta.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:14:06] PROBLEM - te.gyaanipedia.co.in - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'en.gyaanipedia.co.in' expires in 15 day(s) (Sun 18 Aug 2019 04:10:08 PM GMT +0000). [16:14:15] well that should renew i guess in a sec [16:14:19] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9Sa [16:14:21] [02miraheze/ssl] 07MirahezeSSLBot 03002c3eb - Bot: Update SSL cert for en.gyaanipedia.co.in [16:22:57] paladox: why? The bot just did [16:23:17] RECOVERY - hif.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:21] RECOVERY - meta.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:35] RECOVERY - sa.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:37] RECOVERY - la.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:37] RECOVERY - mr.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:39] RECOVERY - mg.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:40] RECOVERY - mai.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:47] RECOVERY - en.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:51] Yup [16:23:52] Bot just did [16:23:53] Spam incoming :P [16:23:54] RECOVERY - commons.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:23:57] RECOVERY - ta.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:06] RECOVERY - te.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:41] RECOVERY - ml.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:41] RECOVERY - pa.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:43] RECOVERY - or.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:44] RECOVERY - bn.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:49] RECOVERY - fa.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:51] RECOVERY - hi.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:24:58] RECOVERY - kn.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:25:03] RECOVERY - gu.gyaanipedia.co.in - LetsEncrypt on sslhost is OK: OK - Certificate 'en.gyaanipedia.co.in' will expire on Thu 31 Oct 2019 03:14:12 PM GMT +0000. [16:29:34] PROBLEM - poserdazfreebies.orain.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'orain.org' expires in 15 day(s) (Sun 18 Aug 2019 04:27:32 PM GMT +0000). [16:29:44] PROBLEM - orain.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'orain.org' expires in 15 day(s) (Sun 18 Aug 2019 04:27:32 PM GMT +0000). [16:30:29] PROBLEM - allthetropes.orain.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'orain.org' expires in 15 day(s) (Sun 18 Aug 2019 04:27:32 PM GMT +0000). [16:31:08] PROBLEM - meta.orain.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'orain.org' expires in 15 day(s) (Sun 18 Aug 2019 04:27:32 PM GMT +0000). [16:37:07] PROBLEM - miraheze.wiki - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'miraheze.wiki' expires in 15 day(s) (Sun 18 Aug 2019 04:33:23 PM GMT +0000). [16:39:54] PROBLEM - miraheze.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'miraheze.com' expires in 15 day(s) (Sun 18 Aug 2019 04:36:53 PM GMT +0000). [18:32:05] Reception123: I hope you don't mind being stalked (I get pinged for all metawiki edits). Thx for fixing once I spotted it. [18:33:18] I don't, it's great for someone to check my (sometimes wrong) edits :p [18:34:10] Reception123: ah same, u know what happened with me trying to add that right the other day - spelt crat wrong and put it on the wrong wiki!!!!!! [18:35:00] Yeah.. though that was my fault as it was me who merged [18:35:36] Reception123: I'll take half the blame, at least it was one of my wikis I added it to. [18:36:10] Yeah if not that would not be good for me :( [18:36:46] But practice is who merges it takes all the blame [18:41:01] Reception123: no, but I'm being honest it wrote it and it was a hard-ish to detect mistake because rf1botwiki is new so you probably didn't think twice about it not saying that and it was simple spelling. We didn't break anything at least (just not fix it). I'll get there as I get more and more used to PHP and mediawiki. I think PHP is on the A-Level course at where I intent to go. [18:41:45] Well for actual syntax I rely on the faithful Travis ci after checking it myself [18:46:23] PROBLEM - db4 Disk Space on db4 is CRITICAL: DISK CRITICAL - free space: / 21973 MB (5% inode=96%); [18:46:46] Reception123: yeah travis is nice [19:09:31] @Stewards please see https://meta.miraheze.org/w/index.php?title=Meta:Administrators%27_noticeboard&diff=79010&oldid=78910 [19:09:32] [ Difference between revisions of "Meta:Administrators' noticeboard" - Miraheze Meta ] - meta.miraheze.org [19:19:59] JohnLewis: ^ [19:21:28] I've not handled it before and in the past no evidence has been handed either way. The wording of it seems like it's an account of something which happened in a stream and not an accusation [19:22:25] JohnLewis: I'm going to leave it to you to respond to the issue in either your position as staff or steward [19:22:58] I'm choosing not to respond, PuppyKun has dealt with it in the past [19:23:10] that's a steward issue so should be moved. [19:23:17] JohnLewis: okay [19:23:52] paladox: yeah probably but I'm choosing to refer this to the right people and not get involved [19:24:12] ok [19:27:42] PROBLEM - www.modesofdiscourse.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'www.modesofdiscourse.com' expires in 15 day(s) (Sun 18 Aug 2019 07:25:08 PM GMT +0000). [19:27:55] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9Qu [19:27:56] [02miraheze/ssl] 07MirahezeSSLBot 03f4203a3 - Bot: Update SSL cert for www.modesofdiscourse.com [19:30:16] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9Qg [19:30:17] [02miraheze/services] 07MirahezeSSLBot 032bb0702 - BOT: Updating services config for wikis [19:33:42] RECOVERY - www.modesofdiscourse.com - LetsEncrypt on sslhost is OK: OK - Certificate 'www.modesofdiscourse.com' will expire on Thu 31 Oct 2019 06:27:49 PM GMT +0000. [19:38:40] RhinosF1: I'm working with local staff on that one. that was my bad kinda [19:38:55] i missed that during cleanup the other day, they said they'll edit the page and im only going to remove previous revisions [19:39:05] PuppyKun: okay, as long as someone deals with it [20:08:46] PROBLEM - jawright.cc - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'www.jawright.cc' expires in 15 day(s) (Sun 18 Aug 2019 08:05:41 PM GMT +0000). [20:08:47] PROBLEM - www.jawright.cc - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'www.jawright.cc' expires in 15 day(s) (Sun 18 Aug 2019 08:05:41 PM GMT +0000). [20:09:01] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj9Q5 [20:09:02] [02miraheze/ssl] 07MirahezeSSLBot 03e49c4bf - Bot: Update SSL cert for www.jawright.cc [20:12:46] RECOVERY - jawright.cc - LetsEncrypt on sslhost is OK: OK - Certificate 'www.jawright.cc' will expire on Thu 31 Oct 2019 07:08:54 PM GMT +0000. [20:12:47] RECOVERY - www.jawright.cc - LetsEncrypt on sslhost is OK: OK - Certificate 'www.jawright.cc' will expire on Thu 31 Oct 2019 07:08:54 PM GMT +0000. [20:29:18] [02ssl] 07Reception123 created branch 03Reception123-patch-1 - 13https://git.io/vxP9L [20:29:19] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03Reception123-patch-1 [+1/-0/±0] 13https://git.io/fj97T [20:29:21] [02miraheze/ssl] 07Reception123 03afa222e - add nonlinearly.com cert [20:29:22] [02ssl] 07Reception123 opened pull request 03#209: add nonlinearly.com cert - 13https://git.io/fj97k [20:30:14] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03Reception123-patch-1 [+0/-0/±1] 13https://git.io/fj97L [20:30:16] [02miraheze/ssl] 07Reception123 03d7b4ddc - Update certs.yaml [20:30:17] [02ssl] 07Reception123 synchronize pull request 03#209: add nonlinearly.com cert - 13https://git.io/fj97k [20:30:34] [02ssl] 07Reception123 closed pull request 03#209: add nonlinearly.com cert - 13https://git.io/fj97k [20:30:35] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fj97t [20:30:37] [02miraheze/ssl] 07Reception123 03117ea6f - add nonlinearly.com cert (#209) * add nonlinearly.com cert * Update certs.yaml [20:32:01] [02miraheze/ssl] 07paladox deleted branch 03Reception123-patch-1 [20:32:03] [02ssl] 07paladox deleted branch 03Reception123-patch-1 - 13https://git.io/vxP9L [20:41:52] RhinosF1: https://meta.miraheze.org/wiki/User_talk:TheGiant1 mind re-doing the template? that version is pretty outdated [20:41:53] [ User talk:TheGiant1 - Miraheze Meta ] - meta.miraheze.org [20:41:57] i updated it [20:42:54] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:43:02] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:43:05] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:43:21] ^ PuppyKun [20:43:22] Reception123: yeah done, Was going to look at making a new one soon anyway [20:43:24] *paladox sorry [20:43:45] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:44:06] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:44:15] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:44:30] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:44:32] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [20:45:24] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj97W [20:45:25] [02miraheze/ssl] 07paladox 032c41717 - Fix indentation [20:49:23] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj97l [20:49:25] [02miraheze/ssl] 07Reception123 03bbcedc6 - wrong CA [20:53:20] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [21:06:39] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [21:12:48] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [21:13:15] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [21:13:19] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj97D [21:13:21] [02miraheze/ssl] 07Reception123 0300ccb02 - CF = case sensitive [21:14:15] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [21:14:17] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:14:43] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:15:53] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:18:06] [02miraheze/ssl] 07Reception123 pushed 032 commits to 03Reception123-patch-1 [+1/-0/±1] 13https://git.io/fj979 [21:18:08] [02miraheze/ssl] 07Reception123 03afa222e - add nonlinearly.com cert [21:18:09] [02miraheze/ssl] 07Reception123 03d7b4ddc - Update certs.yaml [21:18:11] [02ssl] 07Reception123 created branch 03Reception123-patch-1 - 13https://git.io/vxP9L [21:18:51] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-1/±0] 13https://git.io/fj97H [21:18:52] [02miraheze/ssl] 07Reception123 0324b7b48 - rm nonlinearly.com cert (issues) [21:18:58] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fj97Q [21:19:00] [02miraheze/ssl] 07Reception123 03de8826c - rm nonlinearly.com cert (issues) [21:24:59] [02miraheze/ssl] 07paladox pushed 032 commits to 03master [+1/-0/±1] 13https://git.io/fj97x [21:25:00] [02miraheze/ssl] 07paladox 0384e58e8 - Revert "rm nonlinearly.com cert (issues)" This reverts commit de8826ca7e8680588adfa035cd8af69bcebd5195. [21:25:02] [02miraheze/ssl] 07paladox 03b076802 - Revert "rm nonlinearly.com cert (issues)" This reverts commit 24b7b48058a110859dafeef30426398f17efa8b6.