[00:02:33] PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:03:06] oh noes, it's spreading! [00:08:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:12:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:12:33] RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [00:12:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:24:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:32:22] I made a change to the page on custom domains to help prevent confusion (as reported in discord) https://meta.miraheze.org/w/index.php?title=Custom_domains&curid=51&diff=58876&oldid=48200 [00:32:23] Title: [ Difference between revisions of "Custom domains" - Miraheze Meta ] - meta.miraheze.org [00:32:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:38:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [00:42:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:50:12] it's best to do so for attribution purposes [00:50:17] (copyright) [00:54:58] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [01:02:56] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:03:50] Hi [01:08:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [01:12:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:18:02] Hi [01:24:58] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [01:27:11] hi! [01:27:22] please can i have a backup copy of my wiki https://bootstrapping.miraheze.org [01:27:23] Title: [ bootstrapping ] - bootstrapping.miraheze.org [01:28:09] hello rain1 [01:28:12] hey [01:28:15] see https://meta.miraheze.org/wiki/Backups rain1 [01:28:16] Title: [ Backups - Miraheze Meta ] - meta.miraheze.org [01:28:51] can I requst it here? [01:29:03] i don't have the phabricator account ready [01:29:54] ah [01:31:18] You can log in with your Miraheze account by clicking on "Log in or register (and the Mediawiki logo and name)". https://phabricator.miraheze.org/auth/start/?next=%2F rain1 [01:31:19] Title: [ Login ] - phabricator.miraheze.org [01:32:30] It is preferable to do it in Phabricator for any Sysadmin to review your request. [01:32:56] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:35:58] rain1: understood? [01:38:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [01:38:20] i acant log in [01:38:27] o nphabricator.miraheze.org [01:38:30] on phabricator.miraheze.org * [01:42:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:54:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:02:58] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:08:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:12:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:24:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:32:58] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:38:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:42:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:54:58] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [03:02:56] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:08:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [03:12:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:24:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [03:32:56] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:38:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [03:42:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:54:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [04:02:58] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:08:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [04:12:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:24:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [04:32:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:38:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [04:42:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:54:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [05:02:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:08:10] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [05:12:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:24:57] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [05:28:10] Hi, I wonder whether I can have the same permissions as I have as User:開拓者 for User:The Pioneer, because there could be wikis like the weather wiki, where my Japanese user name is not allowed (but can take actions if I use the account The Pioneer instead). [05:28:39] The use of User:The Pioneer will be limited only to such cases if allowed. [05:29:06] I'm not sure, but either way, only a Steward can grant permissions [05:29:15] @The_Pioneer why can't you create your Japanese user name? [05:29:57] I mean, there could be some wikis where their policies ban using Japanese names; technically I can create an account though [05:31:06] #wiki-feed Only Blocked Message [05:31:08] 🤔 [05:31:27] ok [05:31:46] Sorry, that's because I'm performing auto blocks; flooder/bot doesn't seem to be working here [05:32:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:36:13] @Reception123 OK, I can wait for the Stewards' opinions on it. [05:38:09] I think we should divide the blocking record from document record. [05:38:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [05:39:06] @Tenpower what do you mean? [05:39:44] @Miraheze-IRC [05:40:04] Please Bot edit [05:40:31] Miraheze does not operate the bot [05:40:36] Uh, and yeah, and I also wish I could use both of them because I can work as a flooder with my subaccount (The Pioneer) and keep my main account (開拓者) available for other actions. [05:40:39] It's operated by @Zppix so you need to ask him [05:40:39] Hmm [05:42:10] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:42:23] Which will be very convenient in cases which I have to work for hours as a flooder. [05:54:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [06:02:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [06:12:12] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:24:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [06:32:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:38:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [06:42:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:54:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [07:02:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:08:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [07:10:35] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6105 [07:12:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:13:52] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+1/-0/±0] 13https://git.io/fAWDN [07:13:53] [02miraheze/dns] 07paladox 036d13727 - Add prfm.wiki zone [07:24:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [07:32:57] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:38:11] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [07:42:11] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [07:51:22] [02miraheze/dns] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAWyp [07:51:23] [02miraheze/dns] 07Reception123 03b9cb665 - mw->cp [07:52:41] ^ paladox [07:52:57] miraheze/dns/master/b9cb665 - Reception123 The build was fixed. https://travis-ci.org/miraheze/dns/builds/423310817 [07:57:08] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fAWSZ [07:57:09] [02miraheze/ssl] 07Reception123 0318eb0c3 - add prfm.wiki cert [08:05:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAWSB [08:05:13] [02miraheze/services] 07MirahezeSSLBot 033b649ff - BOT: Updating services config for wikis [08:07:57] Reception123: ah all dns need fixing [08:07:58] Then [08:08:53] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [08:08:58] Oh nvm [08:12:51] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:13:34] Nope it was changed [08:24:54] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [08:32:49] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:38:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [08:42:43] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:54:38] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [09:02:35] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:08:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [09:12:43] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:24:24] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [09:32:21] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:38:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [09:42:43] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:54:10] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [10:02:07] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [10:08:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [10:11:33] 503 we're down [10:11:35] paladox: ^ [10:12:43] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:12:50] ok back [10:19:18] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [10:20:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAW7e [10:20:15] [02miraheze/services] 07MirahezeSSLBot 03956b462 - BOT: Updating services config for wikis [10:21:21] Reception123: oh [10:21:35] So puppet errors are causing outages now? [10:23:28] paladox: It seems so, there was like 30 secs of downtime [10:23:56] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [10:26:40] Reception123: I’m going to try and revert some of spf changes later to see if that fixes it [10:27:09] paladox: I'd wait for John or SPF himself, I don't think we should revert his work [10:27:15] it might mess things up even more [10:27:48] Reception123: downtime is more of priority [10:27:57] Errr I mean uptime [10:28:03] paladox: what if we have even more? [10:28:08] it's only been a few seconds, and once [10:28:39] Hmm not sure [10:28:50] That’s why I want to start reverting [10:29:16] I advise against htat [10:29:19] SPF knew what he was doing [10:30:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAW7E [10:30:14] [02miraheze/services] 07MirahezeSSLBot 033ef4614 - BOT: Updating services config for wikis [10:30:26] Reception123: yes I know what he was doing :) [10:30:32] But priority is to uptime [10:31:20] paladox: you have no proof that his changes cause the downtime + again, it was a few seconds [10:31:53] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [10:32:07] Reception123: the puppet failures started after the changes per backlog [10:32:36] yeah, but how is that related to the 503? [10:32:50] a Puppet fail should definitely not cause a 503 [10:33:07] It could if it reloads or restarts varnish [10:34:02] hmm, that should be checked [10:34:11] I was going to investigate but the error fixed itself [10:34:44] SPF|Cloud: around? [10:38:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [10:42:43] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [10:43:17] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6123 [10:53:42] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [10:54:53] paladox: I guess we must revert, reports of other issues [10:58:25] Error 503 is a problem due to several ways; it not only disables viewing the wikis but also shuts down the script I'm running to block proxies, and so on. [10:59:10] But I don't want another error 503 due to the revert; can you avoid having it again? [11:01:39] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [11:08:43] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [11:11:15] !log disabled Puppet on cp* [11:11:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [11:12:43] PROBLEM - cp4 Puppet on cp4 is WARNING: WARNING: Puppet is currently disabled, message: Issues -Reception123, last run 1 minute ago with 0 failures [11:13:31] PROBLEM - cp2 Puppet on cp2 is WARNING: WARNING: Puppet is currently disabled, message: Issues -Reception123, last run 2 minutes ago with 0 failures [11:53:35] This time I got an Error 404... wonder why that happened 🤔 [12:02:29] @The_Pioneer where? [12:04:14] The script stopped running and gave me 404 on console [12:04:27] Sorry I don't have the exact copy [12:53:33] [02miraheze/puppet] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAWbh [12:53:35] [02miraheze/puppet] 07Reception123 0300febb3 - add CnocBride's email to CVT [12:53:39] ^ @CnocBride [13:15:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAWNo [13:15:13] [02miraheze/services] 07MirahezeSSLBot 03e0c4c7f - BOT: Updating services config for wikis [13:17:29] Reception123: frankly I think Marseillaise has received enough warnings [13:17:34] Just go ahead and block them [13:17:53] AmandaCatherine: I have given my final warning, if she does one more disruptive thing I will proceed with a block [13:18:05] *they [13:18:23] Except that Pkbwcgs already gave a final warning [13:18:38] Pkbwcgs is not an administrator, so I would not count that "final warning" [13:18:51] + the first warning can't be a "final warning" too [13:19:46] IMHO any non-admin can issue any number of warnings, and then proceed to report them to an admin when they feel they have exceeded their warning limit [13:19:58] Warnings shouldn’t only have to be issued by admins [13:20:06] didn't say they can't be issued [13:20:17] Just said I'm not taking that one into account, as it was the first warning [13:20:33] No, there were other warnings on AN [13:20:41] Spam spam spam [13:20:59] AmandaCatherine: well, I've already given my warning and unless they continue to be disruptive I will not block them [13:21:15] Fine, whatever [13:21:57] For reference though https://meta.miraheze.org/wiki/Meta:Administrators%27_noticeboard#Disruptive_creation_of_pages_from_Marseillaise [13:21:58] Title: [ Meta:Administrators' noticeboard - Miraheze Meta ] - meta.miraheze.org [13:22:17] ok [13:22:29] AmandaCatherine: quoting you, we should assume good faith :) [13:23:12] Yes, but when someone directly apologizes for something and then explicitly does the same thing again... [13:23:23] ...there’s very little good faith there [13:23:59] maybe they are confused, but it's not that spammy or vandalism really, so I'd like to give them another chance first [13:24:24] Fair enough [13:25:49] and I don't mind them adding stuff to their userpage, if it's not insulting or anything they can add whatever really [13:26:50] Meh [13:40:13] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [13:41:44] Marseillaise They either don't know how to use Mediawiki, or they could just be trolling. [13:41:45] Meh [13:44:15] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 3118 [13:44:44] [d__d]: seen PuppyKun? [13:44:44] <[d__d]> Yes, I saw PuppyKun 2 days ago. [13:44:45] <[d__d]> PuppyKun said: "*wired something and it no longer works*" [14:10:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAWxs [14:10:14] [02miraheze/services] 07MirahezeSSLBot 03695caf4 - BOT: Updating services config for wikis [14:24:22] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 76919 MB (20% inode=94%); [14:30:09] [02miraheze/puppet] 07Reception123 pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/fAWpk [14:30:11] [02miraheze/puppet] 07Reception123 030a8a600 - use_strict_firewall false on mw* Per SPFs recommendation, possibly causign 503 errors [14:30:11] SPF|Cloud ^ [15:02:37] !log re-enabled puppet on cp* [15:02:41] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:02:42] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [15:03:16] paladox: re-enabling per SPFs suggestion to remove the firewall [15:03:27] @The_Pioneer please tell me if you see any other 503s [15:03:30] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [15:03:32] though they should in theory be fixed by this [15:03:55] OK [15:04:11] I will soon have a break though. [15:04:15] ok [15:04:39] Reception123: ok [15:05:04] I guess this blocking is indeed working well; did you see the AbuseLog on Meta? There's only two filed as of today. [15:05:21] Wow, that's really good :) [15:05:30] Right. [15:06:38] I had about 60% of the listed IPs blocked so far; I think it will be over by tomorrow morning JST [15:06:46] FYI [15:08:28] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [15:46:25] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 2999 [16:06:13] [02CreateWiki] 07The-Voidwalker opened pull request 03#86: adjustments to handling subdomain - 13https://git.io/fAlvH [16:07:59] [02CreateWiki] 07The-Voidwalker synchronize pull request 03#86: adjustments to handling subdomain - 13https://git.io/fAlvH [17:11:40] [02CreateWiki] 07paladox closed pull request 03#86: adjustments to handling subdomain - 13https://git.io/fAlvH [17:11:41] [02miraheze/CreateWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAlJQ [17:11:43] [02miraheze/CreateWiki] 07The-Voidwalker 0349a91bc - adjustments to handling subdomain (#86) * adjustments to handling subdomain move strtolower earlier account for users entering the $wgCreateWikiSubdomain as a part of their subdomain without throwing an error * fix [17:12:31] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_31 [+0/-0/±1] 13https://git.io/fAlJd [17:12:33] [02miraheze/mediawiki] 07paladox 03af77e4b - Update CreateWiki [17:40:52] !log upgrade to php 7.2.9 (from 7.2.8) on mw* and test1* [17:41:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:44:36] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 3 minutes ago with 10 failures. Failed resources (up to 3 shown): Package[php7.2],Package[php7.2-curl],Package[php7.2-dba],Package[php7.2-fpm] [17:45:14] it installed safely so must have been done when mw3 puppet was running [17:46:36] !log upgrade phabricator on misc4 [17:46:40] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [17:46:54] Now I had error 502: load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1jv1btd:130 POST https://meta.miraheze.org/w/api.php 502 () [17:46:55] Title: [ MediaWiki API help - Miraheze Meta ] - meta.miraheze.org [17:50:22] @The_Pioneer must have been the php7.2 upgrade i just did [17:50:28] sorry if it caused a problem for you. [17:52:35] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:59:55] It's OK [18:00:20] I know you guys also need to work on technical issues as well [18:00:44] And I don't have any intention to stop your work because of mine [18:57:48] [02CreateWiki] 07The-Voidwalker opened pull request 03#87: actually modify subdomain - 13https://git.io/fAlLR [18:59:36] [02CreateWiki] 07paladox closed pull request 03#87: actually modify subdomain - 13https://git.io/fAlLR [18:59:38] [02miraheze/CreateWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAlLV [18:59:39] [02miraheze/CreateWiki] 07The-Voidwalker 03fef4437 - actually modify subdomain (#87) [18:59:42] Reception123: deploy ^^ [18:59:44] Please [19:00:17] thanks, I feel a little silly about that :P [19:00:28] good thing I tested it [19:01:39] Heh thanks Voidwalker for your commits! [19:02:45] paladox: sure :) [19:05:11] !m Voidwalker [19:05:11] <[d__d]> You're doing good work, Voidwalker! [19:09:22] Thanks [19:11:58] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fAlLj [19:11:59] [02miraheze/mw-config] 07Reception123 03949488f - rm rfc sitenotice [19:12:35] [02miraheze/mediawiki] 07Reception123 pushed 031 commit to 03REL1_31 [+0/-0/±1] 13https://git.io/fAltv [19:12:37] [02miraheze/mediawiki] 07Reception123 0379e6e8f - Update CreateWiki [19:12:46] ^ paladox [19:17:05] Thanks [19:17:20] hey please can i get a backup [19:17:37] https://bootstrapping.miraheze.org [19:17:38] Title: [ bootstrapping ] - bootstrapping.miraheze.org [19:18:30] rain1: how often? [19:18:35] just now [19:18:47] rain1: oh, ok. emailed? [19:18:55] (you can PM me with an email if you would like) [19:18:58] i dont mind if it's email or just linked here [19:19:05] rain1@airmail.cc [19:21:22] ok [19:21:34] rain1: it's easier for me to link it, so that's ok right? [19:24:11] !log srv/mediawiki/w/maintenance/dumpBackup.php --wiki bootstrappingwiki --logs --full --uploads > /mnt/mediawiki-static/dumps/bootstrappingwiki01092018.xml [19:24:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:24:27] rain1: here you go https://static.miraheze.org/dumps/bootstrappingwiki01092018.xml [19:24:28] Title: [ Main Page ] - static.miraheze.org [19:25:08] thank you! [19:25:13] rain1: you're welcome :) [19:25:21] if you need anything else feel free to ask me [19:46:31] labster: Ping [19:46:41] Cyberpower678: hi. Do you need Labster specifically? [19:46:58] He’s listed as an admin contact on all the tropes [19:48:38] Cyberpower678: Oh. Labster isn't very active, you might want to contact GethN7 (Arcane21) [19:50:01] He already responded on Wiki. :D [19:54:00] paladox: JohnLewis so that's how we get Labster to respond! [19:54:52] Lol [19:55:02] Reception123: try for mass pings on att then!!!! [19:55:29] paladox: I will :P [19:58:32] Cyberpower678: when did he answer? Recently? [19:59:12] Reception123: I started a thread on ATT and GethN7 responded almost immediately. [19:59:39] Hello [19:59:49] Sigyn: en serio?.. [19:59:50] Cyberpower678: oh I thought you meant Labster [20:00:28] Oh sorry to disappoint. [20:01:15] Reception123: ahora sabemos que funciona cuando quiere, aquí funciona pero en otro canal está dormido.. xd [20:02:07] :D [20:02:19] Cyberpower678: it's fine, I was very surprised :P [20:03:43] RECOVERY - mw3 JobQueue on mw3 is OK: JOBQUEUE OK - job queue below 300 jobs [20:06:16] JohnLewis: how are we doing on ManageWikiPermissions? [20:06:45] +1 ibidem [20:09:09] AmandaCatherine: the new landing page must be done [20:09:20] Landing page? [20:09:44] We are redesigning managewiki [20:09:46] I think [20:09:53] Yeah, I saw the task [20:09:55] To accommodate permissions [20:10:07] But that shouldn’t hinder the deployment of ManageWikiPermissions as its own special page for the time being [20:10:23] Yeah! :D [20:10:25] It has been deployed to a few wikis [20:10:28] Including yours [20:10:33] No it hasn’t [20:10:52] Oh sorry Reception123 created a branch but never merged it into mw-config [20:11:02] I guess due to bugs [20:11:24] Don't merge please [20:11:36] Corrections have to be made [20:11:46] Reception123: is there a bug? [20:11:51] and add Wiki1776wiki ? [20:12:03] Reception123: I was never gonna do :) [20:12:35] No but it's the wrong config [20:13:24] Huh? [20:18:11] Reception123: what do you mean by “the wrong config”? [20:50:57] Reception123: you still there? [20:53:32] PROBLEM - mw3 JobQueue on mw3 is CRITICAL: JOBQUEUE CRITICAL - job queue greater than 300 jobs. Current queue: 6121 [20:55:54] AmandaCatherine: I think he’s gone to bed [20:56:03] As he is in the eu [20:56:13] As it’s would be almost 11pm for him [20:56:44] Meh [20:57:07] He said something about “wrong config” and didn’t elaborate... [20:57:39] Yep though it’s late in the eu :) [20:57:45] I’m only one hour behind the eu [20:58:33] I’ve GTG in a few minutes too [20:59:27] AmandaCatherine: he made a patch which incorrectly implemented some config variables [20:59:44] JohnLewis: oh [22:36:46] Hi all [22:37:37]