I know this may seem like whining but Nightshade was pulled out of service due to hardware issues. DaB pulled yarrow in as a linux test server, (since river left solaris maintenance is difficult), Right now willow (our only remaining login server) is extremely over stressed, I am seeing core dumps, seg-faults and many other symptoms on a more and more frequent basis. The banning of interwiki bots has done a small favor in reducing the stress. Yet we continue to add more accounts and use more resources on an already overloaded server. Is there an eta on getting Nightshade back in operation? and possibly adding yarrow as a login server? If there are things holding back this process is there anything that us users in userland can do to help expedite this process?
John
Hello all, At Friday 08 June 2012 18:19:49 DaB. wrote:
If there are things holding back this process
to give you all a status-update: I wait for the finishing of the SGE-update, the linux-boxes are in theory ready to use (there is still a problem with server-hopping but I guess most of you don't use that anyway). If you like you can begin to use yarrow too for the moment (let us call it a extended test-window) under 2 precondition: * No cron-using * The box can be rebooted on short-time-base (like 15min between announcement on the command-line and rebooting).
I know that the resources are a little bit short at the moment, and I am sorry for it, but I can not change that – I can only promise at on medium-term-base we will have enough userland-resources again.
Sincerely, DaB.
On 08/06/12 18:32, DaB. wrote:
Hello all, At Friday 08 June 2012 18:19:49 DaB. wrote:
If there are things holding back this process
to give you all a status-update: I wait for the finishing of the SGE-update, the linux-boxes are in theory ready to use (there is still a problem with server-hopping but I guess most of you don't use that anyway).
Also, MMPs don't work. https://jira.toolserver.org/browse/TS-1376
hostbased authentication should be as easy as configuring the yarrow key at the other servers. What's the problem?
Hello, At Friday 08 June 2012 22:43:54 DaB. wrote:
hostbased authentication should be as easy as configuring the yarrow key at the other servers. What's the problem?
the problem is, that that is exactly what I did (and changing various ssh- settings) and that it still not work for unknown reasons. My next testing- setup will test if the hoping between linux-hosts is possible (then it could be a linux<->solaris-problem) or not (then it could be a config-problem).
Sincerely, DaB.
On 08/06/12 22:54, DaB. wrote:
Hello, At Friday 08 June 2012 22:43:54 DaB. wrote:
hostbased authentication should be as easy as configuring the yarrow key at the other servers. What's the problem?
the problem is, that that is exactly what I did (and changing various ssh- settings) and that it still not work for unknown reasons. My next testing- setup will test if the hoping between linux-hosts is possible (then it could be a linux<->solaris-problem) or not (then it could be a config-problem).
Sincerely, DaB.
It should work. Moreover, both Solaris and Linux ssh come from OpenSSH. yarrow is trying hostbased authentication (that's the first thing I suspected could be wrong), I'd look at the sshd log for the reason of the refusal. Maybe the sshd server needs to be restarted to pick the new yarrow host key? (let's remember that its key changed with the reinstall)
toolserver-l@lists.wikimedia.org