Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this community
When I close my MacBook with an active SSH session in Terminal and then wake it up, the prompt goes unresponsive.
In about five minutes it says
Write failed: Broken pipe
and terminates.
This also happens when I don't type anything in the Terminal in about fifteen minutes.
Can I force OS X to:
?
For keeping the connection alive, you can check in /etc/ssh/ssh_config the line where it says ServerAliveInterval, that tells you how often (in seconds) your computer is gonna send a null packet to keep the connection alive. If you have a 0 in there that indicates that your computer is not trying to keep the connection alive (it is disabled), otherwise it tells you how often (in seconds) it is sending the aforementioned packet. Try putting in 120 or 240, if it is still killing your connection, you can go lower, maybe to 5, if with that number it doesn't happen, maybe it is your router who is dumping the connection to free memory.
For killing it when it gets hang up, you can use the ssh escape character:
~.
That is, press the tilde and then the period, if it doesn't work, press Enter before you press that, that will kill the connection immediately.
You can:
Configure your system, system-wide, for all connections By editing: /etc/ssh/ssh_config And add the line:
ServerAliveInterval 10
Or, per-server ~/.ssh/config
Host keepsdroppingme.com
ServerAliveInterval 10
What this basically does it sends keep alive packet, every 10 seconds...
You can also try using the awesome mosh project. It will gracefully handle network losses, machines going to sleep, etc and happily restore the connection when you have a working network again.
Another more time-honored solution is to use tmux on the remote machine. In that case you may still get a broken pipe, but if you reconnect your shell and applications will be waiting just as you left them.
Just resolved this issue add these following lines in $HOME/.ssh/config.
Host *
ServerAliveInterval 120
TCPKeepAlive no
Setting TCPKeepAlive no tells the client to just assume the connection is still good until proven otherwise by a user request, meaning that temporary connection breakages while your ssh term is sitting idle in the background won't kill the connection.
The various answers here are in conflict regarding the exact path to the config files. Maybe it is different in different unixes? I suggest reading the man pages on your system!
In man ssh(1), search for text: config. On my system, I have a choice of either system-wide or this-user config files (and the paths are oddly different).
In man ssh_config(5), search for text: alive. On my system, it looks like I need to set both ServerAliveInterval and ServerAliveCountMax.
What worked for me, on macOS 10.12 Sierra, is to put the following two lines in ~/.ssh/config:
ServerAliveInterval 20
ServerAliveCountMax 180
Now I can ssh to my Ubuntu 16.04 server with no disconnect for 20*180 seconds = 1 hour. Made my day!
Install autossh from MacPorts or Homebrew: brew install autossh
Open Terminal and run autossh -M 20000 -f [SSH ARGUMENTS GO HERE]
Disconnect your wifi or put your Mac to sleep.
When you reconnect to wifi, the ssh session will automatically reconnect.
Jon Stacey wrote a blog post about automatically activating an ssh session when you login.
Install autossh from MacPorts or Homebrew: brew install autossh
Create an Automator workflow with a bash script.
Add these two lines to /etc/ssh/ssh_config:
ServerAliveInterval 60
TCPKeepAlive yes
