[00:01:05] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3952 MB (16% inode=93%); [00:01:32] RECOVERY - cp8 Disk Space on cp8 is OK: DISK OK - free space: / 3594 MB (18% inode=93%); [00:05:20] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 19.13, 21.18, 16.81 [00:08:20] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 14.71, 18.26, 16.44 [00:57:46] 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] [01:03:52] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [01:25:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGzj [01:25:14] [02miraheze/services] 07MirahezeSSLBot 037abae63 - BOT: Updating services config for wikis [01:37:53] 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] [01:43:54] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [03:16:04] 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] [03:22:09] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [04:47:22] 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:02:56] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:22:19] [02mw-config] 07MusikAnimal opened pull request 03#3062: Define $wgGoogleSiteVerificationKey on solarawiki - 13https://git.io/JfGw6 [05:30:17] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGwM [05:30:18] [02miraheze/services] 07MirahezeSSLBot 033e69bfa - BOT: Updating services config for wikis [05:50:42] [02mw-config] 07Reception123 commented on pull request 03#3062: Define $wgGoogleSiteVerificationKey on solarawiki - 13https://git.io/JfGwj [05:58:48] [02miraheze/puppet] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGrY [05:58:50] [02miraheze/puppet] 07Reception123 03cc71d1c - rm southparkfan from stewards Per resignation: https://meta.miraheze.org/w/index.php?title=Stewards%27_noticeboard&curid=662&diff=105333&oldid=105267 [05:58:53] [ Difference between revisions of "Stewards' noticeboard" - Miraheze Meta ] - meta.miraheze.org [07:16:57] RhinosF1: hi [07:19:46] Reception123: can you copy https://quirc.miraheze.org/wiki/MediaWiki:UserInfo.js to meta [07:19:47] [ MediaWiki:UserInfo.js - QuIRC ] - quirc.miraheze.org [07:20:00] Alert to Miraheze Staff: It looks like the icinga-miraheze bot has stopped! Ping !sre. [07:20:01] https://meta.miraheze.org is 03UP03 [07:20:05] https://icinga.miraheze.org is 03UP03 [07:20:21] Reception123: ^ can you also restart the echo [07:20:31] !shutup icinga [07:20:31] I will not report Icinga incidents [07:20:35] *rehash [07:20:36] Rehashing...... [07:20:45] RhinosF1: echo? [07:21:04] Reception123: icinga irc echo bot [07:21:17] ah [07:21:21] Preferably stop it for about 2-3 mins then start again [07:21:23] Reception123: ^ [07:21:32] RhinosF1: I don't think I want to :P [07:21:53] Reception123: it’s crashed and I think disconnected [07:22:02] net splits it seems [07:22:18] it might be mirahezebots_ but i hate underscores in names anyway [07:23:41] I've got no idea what it's called [07:23:48] need to check [07:24:02] Reception123: a hard restart (shutoff wait and start) will fix it [07:24:19] RhinosF1: I know, but I don't know the service name [07:25:03] .github miraheze/puppet [07:25:03] https://github.com/miraheze/puppet [07:25:29] yeah was trying to find it [07:25:55] Reception123: one of https://github.com/miraheze/puppet/blob/cc71d1c7b8bbb83128072a75c0e9c11b30816c20/manifests/site.pp#L89 [07:25:56] [ puppet/site.pp at cc71d1c7b8bbb83128072a75c0e9c11b30816c20 · miraheze/puppet · GitHub ] - github.com [07:26:11] I’d guess irc [07:26:17] RhinosF1: ircecho [07:26:28] [02YouTube] 07Elaeagnifolia opened pull request 03#5: Enable external sites on the YouTube ext - T5535 - 13https://git.io/JfG6M [07:26:30] Or that [07:26:31] !log stopped and started ircecho (icinga) [07:26:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [07:26:37] And welcome back [07:26:42] !speak [07:26:43] I will now report events to this channel [07:26:49] !shutup rc [07:26:49] I will not report MirahezeRC incidents [08:15:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGPq [08:15:14] [02miraheze/services] 07MirahezeSSLBot 03f5d4a06 - BOT: Updating services config for wikis [08:42:18] [02YouTube] 07Reception123 commented on pull request 03#5: Enable external sites on the YouTube ext - T5535 - 13https://git.io/JfGXs [08:42:27] [02YouTube] 07Reception123 edited a comment on pull request 03#5: Enable external sites on the YouTube ext - T5535 - 13https://git.io/JfGXs [09:05:10] Reception123: can you copy https://quirc.miraheze.org/wiki/MediaWiki:UserInfo.js to meta [09:05:11] [ MediaWiki:UserInfo.js - QuIRC ] - quirc.miraheze.org [09:14:01] RhinosF1: can't you :) why am I needed? [09:38:47] Reception123: https://meta.miraheze.org/wiki/IRC/Draft [09:38:48] [ IRC/Draft - Miraheze Meta ] - meta.miraheze.org [09:46:36] k [09:47:40] Reception123: shall I merge with main page [09:48:00] RhinosF1: let me take a closer look and compare [09:48:53] RhinosF1: just saying #miraheze-cvt-meta is a very inappropriate name seeing as CVT is opt-out on Meta [09:49:07] RhinosF1: I'd rather have #miraheze-feed-meta [09:49:24] Reception123: that's not my call, it's the name of the channel [09:49:34] RhinosF1: who created it? EK? [09:49:37] ye [09:49:45] he spoke to john first [09:49:48] RhinosF1: ok, I'll ask him to change that [09:50:10] Reception123: can I sync the page and change after or? [09:50:27] RhinosF1: yeah I'm just still reviewing first [09:50:56] RhinosF1: I don't think we should keep records of wiki-specific channels on Meta, it's not our business [09:51:19] Reception123: I think it's a good idea. personally [09:51:59] I think it's better if individual wikis advertise their own channels, we shouldn't be in charge of making a list of them [09:52:50] Reception123: remove that section then [09:53:15] RhinosF1: ok the rest LGTM, the cvt-meta is the current name so you can leave it but I'll talk to EK about changing that [09:53:24] you can't have a cvt channel for a wiki that is opt-out from CVT [09:53:33] ye [09:55:46] RhinosF1: what flooding are you doing? [09:55:57] Reception123: marking stuff for translation [09:56:00] ah I see [10:33:01] Hello wm-bot5156! If you have any questions, feel free to ask and someone should answer soon. [11:25:17] Hi there ! [11:26:57] 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] [11:29:16] I cannot log anymore into my Wiki. [11:30:12] I get a message saying that the connection has been canceled to prevent my session to be hacked. [11:30:25] AM I in the right place to get some support ? [11:30:58] Please clear your cookied [11:32:55] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:52:01] Good morning [12:57:10] !log update flow_tree_revision set tree_orig_user_ip = NULL where tree_orig_user_ip = '0.0.0.0'; [12:57:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [12:57:25] !log update flow_revision set rev_mod_user_ip = NULL where rev_mod_user_ip = '0.0.0.0'; [12:57:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [12:57:34] !log update flow_revision set rev_edit_user_ip = NULL where rev_edit_user_ip = '0.0.0.0'; [12:57:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [12:57:40] !log update flow_revision set rev_user_ip = NULL where rev_user_ip = '0.0.0.0'; [12:57:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [12:57:49] PROBLEM - wiki.zymonic.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.zymonic.com' expires in 15 day(s) (Thu 21 May 2020 12:50:57 GMT +0000). [12:58:38] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfG7u [12:58:39] [02miraheze/ssl] 07MirahezeSSLBot 031c78b32 - Bot: Update SSL cert for wiki.zymonic.com [13:01:39] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JfG7K [13:01:41] [02miraheze/puppet] 07paladox 0344c16df - Revert "Revert "salt: Stop salt-minion/master (#1351)"" This reverts commit 25dc849edd69fbb0996afaefb308f329b242f0e0. [13:03:56] RECOVERY - wiki.zymonic.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.zymonic.com' will expire on Mon 03 Aug 2020 11:58:31 GMT +0000. [13:33:16] !log MariaDB [atrociousyoutuberswiki]> update recentchanges set rc_ip = '' where rc_ip = '0.0.0.0'; [13:33:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [13:37:23] 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] [13:52:29] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [13:57:31] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGbv [13:57:32] [02miraheze/puppet] 07Southparkfan 037d0c4c1 - Absent salt-master + remark [13:58:14] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfGbI [13:58:15] [02miraheze/puppet] 07Southparkfan 03aba9d99 - Absent salt-master + remark [13:58:59] SPF|Cloud: i assume the bug from the other day [13:59:21] RhinosF1: https://saltexploit.com [13:59:26] [02mw-config] 07MusikAnimal commented on pull request 03#3062: Define $wgGoogleSiteVerificationKey on solarawiki - 13https://git.io/JfGbL [13:59:27] [02mw-config] 07MusikAnimal closed pull request 03#3062: Define $wgGoogleSiteVerificationKey on solarawiki - 13https://git.io/JfGw6 [14:00:00] and I do not feel confident running it the way we currently did [14:00:33] [02mw-config] 07Reception123 commented on pull request 03#3062: Define $wgGoogleSiteVerificationKey on solarawiki - 13https://git.io/JfGbs [14:01:21] Ack [14:01:54] We're not going to use salt anymore, i've already eyed a replacement that seems more secure. [14:03:02] at least not until we change somethings. [14:04:16] Sounds extremely reasonable [14:05:55] Reception123: where’s better? [14:08:19] RhinosF1: hm? [14:08:23] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 21.05, 22.34, 19.37 [14:08:42] Reception123: the comment on github you just made to musikanimal [14:09:13] RhinosF1: oh, I'm not sure but certainly not edit IMO [14:09:21] I wouldn't look for it there tbh [14:09:35] I'm not sure it really belongs in any of the current categories [14:09:43] Reception123: I agree. [14:11:25] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 25.28, 21.35, 19.35 [14:14:27] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 16.77, 19.91, 19.21 [14:31:37] RhinosF1: regarding "Miraheze redesign"... I'd say those current colors are too bright and in fact quite shocking [14:31:51] I think the current page looks fine [14:32:43] Examknow: why did you create wiki request #11909? [14:32:52] They didn't provide any details [14:34:03] AmandaCath: When we demand details then we get a backlog [14:34:27] unless it seems suspicious I usually let it through [14:34:32] Examknow: actually, now that I look at it, that request is clearly a sock of Sourav Hadler [14:34:32] err [14:34:42] Notice the same invalid custom domain [14:34:47] wtf?????? [14:34:48] you don't accept wikis because you want to clear the backlog [14:35:21] you accept them because they provide a description [14:35:23] The same invalid custom domain of simply ".Org" is the giveaway [14:35:34] All of Sourav's requests have had that [14:35:57] AmandaCath: That may be the system... [14:36:33] Examknow: no, it's not. No other wiki requests have that even when they have a CD [14:36:44] It's clearly something that's done manually [14:36:50] yeah i see it [14:36:59] fuck I just approved Sourav's request [14:37:06] * Examknow smacks himself in the face [14:37:27] well maybe now that he has a wiki he will leave us alone [14:37:45] I'll decline the one under the master account [14:37:50] Since he doesn't need to [14:37:55] two* [14:38:09] go ahead [14:38:37] AmandaCath can you report on the steward discussion page? [14:38:50] The wiki should be deleted and the user should be banned [14:39:12] paladox: We probably need CU evidence to do that [14:39:22] JohnLewis: Could you run a CU? [14:39:44] Yeah, and I mean, I do want to see if he will leave us alone now that he has a wiki [14:39:56] But he is definitely out of rope from me [14:39:58] even then you should not be creating wikis without descriptions Examknow [14:40:04] the field is there for a reason [14:40:37] paladox: I used to not and then there was an RfC for me incorrectly declining requests [14:41:00] Also I'd say that "NK Mondal" is clearly WP:QUACKING [14:41:10] And therefore shouldn't require CU [14:41:59] AmandaCath: I would prefer to be extra sure. I myself have been wrongfully blocked for sockpuppetry on enwiki and it was not a fun experience, [14:43:30] Well, I think everyone knows that the enwiki CUs and SPI clerks sometimes just make stuff up [14:43:37] Just read Wikipediocracy [14:43:58] At least ARBCOM got rid of Bbb23 who was the most abusive [14:46:44] yeah he was the one who blocked me lol [14:46:52] I just gave an absolute final warning in no uncertain terms on Sourav's TP [14:47:11] AmandaCath: regarding babel, that’s the third time [14:47:49] JohnLewis, PuppyKun: can we nip the bud in sourav and end it? [14:49:04] Seriously, if he does anything else remotely disruptive after my final warning I just gave him... just globally lock the account [14:49:19] He's had enough time to wikilawyer his way out of sanctions [14:50:06] RhinosF1: I’m not available to do anything currently but I’ll take a look latee [14:50:30] we need a check user [14:50:43] Well, he had a chance and he rejected my message [14:50:47] yeah [14:50:50] JohnLewis: If I weren’t so involved, I’d block & close the discussion myself. [14:51:13] RhinosF1: The sockpuppetry is the final straw for me [14:51:24] ^ [14:51:44] That's why he's basically skating on water [14:52:21] Any additional disruptive action, even just one, from either the master or the sock should result in a global lock of both accounts [14:52:29] no one wants him here [14:54:03] JohnLewis: Do you see any issue with me closing the local discussion now? [14:54:16] Well, looks like MH just got a big complement [14:54:26] See request #11911 [14:56:10] lol [14:59:59] AmandaCath: the redesign is a test & work in progress [15:02:31] AmandaCath: You've got mail from our favorite sockpuppeteer https://meta.miraheze.org/w/index.php?diff=105582&oldid=105578&rcid=396780 [15:02:35] [ Difference between revisions of "User talk:Sourav Halder" - Miraheze Meta ] - meta.miraheze.org [15:03:11] Meh, more wikilawyering [15:03:25] yep [15:03:41] A shared IP would only explain a technical overlap/CU confirmation [15:03:52] But it doesn't explain the identical behavior [15:04:24] AmandaCath: Take note that Sourav Halder has already engaged in sockpuppetry on an RfA [15:04:47] and the steward on WMF says that he also engaged in sockpuppetry there [15:05:07] I don't see an RFA for him [15:05:29] on mh meta [15:05:58] Yeah, I don't see any adminship request [15:06:04] Unless it's been deleted [15:07:40] prob. archived [15:10:50] Examknow: RfIA [15:11:04] oh [15:13:33] AmandaCath: https://meta.miraheze.org/wiki/Requests_for_global_rights#Sourav_Halder.27s_Request_for_Interwiki_administrator [15:13:33] * RhinosF1 busy but if anyone wants to create a mess please ping [15:13:34] [ Requests for global rights - Miraheze Meta ] - meta.miraheze.org [15:14:42] Wow, why would anyone engage in sock/meat/canvassing on a request for something as "light" as interwiki admin [15:15:14] That's one of the only global rights that really isn't a big deal [15:15:20] AmandaCath: Who would spend this much time abusing Miraheze? [15:16:01] Yeah, they should've been globally locked days ago [15:16:19] But my email to stewards@ regarding this was never answered [15:18:55] AmandaCath: It was as soon as they got an oppose vote [15:30:41] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JfGpn [15:30:43] [02miraheze/MirahezeMagic] 07paladox 0304a7d37 - Set flow ip column to null [15:30:44] [02MirahezeMagic] 07paladox created branch 03paladox-patch-2 - 13https://git.io/fQRGX [15:30:46] [02MirahezeMagic] 07paladox opened pull request 03#120: Set flow ip column to null - 13https://git.io/JfGpW [15:37:25] 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] [15:43:30] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [15:56:51] 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] [16:12:25] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [16:13:10] !log delete redis atrociousyoutuberswiki key [16:13:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [16:18:01] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2641 MB (10% inode=93%); [16:23:07] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/JfGjl [16:23:08] [02miraheze/ssl] 07Reception123 031fdd5bd - add lama.madooa.org cert [16:43:05] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 24.69, 22.19, 19.83 [16:46:11] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 13.08, 17.93, 18.60 [17:46:32] !log MariaDB [atrociousyoutuberswiki]> truncate objectcache; [17:46:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:59:13] !log reset email on Maestro venerabile [17:59:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:00:18] Hello John can you do me a favor and check your email I sent you something important [18:12:33] !log > $cWJ = new CreateWikiJson( "dungeonsanddaddieswiki" ); $cWJ->resetWiki(); [18:12:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:24:29] Reception123: [18:24:32] MariaDB [mhglobal]> SELECT wiki_inactive_timestamp FROM cw_wikis WHERE wiki_dbname = 'dungeonsanddaddieswiki'; [18:24:32] +-------------------------+ [18:24:32] | wiki_inactive_timestamp | [18:24:33] +-------------------------+ [18:24:33] | 20200426010200 | [18:24:33] +-------------------------+ [18:24:33] 1 row in set (0.000 sec) [18:24:43] the wiki is marked as inactive because there is a timestamp in the DB [18:39:50] JohnLewis: but users should be able to uncheck it... [18:40:00] And ManageWiki shows it as if it was active [18:40:27] ManageWiki shows based on wiki_inactive, CW works on wiki_inactive_timestamp [18:40:46] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [18:42:17] JohnLewis: well then I presume if there was activity on the wiki after, it would automatically get removed by the script? [18:43:05] No, because the wiki isn't marked as inactive [18:43:18] Hello John are you available? I emailed you a few questions regarding something important. [18:43:48] I'm getting 503 errors for multiple wikis including meta [18:43:54] That happens alot [18:46:32] @leaccount which email account? [18:46:52] jon222TA@gmail.com [18:46:56] everything is down [18:47:24] Alert to Miraheze Staff: It looks like the icinga-miraheze bot has stopped! Ping !sre. [18:47:25] https://meta.miraheze.org is 03UP03 [18:47:28] JohnLewis your email is john@miraheze.org correct? [18:47:41] Yes [18:48:14] JohnLewis, Paladox: Every MH service has gone down [18:48:32] aware [18:50:10] bug of OVH o local? [18:52:50] !log reboot mw4 [18:55:23] things are back [18:55:54] @leaccount email got missed, looking now [18:56:14] paladox, JohnLewis: https://mobile.twitter.com/ovh_status/status/1257740860579602433 [18:56:15] [ Twitter ] - mobile.twitter.com [18:56:18] Lasted 10 mins [18:56:40] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2470 MB (10% inode=93%); [18:56:43] and that'll be why [18:56:48] again!? [18:56:50] ipv6 was only affected [18:57:02] paladox: why do you think I have it on my twitter [18:57:10] SPF|Cloud: that’s my thought [18:57:17] This is outage 3 [18:57:44] Gravelines is France [18:57:48] We're not in France [18:58:04] Isnt Miraheze hosted in Canada? [18:58:05] I think [18:58:07] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:58:12] UK [18:58:33] JohnLewis: or that. I didn’t read closely just linked to it [18:58:43] PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:58:47] I’ve just seen [18:59:04] PROBLEM - phab1 Puppet on phab1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:04] PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - db6 Puppet on db6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - rdb1 Puppet on rdb1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - services2 Puppet on services2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - cp7 Puppet on cp7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:09] PROBLEM - cp7 HTTP 4xx/5xx ERROR Rate on cp7 is WARNING: WARNING - NGINX Error Rate is 46% [18:59:10] PROBLEM - rdb2 Puppet on rdb2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:10] PROBLEM - mail1 Puppet on mail1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:10] PROBLEM - dbt1 Puppet on dbt1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:11] PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:59:55] PROBLEM - mon1 Puppet on mon1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [19:00:00] PROBLEM - db7 Puppet on db7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [19:00:53] PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [19:01:52] RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [19:02:07] RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [19:02:12] RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [19:02:12] RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [19:02:17] RECOVERY - db6 Puppet on db6 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [19:02:17] RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [19:02:17] RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [19:02:17] RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [19:02:18] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [19:02:18] RECOVERY - dbt1 Puppet on dbt1 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [19:02:56] RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:03:08] RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:03:59] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:04:12] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:05:06] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [19:05:07] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [19:05:12] RECOVERY - cp7 HTTP 4xx/5xx ERROR Rate on cp7 is OK: OK - NGINX Error Rate is 20% [19:13:40] JohnLewis: oh, well in that case the sitenotice is misleading.. what can we do about it? [19:13:51] Hello ja_! If you have any questions, feel free to ask and someone should answer soon. [19:15:12] Reception123: huh? [19:18:07] Reception123: just set timestamp to NULL where inactive is 0 and I'll get around to fixing it when I literally have any spare moment [19:20:04] @leaccount I've reviewed your email and discussed it with other stewards. All I can say unfortunately is you'll have to make a request to regain rights on wiki - reviewing the decision, I'm not able to overturn my original one as consensus on the wiki is unfortunately rather clear even taking into account previous editing history [19:20:44] I see [19:22:31] hey guys I got a noob question that I can't seem to find the answer for... I'm trying to add a user to my private wiki. This link is telling me to go to special user rights and add user... but when I load up the username I don't see any options to add them to the `member` group https://meta.miraheze.org/wiki/Special:UserRights [19:22:32] [ User rights - Miraheze Meta ] - meta.miraheze.org [19:23:01] But what about the other page that did not receive a verdict? [19:23:24] ja_ hi, did they log into the wiki? [19:23:37] they went to the link of the wiki's main page [19:23:43] is that sufficient? [19:23:53] (while logged in) they went to the wiki's main page [19:24:21] oh, yeh. [19:24:33] This page John: https://2b2t.miraheze.org/wiki/Ban_Status_of_Users_LordGalvatron_and_CremationEnthusiast [19:24:33] [ Ban Status of Users LordGalvatron and CremationEnthusiast - 2b2t Wiki ] - 2b2t.miraheze.org [19:25:25] This page did not receive any verdict or known clear consensus for these two [19:27:28] 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] [19:29:25] paladox, any thoughts? trying to add this user to my private wiki [19:29:51] !log rebuilding recent changes for atrociousyoutuberswiki [19:29:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:29:56] ja_ as long as the user visited your wiki logged in, they should show in the user list. Which wiki is this for? [19:30:26] @leonac I'll take a look at that in a short while [19:30:40] Thank you JohnLewis [19:31:43] !log MariaDB [mhglobal]> UPDATE cw_wikis SET wiki_inactive_timestamp = null WHERE wiki_inactive = 0; [19:31:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:32:34] paladox I see the user in the user list, but how do I give the user permission to the view the private wiki? [19:32:49] ja_ add the member group to the user. [19:33:10] [02MirahezeMagic] 07paladox closed pull request 03#120: Set flow ip column to null - 13https://git.io/JfGpW [19:33:11] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfZLC [19:33:13] [02miraheze/MirahezeMagic] 07paladox 03e7e5a1f - Set flow ip column to null (#120) [19:33:14] [02miraheze/MirahezeMagic] 07paladox deleted branch 03paladox-patch-2 [19:33:16] [02MirahezeMagic] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/fQRGX [19:33:34] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:33:54] paladox how do I add the member group to the user ... I see 'load user groups' , but no option to add [19:34:05] ja_ which wiki is this for? [19:34:12] infinig [19:34:44] ja_ you do that through Special:UserRights [19:34:57] I'm in there but see no option to add permissions [19:35:26] paladox I'm here https://meta.miraheze.org/wiki/Special:UserRights [19:35:26] [ User rights - Miraheze Meta ] - meta.miraheze.org [19:35:32] oh [19:35:36] you don't add them there [19:35:37] !log disabled a user on Phabricator [19:35:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:35:40] you add them on your wiki [19:35:42] so [19:35:54] here https://infinig.miraheze.org/wiki/Special:UserRights [19:35:55] [ Permission error - infiniG ] - infinig.miraheze.org [19:36:53] paladox bless your soul [19:37:00] :D [19:46:43] paladox the user is getting a 'permission error' ... I set their permission as a bot [19:47:00] ja_ you need to give them the "member" group [19:47:29] paladox do I have to create a member group? don't see that optioon [19:47:50]