[00:00:56] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3594 MB (14% inode=93%); [01:44:09] PROBLEM - gluster1 Current Load on gluster1 is WARNING: WARNING - load average: 6.93, 4.80, 3.16 [01:45:13] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.14, 20.93, 16.57 [01:46:09] RECOVERY - gluster1 Current Load on gluster1 is OK: OK - load average: 2.79, 3.96, 3.05 [01:49:14] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 15.39, 19.74, 17.27 [02:08:26] PROBLEM - wiki.earthmcbe.space - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.earthmcbe.space could not be found [02:18:50] @Hispano76 What function does $wgMetaNamespace perform? Sorry, not familiar with that MediaWiki function off hand. [02:35:20] PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 24.66, 18.80, 16.32 [02:37:20] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 11.74, 15.87, 15.54 [02:40:02] @Doug $wgMetaNamespace is the config I mentioned a while ago, that sets the Project namespace [02:46:08] > @Doug $wgMetaNamespace is the config I mentioned a while ago, that sets the Project namespace @Universal Omega Ah, so you could essentially define a ''different'' namespace as the "project" namespace. That would be a useful feature. Thanks! 🙂 [02:54:34] Yep! [03:10:18] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JJVXy [03:10:20] [02miraheze/services] 07MirahezeSSLBot 03ee2f645 - BOT: Updating services config for wikis [03:25:10] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JJV1s [03:25:12] [02miraheze/services] 07MirahezeSSLBot 03f1a97c5 - BOT: Updating services config for wikis [03:59:34] PROBLEM - wiki.nowchess.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.nowchess.org could not be found [04:06:23] RECOVERY - wiki.nowchess.org - reverse DNS on sslhost is OK: rDNS OK - wiki.nowchess.org reverse DNS resolves to cp6.miraheze.org [06:26:38] RECOVERY - misc1 APT on misc1 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [06:46:49] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JJVQR [06:46:51] [02miraheze/ssl] 07Reception123 0364b9a45 - renew wiki.valkyrienskies.org [06:54:20] RECOVERY - wiki.valkyrienskies.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.valkyrienskies.org' will expire on Sat 31 Oct 2020 05:46:31 GMT +0000. [06:55:39] PROBLEM - test2 Puppet on test2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php7.3-apcu] [07:02:37] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 22.61, 21.18, 18.91 [07:03:36] RECOVERY - test2 Puppet on test2 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [07:08:40] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.13, 19.84, 19.26 [08:06:37] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 20.96, 19.93, 18.94 [08:08:37] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 17.39, 19.15, 18.80 [08:12:40] PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.24, 22.39, 20.13 [08:13:32] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 7.37, 5.18, 3.78 [08:14:40] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 13.88, 19.29, 19.29 [08:15:32] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 4.25, 4.86, 3.84 [09:02:27] RhinosF1 Zppix Reception123 https://meta.miraheze.org/wiki/Requests_for_Comment/Allow_wiki_bureaucrats_to_have_SSH_access_to_the_forked_server [09:02:27] [ Requests for Comment/Allow wiki bureaucrats to have SSH access to the forked server - Miraheze Meta ] - meta.miraheze.org [09:03:35] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 6.95, 5.74, 4.64 [09:05:32] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 3.96, 5.05, 4.52 [09:06:09] PROBLEM - gluster1 Current Load on gluster1 is CRITICAL: CRITICAL - load average: 8.72, 6.98, 5.88 [09:07:38] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 20.79, 21.12, 19.38 [09:08:09] RECOVERY - gluster1 Current Load on gluster1 is OK: OK - load average: 5.96, 6.54, 5.86 [09:09:37] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.35, 19.10, 18.83 [11:23:46] PROBLEM - mw4 Current Load on mw4 is CRITICAL: CRITICAL - load average: 8.52, 6.24, 4.76 [11:25:43] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 3.86, 5.42, 4.65 [11:27:35] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 18.63, 20.68, 19.52 [11:29:35] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 14.44, 18.75, 18.97 [12:23:07] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JJwf5 [12:23:09] [02miraheze/ssl] 07Reception123 03c9361d0 - add tla.awiki.org cert [12:35:18] PROBLEM - tla.awiki.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - tla.awiki.org reverse DNS resolves to 58.82.2fa9.ip4.static.sl-reverse.com [12:35:26] PROBLEM - tla.awiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address tla.awiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [12:35:34] Reception123: ^ [12:37:17] RhinosF1: well it worked when I generated a cert [12:37:36] Reception123: rDNS is wrong [12:37:39] I'll be back in about 30 mins [12:37:52] RhinosF1: hmm [12:38:06] Reception123: heh, clicking the url redirects to mw-lb [12:38:16] I think they set it up wrong [12:43:40] Hello [12:43:48] How can be user topic banned on Miraheze Meta? Notice on talk page and if he violates the ban, will he be blocked? [12:44:04] Yes [12:44:07] By meta admin/steward/cocc? [12:44:15] Any of them [12:45:05] Because I think the number of three nonsensical RfCs is enough. [12:45:12] Yeah topic ban them [12:46:28] Can i do it? Or should I leave it to someone else? [12:48:33] You can [12:48:50] (because i deleted 2 RfCs by him and i am bit new:) ) [12:48:57] Okay, in 15 mins. [12:48:59] Thank you [12:49:53] There's enough clarity and agreement on it that it's common sense to do it [12:51:14] No one's going to oppose it [12:51:31] * RhinosF1 tweaked wording for clarity via discord [12:53:02] RhinosF1: I'll let them a chance to fix if not remove [12:58:48] Reception123: it's not even serving the wiki though [12:59:24] It just redirects to mw-lb.miraheze.org [13:12:06] @RhinosF1 https://ctrlv.cz/DMM9 [13:12:08] [ CtrlV.cz | Nejrychlejší ScreenShot a PrintScreen online ] - ctrlv.cz [13:12:57] Is it okay? [13:19:39] hello! [13:19:50] Hello [13:20:12] our wiki, https://tuscriaturas.miraheze.org/wiki/ is being very slow. But the English version, is going fine [13:20:13] [ Bestiario del Hypogripho ] - tuscriaturas.miraheze.org [13:20:38] we wonder if having installed some plugin/complement (whatever they are called) could have impacted the speed? [13:21:02] an example of plugin/complement: disqustag [13:38:04] @MrJaroslavik: perfect [13:38:26] Thank [13:55:24] [02landing] 07MrJaroslavik commented on pull request 03#40: Add Czech Translation (2) - 13https://git.io/JJwIR [14:20:17] !log GDPR removal [14:20:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:24:49] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 7.17, 6.11, 5.00 [15:26:47] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 4.33, 5.33, 4.85 [15:30:22] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JJwYB [15:30:23] [02miraheze/services] 07MirahezeSSLBot 03d45f322 - BOT: Updating services config for wikis [15:32:07] Rumors are being spread about users being locked unfairly, please do know that is not the case we cannot comment on specifics but please do know it was action as required by our ToU. [15:32:41] Zppix: where was/is this? [15:32:58] AmandaCath: see meta [15:33:41] Huh [15:34:30] GDPR violations IMHO should just be deleted... but I guess an argument could be made for locking for repeated issues [15:35:52] !log runJobs on mw7 with specific type [15:35:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:36:05] Although, there's no global lock log for either the old username or the renamed account. Is a GDPR violation a valid reason for CentralAuth to be oversighted? [15:36:22] If so, the global rename log should also be RevDel'd [15:36:37] And maybe the account locally blocked with "Oversight Block" [15:37:11] AmandaCath: as ive said numerous times in the last couple hours, we cannot comment [15:38:09] I'm not asking for comment on this particular case. I'm asking a general question [15:38:37] AmandaCath: the lock isn't logged [15:38:42] Hello n[m]1! If you have any questions, feel free to ask and someone should answer soon. [15:38:59] RhinosF1: exactly. That means that CA was oversighted [15:39:29] I'm asking a general question if GDPR violations were a reason to oversight the account, since it doesn't seem like it at first glance [15:39:36] AmandaCath: nope, it's managed by a gdpr script that doesn't insert a log [15:39:44] It's not an oversight block; it was ToU enforcement, which is the exclusive jurisdiction of system administrators, not stewards. [15:40:23] Well, anything that hasn't been oversighted should be publicly logged, even if the specifics can't be disclosed [15:40:41] Tech:Server admin log it was [15:40:50] The steps for gdpr aren't public so I'm not going to comment on when things will be logged etc or deleted [15:41:20] ^ [15:41:30] And Doug is correct [15:41:54] n[m]1: can we help you? [15:43:09] Unrelated, but worth noting: please ignore the global abuse log hits from my wiki (simcitywiki) - I've handled it already [15:43:42] AmandaCath: okay [15:53:18] Not at the moment but thanks for asking :) [15:55:39] wait a minute, the reason for that GDPR lock is right on their user page [15:55:50] They self-disclose they are under 13 [15:55:58] Should that be deleted? [15:58:35] <-CloudGuy38-> Well I am 14 (almost to 15), so it's like a COPPA thing. [15:59:45] @CloudGuy38 yeah, that too. But the EU's GDPR is more restrictive in that it virtually does not allow any data collection whatsoever for those under 13, I believe [16:00:08] <-CloudGuy38-> ok [16:00:18] AmandaCath: there's a process we follow and scripts that have to be ran in select order. I've already said we're not going to say exactly how that works but please please please never draw public attention to that. [16:06:00] Hm, the current privacy policy wording suggests that children under 13 can use Miraheze services but their data will not be collected. That should probably be fixed/clarified [16:06:14] To indicate that those under 13 are not allowed to use MH services [16:07:29] under the GDPR the age of consent is 16 [16:11:33] hi [16:11:34] <-CloudGuy38-> It said between 13-16 [16:12:36] > To indicate that those under 13 are not allowed to use MH services Speaking in general terms, that reference may be intentional, and may not need correcting. Miraheze cannot enforce that which it does not know. [16:13:10] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 7.69, 5.68, 4.94 [16:13:34] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2647 MB (10% inode=93%); [16:13:35] In short, that policy is probably properly worded and thoroughly vetted by Miraheze Staff and Board. 🙂 [16:13:55] No offense intended, but GDPR sucks [16:14:10] It's just so complicated to understand fully etc [16:14:22] <-CloudGuy38-> There's a lot of chapters [16:14:24] It protects user privacy [16:15:01] Reception123: I know that, but surely there's a more straightforward/simpler way to accomplish the same thing [16:15:07] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 3.77, 4.98, 4.78 [16:15:26] AmandaCath: well say that to the EU [16:15:58] And anyway many non EU companies also enforce it since they have EU users [16:17:05] An example being the WMF [16:21:05] GDPR in a nutshell: Companies based in the European Union have to: * Collect only a limited amount of data, * Retain that data for only a limited time, * Disclose how they collect, handle, secure, retain, and destroy data; and, * Not collect data on users in certain demographic groups and, where known, destroy that data when they've collected it. [16:21:16] It's a lot of legalese, but it couldn't be simpler. [16:21:33] AmandaCath: email board@ if you want it changing [16:21:33] It's one of the best user privacy laws in the world. [16:21:38] ^ [16:21:40] ^ [16:25:04] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 6.19, 6.90, 5.57 [16:25:18] !sre report of 503 (T6009), needs investigating [16:25:36] Just seen [16:26:26] Probably just a too large import [16:27:02] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 3.44, 5.70, 5.30 [16:27:24] AmandaCath: https://phabricator.miraheze.org/T6009#117494 [16:27:25] [ ⚓ T6009 503 Backend fetch failed ] - phabricator.miraheze.org [16:27:27] Reception123: yes [16:29:32] What's the import size limit anyway? [16:30:34] AmandaCath: it's not strict [16:30:40] Yeah it depends [16:30:49] It's just taking that long that the web server kills it [16:31:46] RhinosF1 i recommend you enable "Clean delete reasons" gadget in preferences :) [16:37:13] > RhinosF1 i recommend you enable "Clean delete reasons" gadget in preferences :) @MrJaroslavik Yes, that's a good gadget. However, in this case, actually, that deletion rationale was so perfectly concise, it fit completely into a one-line log entry. 🙂 [16:38:36] > What's the import size limit anyway? I heard @paladox say something like ~900 MB or something a few weeks ago. It's fairly large. If one is patient, even large imports can be imported. Agree, though, that [[Special:Import]] from a GUI perspective is sub-optimal. [16:38:44] but that's a WMF thing 😉 [16:38:46] What Doug said [16:39:48] It will never get to 900MB [16:39:59] Usually it fails around over 20 MB [16:40:02] Or earlier [16:40:06] yeah, exactly [16:41:07] largest import I did on TestWiki yesterday was 17 MB, but that was only for a single page [16:41:34] and it had a lot of revisions...took a few minutes, but imported perfectly 🙂 [16:47:03] Hello Waggle! If you have any questions, feel free to ask and someone should answer soon. [16:47:56] RhinosF1 DO NOT BAN ME ANYMORE [16:48:02] That works [16:49:15] ... erm? [16:50:05] Sigyn DO NOT BAN ME FROM THIS SERVER ANYMORE. [16:51:53] shakes his head [16:52:59] <-CloudGuy38-> shaking my head too [16:54:08] @MatchCheck3223: they got killed by a bot [16:54:40] Hello CircleyDoesExtra! If you have any questions, feel free to ask and someone should answer soon. [16:55:00] Hi CircleyDoesExtra [16:55:12] Do you mind proving from discord it's you [16:55:17] Yes [16:55:27] I am from Discord as -CloudGuy38- [16:55:53] Can you make a comment on discord saying it just to be 100% sure [16:56:06] <-CloudGuy38-> Yes [16:56:12] Oh I got it [16:56:34] Perfect [16:57:59] Now I made a account [16:58:36] Why does Miraheze block Tor and VPN users from creating an account? [16:58:48] n[m]1: it's an extension [16:59:30] It's possible to request an exemption by emailing Stewards if you have a good reason [17:03:40] > I heard @paladox say something like ~900 MB or something a few weeks ago. It's fairly large. If one is patient, even large imports can be imported. Agree, though, that [[Special:Import]] from a GUI perspective is sub-optimal. @Doug 250MB [17:04:45] RhinosF1: does the extension apply to hosted wikis too or only the metawiki? [17:05:01] n[m]1: all wikis [17:05:33] > @Doug 250MB @paladox Thanks, sorry for getting the number wrong. Appreciate the clarification. 🙂 [17:06:12] May I ask why this extension to block VPN/Tor is being used? [17:06:21] Open proxies [17:06:49] .mh NOP [17:06:49] https://meta.miraheze.org/wiki/NOP [17:06:54] n[m]1: ^ [17:08:30] If you are a trusted user, though, and have not been globally sanctioned by sysadmins or stewards, stewards can grant global IP exemptions pretty liberally as Reception123 said. [17:09:41] Well it depends if there's a good reason [17:09:46] To prevent abuse [17:10:49] Thanks for the answers! [17:12:04] Here's a relevant read: https://arxiv.org/pdf/1904.04324.pdf [17:13:22] PROBLEM - mw4 Current Load on mw4 is CRITICAL: CRITICAL - load average: 9.36, 6.10, 4.98 [17:13:33] Tor is blocked and any nodes not auto blocked will be on discovery [17:15:20] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 4.35, 5.42, 4.87 [17:32:42] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 7.66, 6.34, 5.34 [17:34:40] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 4.51, 5.70, 5.23 [17:40:29] Hey RhinosF1 [17:44:30] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 7.33, 6.18, 5.35 [17:46:28] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 3.77, 5.13, 5.06 [17:54:46] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 6.83, 6.53, 5.71 [17:56:45] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 3.84, 5.42, 5.39 [18:13:28] PROBLEM - mw5 Current Load on mw5 is CRITICAL: CRITICAL - load average: 10.43, 6.64, 5.55 [18:14:28] PROBLEM - mw4 Current Load on mw4 is WARNING: WARNING - load average: 8.00, 6.28, 5.30 [18:15:26] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 6.69, 6.86, 5.79 [18:16:28] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 3.34, 5.17, 5.02 [18:17:26] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 3.70, 5.73, 5.50 [18:43:02] PROBLEM - mw5 Current Load on mw5 is CRITICAL: CRITICAL - load average: 8.06, 5.97, 5.36 [18:43:06] PROBLEM - mw4 Current Load on mw4 is CRITICAL: CRITICAL - load average: 8.46, 6.31, 5.46 [18:45:00] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 7.49, 6.75, 5.74 [18:45:05] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 6.11, 6.49, 5.65 [18:45:45] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.84, 19.30, 17.68 [18:46:58] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 3.75, 5.65, 5.46 [18:47:44] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 16.92, 18.45, 17.58 [19:14:39] PROBLEM - cloud2 Current Load on cloud2 is CRITICAL: CRITICAL - load average: 25.53, 21.23, 18.86 [19:16:38] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 19.29, 19.99, 18.67 [19:42:27] PROBLEM - cloud2 Current Load on cloud2 is WARNING: WARNING - load average: 21.60, 20.28, 18.96 [19:50:28] RECOVERY - cloud2 Current Load on cloud2 is OK: OK - load average: 18.96, 19.96, 19.57 [20:12:00] PROBLEM - gluster1 Current Load on gluster1 is CRITICAL: CRITICAL - load average: 10.23, 7.45, 5.83 [20:13:56] RECOVERY - gluster1 Current Load on gluster1 is OK: OK - load average: 3.80, 6.16, 5.57 [20:58:22] !log GDPR action [20:58:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [21:36:31] !log enforce GDPR [21:36:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [22:53:07] ^ MirahezeBot being down is known, small issue with PyPi [23:36:57] PROBLEM - tla.awiki.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for tla.awiki.org could not be found [23:43:11] [02landing] 07paladox closed pull request 03#40: Add Czech Translation (2) - 13https://git.io/JJafy [23:43:13] [02miraheze/landing] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JJwEr [23:43:14] [02miraheze/landing] 07MrJaroslavik 0367570ad - Add Czech Translation (2) (#40) * Add Czech Translation (2) * Add Czech * -1 blank line [23:43:56] PROBLEM - tla.awiki.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - tla.awiki.org reverse DNS resolves to 57.82.2fa9.ip4.static.sl-reverse.com [23:44:02] miraheze/landing/master/67570ad - MrJaroslavik The build was broken. https://travis-ci.org/miraheze/landing/builds/714308811 [23:50:58] PROBLEM - tla.awiki.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for tla.awiki.org could not be found [23:55:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JJwEH [23:55:14] [02miraheze/services] 07MirahezeSSLBot 03ae6a2f4 - BOT: Updating services config for wikis [23:57:56] PROBLEM - tla.awiki.org - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - tla.awiki.org reverse DNS resolves to 57.82.2fa9.ip4.static.sl-reverse.com