Indeed. I forgot to consider that. But I don’t think the problem is the volume of users. Shell sessions don’t cost many resources. We could also implement an autokiller which kills everything related to the user if it uses more than allowed.
Cyberpower678 English Wikipedia Account Creation Team Mailing List Moderator Global User Renamer From: Labs-l [mailto:[email protected]] On Behalf Of John Sent: Monday, April 04, 2016 4:02 PM To: Wikimedia Labs <[email protected]> Subject: Re: [Labs-l] [Tools] New bastion at tools-login.wmflabs.org Killing shells is a bad idea, Often Ill login and run a sql query which might take 15-20 minutes to run and do something else in the meantime. Having to login/reconnect between queries is obnoxious. (Mysql handles this nicely by auto-reconnecting but with a SSH shell its a different story. Honestly I think the best idea is find out who is utilizing resources beyond reason, call it out and have them stop. If they fail to get the message disable access. If it is just an issue of the volume of users, get a multi-host with load balancing. On Mon, Apr 4, 2016 at 3:54 PM, Maximilian Doerr <[email protected] <mailto:[email protected]> > wrote: I think the primary problem is that users keep running bot scripts on it, when they shouldn't, and I think the easy solution would be to implement a killer, which kills all scripts started on tools-login when the user logs off, or if it has been running for more than 15 minutes. It's okay to run it on -login quickly to understand how it will interact with the labs environment, but it's not supposed to be permanent. Another seemingly recurring problem, and I'm guilty of it too is when users pointlessly leave shell sessions open. That's also a security risk, and a shell should automatically terminate on labs, if it's been inactive for 30 mintues. Just my thoughts. Cyberpower678 English Wikipedia Account Creation Team Mailing List Moderator Global User Renamer -----Original Message----- From: Labs-l [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Yuvi Panda Sent: Monday, April 04, 2016 3:43 PM To: Wikimedia Labs <[email protected] <mailto:[email protected]> > Subject: [Labs-l] [Tools] New bastion at tools-login.wmflabs.org <http://tools-login.wmflabs.org> Hello! I've moved tools-login.wmflabs.org <http://tools-login.wmflabs.org> to a new bastion host with twice the RAM and CPU of the old one. This should hopefully provide a better bandaid against it getting overloaded up. More discussion about a longer term solution at https://phabricator.wikimedia.org/T131541 You can find new fingerprints at https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/tools-login.wmflabs.org Apologies for the interruption! I'll leave the old bastion up at tools-bastion-05.eqiad.wmflabs. -- Yuvi Panda T http://yuvi.in/blog _______________________________________________ Labs-l mailing list [email protected] <mailto:[email protected]> https://lists.wikimedia.org/mailman/listinfo/labs-l _______________________________________________ Labs-l mailing list [email protected] <mailto:[email protected]> https://lists.wikimedia.org/mailman/listinfo/labs-l
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
