[00:00:55] <Voidwalker>	 there isn't one, so no one does
[00:02:05] <Zppix>	 Voidwalker:  *waits for  a pronunciation policy RfC*  :P
[00:02:44] <Voidwalker>	 I would probably close it as moot :P
[00:02:59] <apap>	 aw ;)
[00:03:01] <apap>	 :(*
[00:03:06] <Zppix>	 Voidwalker:  anti-pronunciation are you :P
[00:04:00] <Voidwalker>	 lol
[00:04:12] <apap>	 Voidwalker: this is just an individual question, not Miraheze related. should I PM it to you or can I ask here?
[00:04:31] <Zppix>	 apap:  if its not personal feel free to ask here
[00:04:39] <apap>	 okay
[00:04:56] <apap>	 it's just a question about Wikipedia cloaks
[00:05:10] <apap>	 how long did it take to get your cloak Void?
[00:06:53] <Voidwalker>	 around a week but less than two
[00:07:01] <apap>	 weird
[00:07:03] <Voidwalker>	 but it was around three years ago
[00:07:14] <apap>	 oh
[00:07:22] <apap>	 i guess it was different then
[00:07:50] <Zppix>	 Voidwalker:  thats sound about right when i used to have one
[00:07:59] <Zppix>	 but i may be wrong that was many moons ago
[00:08:21] <Zppix>	 nor do I care to remember the cloak has memories i dont like remembering
[00:08:27] <icinga-miraheze>	 PROBLEM - bacula1 Bacula Private Git on bacula1 is WARNING: WARNING: Full, 4198 files, 8.698MB, 2019-09-29 00:05:00 (1.1 weeks ago)
[00:08:29] <apap>	 i think it's taking me almost a month to get my cloak, but ill wait.
[00:08:33] <apap>	 o no
[05:38:19] <RhinosF1>	 .tell apap WikiMedia cloaks can take a long time to be issued, don't worry. I waited a few month when I had one.
[05:38:19] <ZppixBot>	 RhinosF1: I'll pass that on when apap is around.
[06:25:34] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3037 MB (12% inode=94%);
[07:53:00] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 1 datacenter is down: 2400:6180:0:d0::403:f001/cpweb
[07:53:55] <icinga-miraheze>	 PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[07:56:07] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[07:56:46] <icinga-miraheze>	 RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy
[08:09:35] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw1 mw2
[08:10:04] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[08:10:46] <icinga-miraheze>	 PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[08:10:59] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[08:11:21] <icinga-miraheze>	 PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw2 mw3
[08:12:38] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[08:12:59] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[08:13:38] <icinga-miraheze>	 RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24570 bytes in 0.392 second response time
[08:13:50] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[08:14:07] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy
[09:26:42] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 1 datacenter is down: 107.191.126.23/cpweb
[09:28:01] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1
[09:29:40] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[09:30:39] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[11:55:09] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeCHZ
[11:55:11] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot 03e4dbe9d - BOT: Updating services config for wikis
[15:01:11] <ZppixBot>	 Hello wm-bot514! If you have any questions, feel free to ask and someone should answer soon.
[16:49:08] <BurningPrincess>	 I don't want anyone with an acct to edit, just people I allow,. Will it do that?
[16:52:36] <Voidwalker>	 instead of adding the edit right to user, create a new group for the right
[16:52:49] <BurningPrincess>	 Thanks
[16:54:11] <BurningPrincess>	 Voidwalker:  what should my editor group be called?
[16:54:25] <Voidwalker>	 what ever you want it to be called :)
[16:54:27] <BurningPrincess>	 I can't decied beween editor or member
[16:55:10] <Voidwalker>	 member tends to be used for read access on private wikis, but you can decide what that means
[16:58:31] <BurningPrincess>	 I can't change the group for some reason
[16:58:59] <RhinosF1>	 BurningPrincess: what's the error?
[16:59:43] <BurningPrincess>	 https://imgur.com/a/Lobma80
[17:00:57] <RhinosF1>	 BurningPrincess: go the MangeWiki/permissions page and find the group you want to able to add that right to a user, then look in the group assignments section
[17:03:36] <BurningPrincess>	 502 Bad Gateway
[17:04:06] <RhinosF1>	 paladox:
[17:04:12] <k6ka>	 Yep, we've hit 503s again.
[17:04:50] <k6ka>	 Recommended action: sacrifice RhinosF1 to the gods to break this curse
[17:05:16] * k6ka starts preparing the sacrificial pyre
[17:05:17] <RhinosF1>	 Issue known - hopefully it'll recover
[17:05:26] <RhinosF1>	 If not, stare at paladox
[17:08:30] <icinga-miraheze>	 PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw3
[17:08:52] <RhinosF1>	 Known
[17:08:57] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw1 mw2
[17:11:18] <icinga-miraheze>	 RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy
[17:11:45] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[17:17:27] <RhinosF1>	 k6ka, BurningPrincess: how's that now?
[17:18:07] <k6ka>	 up again for me
[17:18:12] <RhinosF1>	 Good
[17:18:54] <paladox>	 sorry for all the issues :(
[17:19:02] <paladox>	 We are still looking at this
[17:37:36] <BurningPrincess>	 RhinosF1:  done, thank you
[17:39:21] <RhinosF1>	 BurningPrincess: good
[17:40:38] <BurningPrincess>	 I am happy tjhat it seems that miraheze will last as one wiki host I hosted it on shut down
[17:51:06] <BurningPrincess>	 I wanted more peo[le to write for the wiki, but IU am n ot sure how to get more people
[17:53:14] <Not-f817>	 [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeCAl
[17:53:16] <Not-f817>	 [02miraheze/ManageWiki] 07translatewiki 03ed4cd2a - Localisation updates from https://translatewiki.net.
[17:53:17] <ZppixBot>	 [ Main page - translatewiki.net ] - translatewiki.net.
[17:53:19] <Not-f817>	 [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeCA8
[17:53:20] <Not-f817>	 [02miraheze/MirahezeMagic] 07translatewiki 03a3db2c0 - Localisation updates from https://translatewiki.net.
[17:53:21] <ZppixBot>	 [ Main page - translatewiki.net ] - translatewiki.net.
[18:20:11] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeCxq
[18:20:12] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot 030f3c9d3 - BOT: Updating services config for wikis
[18:28:44] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[18:29:00] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[18:31:43] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[18:31:51] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[19:22:53] <icinga-miraheze>	 PROBLEM - wiki.pyxxl.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[19:23:29] <icinga-miraheze>	 PROBLEM - islamkosh.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[19:24:12] <icinga-miraheze>	 PROBLEM - wiki.om3ga.tk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[19:32:35] <icinga-miraheze>	 RECOVERY - wiki.pyxxl.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.pyxxl.tk' will expire on Thu 24 Oct 2019 06:31:50 PM GMT +0000.
[19:33:00] <icinga-miraheze>	 RECOVERY - islamkosh.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'islamkosh.tk' will expire on Sat 16 Nov 2019 01:40:12 PM GMT +0000.
[19:36:29] <icinga-miraheze>	 RECOVERY - wiki.om3ga.tk - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.om3ga.tk' will expire on Fri 22 Nov 2019 12:00:37 PM GMT +0000.
[20:32:12] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.11, 6.44, 4.39
[20:39:38] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.60, 6.54, 5.38
[22:13:50] <Examknow>	 hi
[23:27:20] <Zppix>	 paladox:  im right in saying theres no way for me to run a direct query against the DB is there (kinda like how wikimedia has replicas)
[23:27:42] <paladox>	 yup
[23:28:13] <Zppix>	 paladox:  looks like i get to have some alone time with an api.php result and stripping all the unwanted crap
[23:28:16] <Zppix>	 xD
[23:29:29] <paladox>	 heh