Well, generally, if ssh is hung, it's due to a high load; typically If I have an idea of what's causing it, I'll run a ssh with the command to kill that process or a reboot and cross my fingers. Going forward, I think it's always a really good idea to have console acres via an ILO, or a second ssh instance on a non-standard port reniced so it will get priority. That can sometimes help, although not always.

-- Sent from my mobile device

On Jun 28, 2011, at 3:48 PM, "David N. Blank-Edelman" dnb@ccs.neu.edu wrote:

Hi Felix-

Thanks for your response.

On Tuesday, June 28, 2011 at 6:08 PM, Felix Schröder wrote:

...

To kick out a stalled SSH session just type "ssh root@filer logout telnet" on a *nix machine, then type in the password - That will force the filer to logout any interactive (ssh) session. It works the same way with rsh.

I must not have been clear in my message. Both interactive, and non-interactive ssh command the machine are hanging. I can't even do an ssh netapp help, nevermind execute the logout command. The connections never get that far.

I should also mention that at the moment, according to netstat, there are no existing ssh connections so there isn't really anything to logout.

-- dNb