Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've seen this with so many consoles (on Linux, Mac, ...), and with lots of different machines in many different networks. I can never pinpoint the exact reason, why this happens: All you have to do is log in to a machine via SSH. If the connection breaks for some reason (for simplicity, let's say the network cable was pulled), then sometimes the console just hangs forever - at other times, it just exits fine to the parent shell.

It's so annoying when this happens (e.g. you lose the command history.) Is there maybe a secret keyboard shortcut which can force an exit (Ctrl-C or Ctrl-D don't work)? And what's the reason for this random "bug" across all the implementations anyway?

share|improve this question

4 Answers 4

up vote 56 down vote accepted

There is a "secret" keyboard shortcut to force an exit :~) From the frozen session, hit these keys in order: Enter~. The tilde (only after a newline) is recognized as an escape sequence by the ssh client, and the period tells the client to terminate it's business without further ado.

The long-hang behavior on communication issues is not a bug, the SSH session is hanging out hoping the other side will come back. If the network breaks, sometimes even days later you can get an SSH session back. Of course you can specifically tell it to give up and die with the sequence above. There are also various things you can do such as setting keep-alive timeouts in your client so that if it doesn't have an active link for a certain amount of time it shuts off on it's own, but the default behavior is to stay as connected as possible!

Edit: Another useful application of this interrupt key is to get the attention of the local ssh client and background it to get back to your local shell for a minute —say to get something from your history— then forground it to keep working remotely. Enter~ Ctrl+Z to send the ssh client to the background job queue of your local shell, then fg as normal to get it back.

share|improve this answer
8  
+1 for knowing the dodecatouple-secret-probation password for shooting sshd in the head. Did you find out about it the same way I did (mistyping ~/.somethingorother after hitting enter)? –  voretaq7 Jun 22 '11 at 18:22
    
Okay, +1 very cool - there seem to be some possible solutions. On my OS X terminal (which is currently frozen), the key strokes don't work (but that may have something to do with the (German) Mac keyboard, where tilde itself is a key combination: Alt-n)... I'll really need to find out, how to configure the keep-alive timeouts on my client! –  Chris Lercher Jun 22 '11 at 18:27
2  
@voretaq7: No I wasn't that smart, but when somebody did clue me in I went "Really? So that's what was happening all those times my shell just went BANG! for no reason when I was typing?". It's not a common sequence except in mistypes of the one you mention, but it can happen. –  Caleb Jun 22 '11 at 18:34
4  
Whereby "secret" he means "in the man page". –  larsks Jun 22 '11 at 19:05
5  
Of course it's in the man page :) I only used the word secret because the OP did, and I was using tongue in cheek. The problem with this feature is that people don't know where to look for it, they expect control characters and such signals to be part of the shell or such. Once you know where to look or even what to ask, of course it's there. –  Caleb Jun 22 '11 at 20:17

The fact that it hangs is a function of TCP, not SSH. The application has no way of knowing that the TCP session/connection has been severed unless TCP informs the application using the connection that the connection no longer exists. From the perspective of each host, the TCP session is still in the Established state and there's nothing to say that a long idle (no data flowing) session is not valid other than a RST or a lack of response to a TCP keepalive packet (which is not universally implemented). That doesn't appear to be a bug in SSH to me, I'd expect that behavior.

share|improve this answer

If the connection is properly hung any magic keystroke will not get through as the connection is already hung before you issue the key presses. You can tell the client to terminate but this won't affect the history kept (or not) at the server end.

While this doesn't actually answer the question it may help reduce the effects of a connection hang: when I'm working remotely (and even usually when I'm not) I run through screen (with or without the byobu wrapper depending on its availability) so that if there is any sort of connection drop my session, with all its history, is preserved and available in the state I left it when I reconnect.

share|improve this answer
3  
Your suggestion about screen is fine, but the first bit is actually not applicable to the issue. You don't need to get keys through to the remote side, you only have to get them through to the LOCAL ssh client! The OP want's his local shell back including history. SSH takes it over and doesn't respond to normal break sequences like CTRL-C because it passes those on. There is a way to get through and terminate the local client, see my answer. History on the local end is usually kept anyway if you login again, depending on shell configuration. –  Caleb Jun 22 '11 at 18:20
2  
@Caleb: the question specifically mentioned losing history, and the command history is stored server-side. To tell the server to do anything different with the history you need to get a message to the server to tell it to do something different with the history. Of course there are ways of making bash (and some other shells) record history lines immediately rather than collecting them in RAM until the user properly exists the shell with exit/logout which would solve the history issue without using screen. –  David Spillett Jun 22 '11 at 19:44

SSH offers a keep-alive facility. Add the following to your local ~/.ssh/config (create if it doesn't exist):

ServerAliveInterval 15
ServerAliveCount 3

This setting will establish a keep-alive signal sent every 15 seconds through the secure tunnel. After three consecutive failures, the SSH client will exit.

Note that on some systems instead it needs to be:

ServerAliveInterval 15
ServerAliveCountMax 3

Taken from this answer on ask.ubuntu: http://askubuntu.com/a/29967/30266

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.