[00:02:52] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 4023 MB (16% inode=93%); [00:05:35] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 17.00, 21.09, 16.98 [00:07:38] PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[php7.3-apcu] [00:07:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [00:08:39] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 13.04, 17.65, 16.40 [00:10:08] PROBLEM - bacula2 Bacula Private Git on bacula2 is WARNING: WARNING: Full, 4113 files, 11.96MB, 2020-04-26 00:05:00 (1.1 weeks ago) [00:13:54] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:14:08] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [00:30:04] RECOVERY - bacula2 Disk Space on bacula2 is OK: DISK OK - free space: / 949040 MB (99% inode=99%); [00:32:13] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfsKg [00:32:14] [02miraheze/puppet] 07paladox 038545d5c - db6 fix label [00:38:03] !log upgrade puppet-agent - puppet2 [00:38:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [00:38:07] err bacula2 [00:38:09] * paladox fixes [00:38:58] !log re-started backups on bacula2 [00:39:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:01:13] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/Jfs6E [01:01:15] [02miraheze/puppet] 07paladox 03823df26 - db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 [01:01:16] [02puppet] 07paladox created branch 03paladox-patch-3 - 13https://git.io/vbiAS [01:01:18] [02puppet] 07paladox opened pull request 03#1352: db6/db7: Raise mariadb::config::table_definition_cache and mariadb::c… - 13https://git.io/Jfs6u [01:01:21] [02puppet] 07paladox edited pull request 03#1352: db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 - 13https://git.io/Jfs6u [01:01:26] [02puppet] 07paladox edited pull request 03#1352: db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 - 13https://git.io/Jfs6u [01:01:45] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/Jfs6z [01:01:46] [02miraheze/puppet] 07paladox 033ffa597 - Update db7.yaml [01:01:48] [02puppet] 07paladox synchronize pull request 03#1352: db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 - 13https://git.io/Jfs6u [01:01:55] [02puppet] 07paladox closed pull request 03#1352: db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 - 13https://git.io/Jfs6u [01:01:56] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Jfs62 [01:01:58] [02miraheze/puppet] 07paladox 0384748a5 - db6/db7: Raise mariadb::config::table_definition_cache and mariadb::config::table_open_cache to 10000 (#1352) [01:01:59] [02puppet] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/vbiAS [01:02:01] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-3 [01:04:09] !log set table_definition_cache and table_open_cache to 10000 on db6/db7 [01:04:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:15:23] PROBLEM - cp8 Current Load on cp8 is WARNING: WARNING - load average: 1.29, 1.96, 1.42 [01:18:22] RECOVERY - cp8 Current Load on cp8 is OK: OK - load average: 0.83, 1.50, 1.34 [01:58:02] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [02:04:11] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [02:10:36] PROBLEM - cp8 Current Load on cp8 is WARNING: WARNING - load average: 1.63, 1.72, 1.50 [02:13:39] RECOVERY - cp8 Current Load on cp8 is OK: OK - load average: 1.13, 1.45, 1.43 [03:38:18] PROBLEM - cp8 Current Load on cp8 is CRITICAL: CRITICAL - load average: 3.25, 2.25, 1.69 [03:41:21] PROBLEM - cp8 Current Load on cp8 is WARNING: WARNING - load average: 1.47, 1.88, 1.64 [03:44:23] RECOVERY - cp8 Current Load on cp8 is OK: OK - load average: 1.40, 1.66, 1.60 [03:57:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [04:03:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [04:15:16] PROBLEM - cp8 Current Load on cp8 is CRITICAL: CRITICAL - load average: 2.15, 2.34, 1.97 [04:18:20] PROBLEM - cp8 Current Load on cp8 is WARNING: WARNING - load average: 0.93, 1.77, 1.82 [04:21:22] RECOVERY - cp8 Current Load on cp8 is OK: OK - load average: 1.43, 1.48, 1.68 [04:32:13] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 25.63, 20.73, 19.26 [04:35:14] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 16.89, 19.08, 18.91 [04:51:51] PROBLEM - cp8 Current Load on cp8 is WARNING: WARNING - load average: 1.52, 1.88, 1.75 [04:54:59] PROBLEM - cp8 Current Load on cp8 is CRITICAL: CRITICAL - load average: 2.02, 1.87, 1.76 [04:58:05] RECOVERY - cp8 Current Load on cp8 is OK: OK - load average: 1.21, 1.44, 1.60 [05:27:52] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [05:52:24] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:22:51] RECOVERY - bacula2 Bacula Private Git on bacula2 is OK: OK: Full, 4151 files, 12.07MB, 2020-05-04 06:20:00 (2.9 minutes ago) [07:04:36] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 2.18, 4.21, 3.38 [07:07:41] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 2.64, 3.16, 3.10 [07:14:58] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 22.17, 22.96, 20.26 [07:21:01] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 18.21, 19.72, 19.78 [07:33:18] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 19.97, 22.40, 21.24 [07:36:17] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 12.49, 19.14, 20.29 [07:37:44] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [07:43:40] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:58:46] hi, i can not login in my wiki https://dish.miraheze.org, reset password not helped me [07:59:47] Dish: hi, please remove all your cookies that have .miraheze.org in them [08:05:35] thanks, now its ok [08:05:54] Dish: great! sorry for the inconvenience! [08:09:09] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [08:12:16] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [08:16:32] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 15.68, 20.22, 20.78 [08:22:40] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 26.62, 23.70, 21.97 [08:28:47] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 18.02, 21.68, 21.78 [08:36:49] RhinosF1: stop ranting about https://publictestwiki.com/wiki/Special:DoubleRedirects and use Project:Support_Desk [08:47:03] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 4 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [08:49:33] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 14.70, 17.60, 20.04 [08:53:18] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:07:00] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 22.06, 22.53, 21.60 [09:13:07] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 28.44, 25.52, 23.14 [09:16:06] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 16.20, 22.51, 22.48 [09:22:09] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 33.56, 25.20, 23.17 [09:25:14] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 19.93, 22.97, 22.71 [09:28:31] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [09:31:13] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 24.43, 21.41, 21.84 [09:34:23] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 19.58, 20.89, 21.62 [09:34:46] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [09:40:24] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 24.93, 21.13, 21.27 [09:41:05] ZppixBot: I nearly lost you in icinga [09:41:12] paladox: can we downtime the alert? [09:41:45] [02landing] 07AlirezaIvaz reviewed pull request 03#25 commit - 13https://git.io/Jfs5g [09:41:47] we can, but then that'll hide serious problems. [09:42:43] paladox: then that might be a bad idea. cloud1 load is known though, right? [09:43:04] yes [09:44:16] paladox: then downtiming the cloud1 load alert would hide only that right? That's not a serious issue. Either that or we need to fix it. [09:44:36] yes, but why do we need to hide it? [09:45:20] paladox: because it's flapping and going off constantly to the point I'm missing messages in the middle that I do want to see. [09:46:01] Messages like? [09:46:16] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 23.50, 22.54, 22.12 [09:46:25] paladox: the zppixbot one [09:47:42] You couldn't possibly have almost lost it.... it pinged you, the point of a backscroll is for you to go back and find your pings. [09:48:34] which mostly are from 'CRITICAL:', my point is the alert is going off for a known issue. [09:49:19] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 26.90, 23.78, 22.65 [09:52:17] downtimed for 3 hours [09:53:10] paladox: thanks, please extend if no fix as this is a days old issue. [09:53:36] * RhinosF1 as said sees no point in a critical alert for a known issue that has zero impact as far as he can see [09:57:09] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 4 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [09:57:56] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 6.99, 5.33, 3.76 [10:03:23] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:04:03] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 1.35, 3.22, 3.34 [10:17:11] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 2.20, 3.61, 3.49 [10:20:18] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 3.33, 3.08, 3.27 [10:38:55] [02miraheze/ManageWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfsFo [10:38:57] [02miraheze/ManageWiki] 07JohnFLewis 030314da3 - collect all NS data, not just main [10:39:51] [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfsF1 [10:39:53] [02miraheze/mediawiki] 07JohnFLewis 035e1bb2f - MW [10:48:55] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 3.22, 4.17, 3.59 [10:52:03] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 3.03, 3.67, 3.50 [10:53:04] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [10:54:05] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [10:55:07] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 2.32, 3.02, 3.28 [10:56:08] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [10:57:15] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [11:21:46] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 2.45, 3.42, 3.29 [11:24:50] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 3.22, 3.26, 3.24 [11:38:00] [02miraheze/ManageWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Jfsxc [11:38:02] [02miraheze/ManageWiki] 07JohnFLewis 035e6888b - fix errors with permission logging and autopromote [11:38:15] [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfsxC [11:38:17] [02miraheze/mediawiki] 07JohnFLewis 03f8dc3bd - MW [12:17:33] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [12:23:57] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:46:08] Hello Nia! If you have any questions, feel free to ask and someone should answer soon. [12:48:40] Hi! I am the owner / beaureucrat for a wiki 'atlantisboard.miraheze.org' But when I try to access it, it says it cannot be found on the miraheze server. It's listed for Adoption, but if I click on the link there, I just end up at the Miraheze Meta home page. Could someone please check what is going on? :O [12:48:51] hi Nia [12:48:55] I will take a look into that [12:49:26] If it helps, my admin name on the wiki is 'saatlantis' [12:49:48] Nia: your wiki was marked as deleted because of extensive inactivity, I've gone and undeleted it for you :) [12:49:55] Thank youuuuuu [12:50:06] is it possible to not delete this wiki ever? [12:50:12] Nia: if your wiki is made to be read and won't get many edits you can request an exemption to the dormancy policy [12:50:28] Nia: you can read https://meta.miraheze.org/wiki/Dormancy_Policy/Exemptions for more :) [12:50:30] [ Dormancy Policy/Exemptions - Miraheze Meta ] - meta.miraheze.org [12:50:46] Perfect [12:50:53] thank you for the quick response [12:50:59] Is there a way to request a backup as well? [12:51:08] Nia: you can backup yourself using Special:DataDump [12:51:41] Cool, you guys rock. Stay safe and healthy! <3 [12:52:19] Nia: you too :D have a nice day [12:57:24] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 2.47, 3.55, 3.24 [13:00:01] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 22.01, 23.08, 24.66 [13:00:31] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 1.27, 2.67, 2.96 [13:07:37] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 3.71, 4.42, 3.90 [13:16:56] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 7.39, 7.40, 6.85 [13:19:17] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 104.02 ms [13:20:03] RECOVERY - db6 Current Load on db6 is OK: OK - load average: 4.63, 6.37, 6.56 [13:29:39] * hispano76 greetings [13:30:58] hi hispano76 [13:31:55] Good morning [13:32:04] Hi AmandaCath [13:33:12] hi AmandaCath [13:33:31] I just cleaned out a large chunk of an extensive request wiki backlog, but more eyes are still needed [13:33:31] hello AmandaCath [13:33:38] See also https://meta.miraheze.org/m/4K5 [13:33:53] [ Community noticeboard - Miraheze Meta ] - meta.miraheze.org [13:35:25] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 6.74, 7.25, 7.02 [13:36:16] AmandaCath: hopefully not for long, https://phabricator.miraheze.org/T5105 [13:36:17] [ ⚓ T5105 Investigate and Implement basic Machine Learning concepts for automatic wiki creation ] - phabricator.miraheze.org [13:36:33] (Ik you're aware, just saying though :) [13:38:04] :) [13:39:00] morning/afternoon everyone [13:41:52] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 10.07, 8.16, 7.40 [13:44:11] AmandaCath: Looking at the ip you just revertee [13:44:57] RhinosF1: ?? [13:44:57] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 5.75, 7.36, 7.26 [13:45:28] AmandaCath: on meta. You just reverted an ip. Looking into the ip. [13:45:49] Yeah, I thought it's just run of the mill vandalism [13:45:55] Doesn't raise any red flags for me [13:46:45] * RhinosF1 can’t see it used before [13:51:15] Looks like a few vandal edits on wmf before [13:51:29] If they want more fun, i’ll find a hammer [13:54:32] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 2.27, 3.56, 3.94 [13:55:09] AmandaCath: please don't stall extension requests [13:55:50] Reception123: oh, I thought anything blocked by security review was de facto stalled because of the extensive backlog [13:55:57] " we use Stalled for tasks that are waiting on an external entity to respond before any further action from us can be taken." [13:56:18] AmandaCath: true, we used to do that [13:56:23] but now we don't anymore [13:56:59] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGe1 [13:57:01] [02miraheze/MirahezeMagic] 07translatewiki 0382e2196 - Localisation updates from https://translatewiki.net. [13:57:01] [ Main page - translatewiki.net ] - translatewiki.net. [13:57:02] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±11] 13https://git.io/JfGeM [13:57:04] [02miraheze/ManageWiki] 07translatewiki 031f54f55 - Localisation updates from https://translatewiki.net. [13:57:04] [ Main page - translatewiki.net ] - translatewiki.net. [14:03:50] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.63, 7.98, 7.46 [14:06:03] Hmm... are requests to have a wiki redirect to another wiki allowed? [14:06:21] Reference, RequestWiki #11894 [14:06:35] no, but we do accept requests to have wikis added to the ssl repo (to redirect to another wiki) [14:07:09] So should I direct them to Phabricator for that request? [14:08:55] ZppixBot: don't set the world on fire, unless it gets rid of the backlog :P [14:10:52] JohnLewis: I'm a bot, Zppix is my master [14:11:22] oh come on JohnLewis no fun [14:11:24] Zppix: 2020-05-01 - 14:22:05CDT tell Zppix Please see your email again, and let me know [14:12:10] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ufw-allow-tcp-from-any-to-any-port-5666] [14:12:59] [02miraheze/CreateWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGv4 [14:13:01] [02miraheze/CreateWiki] 07translatewiki 039684cb2 - Localisation updates from https://translatewiki.net. [14:13:01] [ Main page - translatewiki.net ] - translatewiki.net. [14:14:47] Zppix: Maybe get ZppixBot to ignore Not-* :P [14:15:37] Zppix: URL ignore takes exact nicknames [14:15:43] Examknow: ^ [14:15:57] * RhinosF1 ‘s brain is somehwere else [14:16:14] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 6.09, 4.60, 4.07 [14:16:46] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 5.32, 7.42, 7.53 [14:16:51] oh [14:19:23] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 3.14, 3.83, 3.86 [14:19:27] Examknow: I made it ignore for welcome.py but nothing else [14:21:01] ah okay [14:21:14] not my biggest concern [14:25:04] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [14:33:27] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.06, 7.49, 7.29 [14:35:26] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 5.58, 4.41, 4.00 [14:36:37] RhinosF1: our URL module is not the same as upstreams so if you have to modify it to ignore it go for it [14:37:04] Zppix: It’s somewhere in my plan for this year [14:39:54] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 4.70, 6.23, 6.83 [14:42:34] Well, now Sourav has put some Bengali-script on AN abs if the machine translation is accurate for these characters, it's just more of his usual trolling [14:42:48] and if* [14:42:57] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.50, 7.58, 7.26 [14:44:11] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JfGUa [14:44:13] [02miraheze/MirahezeMagic] 07paladox 033f03ea2 - Erase data from user_* tables [14:44:14] [02MirahezeMagic] 07paladox created branch 03paladox-patch-2 - 13https://git.io/fQRGX [14:44:16] [02MirahezeMagic] 07paladox opened pull request 03#119: Erase data from user_* tables - 13https://git.io/JfGUV [14:44:33] And now they say that they want to be globally locked and in the next sentence are begging for a final chance [14:44:44] That's blatant trolling if I'll ever see it [14:44:47] AmandaCath: I have a few words for that [14:46:12] Reception123: out of curiosity, why not propose a global community ban given the crosswiki disruption? [14:48:52] [02MirahezeMagic] 07paladox closed pull request 03#119: Erase data from user_* tables - 13https://git.io/JfGUV [14:48:53] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGTT [14:48:55] [02miraheze/MirahezeMagic] 07paladox 033f15229 - Erase data from user_* tables (#119) [14:48:56] [02MirahezeMagic] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/fQRGX [14:48:58] [02miraheze/MirahezeMagic] 07paladox deleted branch 03paladox-patch-2 [14:49:27] AmandaCath: save time [14:49:40] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfGTq [14:49:41] [02miraheze/mediawiki] 07paladox 03cbbd577 - Update MirahezeMagic [14:50:30] Personally I have a feeling we will be back here in the near future if he evaded his Meta ban, so ultimately a global CBAN will save time in the future [14:51:04] * RhinosF1 doesn’t have time for GCBAN sorting [14:51:19] * RhinosF1 also thinks we should have a global ban policy [14:51:43] We do have a global ban policy: community consensus [14:52:45] That’s not specific [14:53:25] I generally don't support global bans being implemented without community consensus though [14:54:00] If we are doing "Terms of Use Ban" we should at least state in a general sense which clause(s) of the ToU were violated [14:54:07] Oh, I mean one that has criteria for a ban, requirenents fot consensus etc. [14:54:14] Which shouldn't violate any privacy [14:54:28] AmandaCath: if it’s got as far as a ToU ban, you can either guess or we can’t say [14:54:34] Or both [14:54:50] well, I can't guess anything about the two currently listed [14:55:22] You need to look closer at the most recent [14:55:22] !log root@jobrunner1:/srv/mediawiki/w/extensions/SocialProfile# sudo -u www-data php UserBoard/maintenance/migrateOldUserBoardUserColumnsToActor.php --wiki=atrociousyoutuberswiki --force [14:55:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:55:36] The first we can’t say as far as I know [14:56:49] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 6.04, 7.83, 7.79 [14:56:51] I would think that just stating which clauses were violated, leading to the ban, wouldn't violate any privacy [14:57:10] Let's show WMF Trust & Safety the right way to go about these things [14:57:41] Any kind of extreme action made based on secret evidence generally won't go over well [14:58:27] AmandaCath: The Joaquinito one was based on Section 8 of the ToU [14:58:37] well... I meanit could violate the privacy AmandaCath [14:58:42] Based on significant long term issues [14:59:13] Well, I don't like the idea that "Miraheze can just ban anyone if it feels like it" [14:59:21] AmandaCath what if someone reported you and lets say the user is called User a. And wikimedia say it's under the "no threats clause". You would instantly know it was User A. [14:59:41] Putting there life in danger because there are some individuals who will target people who report them. [14:59:50] Which is what I interpret "it's sole discretion" to mean [15:00:13] Paladox: obviously cases of real-life danger would and should be the exception to any rules [15:00:20] All ToU action is under Section 8, baring Section 8 of the PP [15:00:23] AmandaCath which is the case. [15:00:24] AmandaCath: The barrier is very high and the investigation into Joaquinito01 took 10 weeks [15:01:30] I just looked at Joaquinto01 and I don't see anything... obviously the material in question may be deleted [15:02:00] But I still don't like the idea of "Miraheze may ban you for any or no reason if it wants to" [15:02:16] Which is what I interpret ToU 8 to be reading [15:02:16] i don't like that either [15:02:21] It’s not deleted mostly, it’s just not clearly linked [15:02:36] AmandaCath: The barrier for ToU action is very high [15:03:12] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 5 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [15:03:33] I understand that, but there still should be a public reason for banning under ToU [15:03:48] And there should be a set of criteria for which a ToU ban would be considered [15:04:20] Like I said, Clause 8 reads to me like it's saying that "MH may ban you for any or no reason if it feels like it" [15:04:31] AmandaCath: I can think of two reasons listed within section 8 as examples that Joaquinito fits [15:04:47] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 7 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [15:04:51] As it was at the time of the ban [15:05:02] which is? [15:05:48] paladox: “Posting illegal content or harassment on a Wiki” and “Excessive violation of this or other Miraheze policies” [15:06:06] https://meta.miraheze.org/w/index.php?title=Terms_of_Use&oldid=93157#8._Access_Restrictions was applicable at the time [15:06:08] [ Terms of Use - Miraheze Meta ] - meta.miraheze.org [15:06:23] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.56, 7.29, 7.28 [15:06:23] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:06:45] Well, see, "posting illegal content" should be the ban reason [15:07:44] Also FYI we've got more Sourav trolling on our hands [15:07:50] AmandaCath: we don’t make that public nor do we have to. They are multiple example reasons given in the ToU. I can assure you, ToU action is not done lightly. [15:08:39] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 6 minutes ago with 1 failures. Failed resources (up to 3 shown): Package[nagios-plugins] [15:09:40] I'm just a big pusher of transparency, and IMHO just a generalized statement such as "user engaged in harassment of other users" or "user posted in illegal content" is preferable over just "ToU Violation" [15:10:15] Generalized statements like that don't violate any privacy [15:10:59] AmandaCath: It’s not that simple. You say that and people go looking for harrasment which makes the situation worse or the banned user might know the reporter who is privately complaining [15:11:43] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [15:11:50] Those who are accused have a right to know who is accusing them, don't they? [15:12:04] And they have a right to know exactly what they are being accused of [15:12:45] They do, as far as I'm aware if the person banned emails we can tell them why they were banned [15:12:50] But not publicly [15:12:51] cc JohnLewis ^ [15:13:00] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 4.61, 6.81, 7.18 [15:13:13] AmandaCath: No, the identity of the accuser is private. Why they were banned is a matter between Miraheze and the banned user. [15:13:33] ^^ [15:13:40] In general, ToU bans would be final and unlikely to be succesfully appealed. [15:13:44] Yes, we discuss it in private where appropriate. Each situation is complex and sensitive. It may also come down from the Board where and when such private and sensitive matters can be discussed publicly [15:13:53] the accuser must stay private or else people would be afraid to come forward [15:14:21] And if a person is banned pursuant to the ToU it's unlikely they wouldn't know why, but if they don't they can email. [15:14:22] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [15:14:50] A ToU ban would only be overturned based on proceedural irregularity (and yes, no evdience/falsified is an irregularity) [15:15:09] What JohnLewis said [15:15:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGID [15:15:15] [02miraheze/services] 07MirahezeSSLBot 03a3bc65e - BOT: Updating services config for wikis [15:15:36] but they are the final option [15:15:49] we don't just ToU ban anyone, it is a very serious thing that is not taken lightly at all [15:15:52] I'm surprised that the accused would not have a right to know their accuser(s), but maybe that's a UK thing [15:16:09] I can think of one option after but that’s unprecedented [15:16:11] I'd wonder how that affects court cases, though [15:16:13] well this isn't exactly a court of law [15:16:22] and users have the right to anonymity if they wish [15:16:27] AmandaCath: It’s not a court of law [15:16:46] It's not a UK thing, we'd just withhold it unless we need to release it [15:17:24] This information would not be withed from competent authorities and we would comply with any court orders, etc. [15:17:34] but unless that happens we keep accusers private [15:18:16] I can respect that, it's just different [15:18:41] * RhinosF1 respectfully suggests it might be time to put an end to this topic. [15:19:11] AmandaCath: well as I said it's to protect users and not to discourage reporting of inappropriate behavior [15:19:18] RECOVERY - db6 Current Load on db6 is OK: OK - load average: 5.73, 6.07, 6.70 [15:19:29] I don't follow legal cases unless the topic is related to my field of work, but from what I understand Canada does something in between where the accused knows the identity of accuser but the accuser identity is not made public [15:19:55] well as I said, this isn't a court of law [15:20:13] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 3.71, 3.36, 4.00 [15:20:40] Agree with RhinosF1 that this is not going far, but I do value hearing and learning about other perspectives [15:22:03] This isn’t going far because the policy is like that. I don’t see any senario where legally the reason would be released execpt via a court of law to a limited group of people. [15:22:44] (well for the reason it can be given to the banned user if requested) [15:22:53] but as John says it depends on the case and each is different [15:23:09] why do we have to have LTAs [15:23:12] ?? [15:23:21] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 4.43, 3.64, 3.97 [15:23:27] Reception123: I mean full reasoning and evidence. Even then, it would have to be heavily redacted and simplified [15:23:42] Examknow: because we have humans [15:23:44] yeah [15:24:55] So the accused can't even see the full the evidence against them? [15:25:50] AmandaCath: without a court order or agreement of the accuser, anything that could reveal the accuser would have to be removed. [15:26:32] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 3.47, 3.48, 3.85 [15:26:40] I would be very surprised if they didn’t know why though [15:27:00] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 4.96, 6.53, 6.88 [15:27:02] Hm, that's an intriguing perspective [15:27:45] AmandaCath: well it's not intriguing to protect the accuser's identity [15:27:50] ^ [15:28:08] It's intriguing that even the accused doesn't know who is accusing them [15:28:46] I've only seen that done in cases of death threats or the like, which fortunately don't happen frequently over here [15:29:21] Well if say we revealed the identity of the accuser they may be prone to harassment from the person who violated the ToU on other websites for having accused them and getting them banned [15:29:28] so we don't want to discourage reporting users violating policies [15:29:49] I mean if you’ve done harrassed someone, you know who it is. If you’ve done someting and there’s enough evidence for a ToU ban and it’s serious enough, you likely know. [15:30:02] True [15:30:17] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.53, 6.75, 6.85 [15:30:28] But it makes it hard for outsiders to understand and see that it was legitimate [15:31:00] AmandaCath: outsiders aren’t supposed to know about private evidence and issues. [15:31:08] That’s kinda the point [15:31:22] Also would like to reiterate that ToU bans are quite rare [15:31:33] the preferred method is Stewards looking into things [15:31:38] ToU is only applied in extreme cases [15:32:18] ^ [15:32:45] I guess as long as long as we don't do what WMF T&S notoriously does by saying "office bans are final and we won't even consider appeals from the banned party under any circumstances" [15:32:48] Then we are okay [15:33:17] Well it all depends on the circumstances [15:34:18] AmandaCath: John’s answered that. If there is either new evidence or the previous can be discounted, a review may be considered [15:34:51] Hello skhsourav! If you have any questions, feel free to ask and someone should answer soon. [15:34:58] halo [15:35:14] can someone please worldlyblock me? [15:35:29] JohnLewis: ^ [15:35:42] hi sir [15:35:46] Ban evasion s [15:35:47] skhsourav: you want to be globally locked? [15:35:49] is examknow here? [15:35:54] JohnLewis blocked :P [15:35:58] they want a global block [15:36:08] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 2.69, 4.35, 4.13 [15:36:12] paladox: I think he means lock [15:36:14] err block not blocked [15:36:40] skhsourav: Evading bans on IRC channels will not help your case [15:36:57] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 5.87, 7.26, 7.12 [15:39:09] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 3.20, 3.81, 3.94 [15:39:20] skhsourav: You were banned from this channel for not respecting the Code of Conduct the other day. If you want to be globally locked please say so *clearly* (i.e. "I would like to be globally locked") on Stewards noticeboard. [15:40:35] ^ [15:40:45] okayokay i uderstand sir [15:41:39] wtf?? [15:42:08] maybe a reference to https://www.youtube.com/watch?v=3G0j_ERk65k lol [15:42:08] [ YouTube ] - www.youtube.com [15:42:23] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 6.94, 6.59, 5.15 [15:42:41] !ops should probably +b that range [15:42:51] For ban evasion if nothing else [15:43:24] .gj Reception123 [15:43:24] You're doing good work, Reception123! [15:43:31] AmandaCath: I banned all of his range on ##Examknow [15:43:39] he found another one today [15:44:04] AmandaCath: :) [15:49:28] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 9.13, 7.35, 7.20 [15:50:49] PROBLEM - cp6 Stunnel Http for test2 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [15:53:36] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 6.14, 7.72, 7.49 [15:54:31] PROBLEM - cp6 Stunnel Http for test2 on cp6 is WARNING: HTTP WARNING: HTTP/1.1 404 Not Found - 322 bytes in 0.001 second response time [15:55:28] Uh oh icinga [15:56:46] PROBLEM - db6 Current Load on db6 is CRITICAL: CRITICAL - load average: 8.17, 8.02, 7.64 [15:57:05] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGtQ [15:57:07] [02miraheze/puppet] 07paladox 038baef66 - Fix [15:59:52] PROBLEM - db6 Current Load on db6 is WARNING: WARNING - load average: 4.62, 6.55, 7.13 [16:00:18]