Hey, I'm NDKilla.
I'm on on the Operations team and I like Badges.
Sun, Mar 17
@Void / (root partition) has 17GB free on lizardfs1, but /mnt/mediawiki-static has 100% disk usage (rounded / 100 MB free)
Sat, Mar 16
Robert I previously linked you to the storage space for db4 on Facebook. The same website shows various monitoring information for all of our servers.
I think this task as-is is is technically resolved. Should we make a new task or rename this task for migrating all wikis to use elastic search? just the largest wikis?
Setting this to normal since I'm assuming both issues in this task will get resolved when file storage issue is resolved.
@Zephyrantes that error is most likely caused by file storage not having capacity to temporarily copy the file for the move.
Wed, Mar 13
Tue, Mar 12
This is the problem, I didn't realize we set that manually. That needs to be like "cargo_" . $wgDBname" or even just $wgDBname, which I believe is the default. (But we may not want to use the default so it can be removed later if the extension is deleted?)
Fri, Mar 8
cc @Southparkfan because this apparently has to do with headers and Paladox thinks you may have broken things 🔧
Tue, Mar 5
See also T2087
Sat, Mar 2
I have no direct concerns myself, although you mentioned there have been instances where expanded access would have allowed you to resolve issues yourself, where there are currently no such instances.
Jan 23 2019
why dont we already use elasticsearch? is it intensive on some other resource? I've installed and use it on the wiki at work, but it's basically no-traffic, I just wanted better search queries.
This seems to work for me. Note that a bot has to update some server-side configuration when you first enable the extension. If you're still having issues feel free to re-open this task.
Jan 9 2019
Jan 5 2019
Dec 2 2018
No real objections so a more neutral support mostly based on my own inactivity. I agree with Reception saying that having people handle SSL is a good thing.
Nov 12 2018
Oct 20 2018
I don't think the 'somehow' is needed, and with-width was a typo presumably.
Sep 22 2018
@AmandaCath If it tells you what files were uploaded to private wikis, it would have to be restricted. Otherwise I wouldn't see the need I suppose.
Sep 2 2018
This is not possible for reasons besides the above. Anyone will always be able to register for your site because Miraheze uses global logins. Even if we restricted account creation on your wiki, someone could create an account else where and then load your site.
Honestly any such script would probably need to be based on the CLI and be niced on one of the mw systems. Anything running in the browser would time out I think? (I don't see how you could run the script for hours or days as a flooder unless you're repeatedly running it with different input? Seeing as how sometimes Special:Nuke even times out.
Aug 15 2018
Aug 1 2018
Jul 31 2018
Jul 2 2018
Fixed the issue with mwexception i believe but it resulted in not having autopromote set up. I don't know what valid config for that is, but it wasn't that.
Jul 1 2018
May 14 2018
May 4 2018
Apr 26 2018
Apr 11 2018
@WesleyCollege I'm still looking into some weird things, but could you have the user try resetting their account by email and trying to login, letting me know if anything goes wrong?
Fine @John, I'll comment now.
Apr 9 2018
Since the account in question was directly created by the user reporting this there should be no issues just updating the user info and letting them reset the password.
Apr 7 2018
Resolved by rMWCF4337f050917b
Apr 2 2018
I think a nice starter list for categories be the categories used on the current "Gazetteer of wikis"
Mar 30 2018
Although this was already approved by a majority of operations members, just wanted to say happy to welcome you back, John!
Mar 17 2018
Resolved by rMWCF98388bb67878
Feb 26 2018
Feb 17 2018
@Southparkfan In regards to the very final note of your comment, software raid a possibility?
Feb 4 2018
Possibly (/probably) related to T2646 but I haven't checked the exception log so not closing as dupe.
Feb 1 2018
@labster spf is under the assumption were obligated to pay them because we were already invoiced, so we were making arrangements to continue testing
@Samwilson code looks relatively short, can you take a look at this if you get a chance?
Jan 24 2018
@Ha-Mim You could just create another "main page" like "Name_of_your_wiki" and then change the "Main_page" text to just say "This is my wiki. If you are allowed to view this wiki [click here]" and have click here link to your actual main page.
MacFan4000 can not read the contents of your wiki, except for a couple whitelisted pages ("Main_page" and some technical pages).
Jan 16 2018
There are plenty of tutorials out there for setting up spamassassin with postfix (spamd). We could just have it add spam score headers until we get the settings right.
Jan 9 2018
Raising the priority does not make us respond to these tasks faster.
Jan 6 2018
@revi has been particularly helpful notifying us of potential issues with SSL, including trying to notify us when browsers add or remove CAs from their default trust stores.
Jan 5 2018
I would also like to see more commit-related activity. I appreciate them coming on IRC a bunch and usually don't want to punch them because of their bot, but going to hold off on a +1 til i see more of an ability of Zppix to fill a gap we need.
Jan 4 2018
@labster pretty sure they mean 4 days from now. I'll send out the order number.
@labster I'm not sure about the phone call. If that's the case, hopefully they call you? After you get the order number give me it (Or list here) so that I can send it to the representative I was talking to
Jan 3 2018
@revi revi, everyone on the team knows of your work, but just as a formality (And documentation) could you describe your experience with SSL handling and what you'd be able to do with puppet-users access?
Jan 2 2018
The error is related to a block being above the maximum time. Sysop is required to view deleted revisions I believe.
Dec 21 2017
Dec 18 2017
I sent an email to @Southparkfan and staff@ regarding leaseweb.
Dec 15 2017
I'm against doing anything like this outside of very extreme measures (i.e. global staff spending a majority of their active time cleaning up abuse on our main site) because IP addresses tend to rotate a lot. Software global blocks affect every wiki and can be set with several different options, including anon block only and an expiry. Webserver blocking could affect all wikis but would be permanent (until removed again manually) and would affect both logged in and logged out editors.
composer dependencies have to be added on mw1/mw2
Dec 12 2017
Nov 29 2017
restarted jobrunner but also manually running all jobs
Nov 19 2017
Nov 8 2017
I have yet to look into dedicated servers yet but I was talking to @Southparkfan about 3 20€ servers from transip that would give us way more storage (and more total ram but less per server) for 60€ per month. This brings up our costs a bit but seems more cost effective and if one server (as a test) works out (latency etc) then we could migrate wikis and decommission db2 and db3
Oct 27 2017
Will try to do on-boarding asap (probably tomorrow)
Oct 26 2017
It is an unfortunate circumstance that the three people with hands on operations experience (@John, @Southparkfan, and myself) have had to put real life before Miraheze but hopefully everyone understands that.