I too am having the same issue, Write failed: Broken pipe on my ssh connections independent of server. This only happening since I upgraded to Lion, at first I thought it was my Internet Connection acting up, but my colleague here noticed the same thing only after upgrading to Lion everyone else still using Snow Leopard is fine.
I have just upgraded to 10.7.1 and still happening.
I also have under .ssh two files:
config and ssh_config with the contents:
I have used just the file config on Snow Leopard and tried to use ssh_config in Lion to see if it resolved the issue but nothing changed...
P.S. - I'm using iTerm2 and was using it with Snow Leopard as well,. my friend just uses the Terminal that comes with OSX.
Thanks for any help on this.
I haven't tried changing the ssh config yet just because I haven't gotten around to it, however, running options at the cli when you make a connection should fix the problem.
ssh -o TCPKeepAlive=no -o ServerAliveInterval=15 username@remotehost
This does not fix meerkat from disconnecting and reconnecting all day long though if I am not actually tunneling traffic through it the whole time.
You could always fallback to actual tcp keep-alives but it generally isn't recommended.
SecureCRT NO-OP works as expected and that is what I have been doing for remote host ssh work. I can do ssh tunneling/port forwarding through SecureCRT as well but I prefer meerkat because I can just turn different tunnels on and off with a single click.
When I get some time I will probably adjust my local ssh config so that I don't have to type the options out everytime I make a connection. SecureCRT NO-OP will do in the meantime.
Hope that helps.
This Write failed: Broken pipe thing is driving me nuts. As I ssh into the linux server to to all of my work, whenever I try to display something a little bit graphics intensive, the ssh session become unresponsive and drop with the given error.
Would it be a problem with X11.app ? I have tried various version of OpenSSH (5.3 - 5.82p) but they're all the same
So I keep googling hoping someone will answer but non did. I actually installed virtualbox and have Xubuntu running then SSH and everything works fine
So long story short - I keep googling and came to some forums post about Write failed: Broken pipe and apparently this could be because some logging issue from syslogd. You can do something to the com.apple.syslogd.plist as seen here http://dans.im/blog/archives/8 What I did was just move the whole file to the trash can. I think the ssh connection stop dropping now.
A lot of people have reported wifi problems since upgrading to Lion. A brief interruption in the network connection of even a few milliseconds could disrupt an SSH connection. It could be that your SSH problem is actually a network connectivity problem.
Stupid question. Is it possible that the DHCP IP address lease is turning over to quickly AND each time it is getting a new IP address.
If the Mac were getting a new IP address each time the DHCP lease needed to be renewed, that would break any TCP connection.
As an experiment, can anyone having this problem try switching to a manually assigned IP address and see if the problem continues?
Or write a script to capture the "ifconfig" information once a minute, and then see if the IP address has changed between when the ssh (or RealVNC) connection was made and when it received SIGPIPE.
while sleep 60
again, this is just a wild guess.iMac, Mac OS X (10.6.7), 27" i7, MacBook, MacMini, etc...
I know this isn't particularly helpful but I'm another one with this issue. I practically live in SSH on my Mac and this is a real dealbreaker for me, I'm about to try the plist fix that someone mentioned above. Hopefully I'll have success here!