[Discuss] (ssh) Write failed: Broken pipe

[gmongardi at napc.com (Grant Mongardi)]

It could be a firewall process, where the firewall is dropping what it
feels are inactive connections. Are other machines behind the same firewall
behaving differently?
Grant M.


On Thu, Sep 5, 2013 at 2:50 PM, Greg Rundlett (freephile) <
greg at freephile.com> wrote:

> I've been experiencing a broken ssh tunnel that abruptly fails with "Write
> failed: Broken pipe".  (Not the normal timeout experience of "Connection
> reset by peer".)  Google and SO are failing to find me an answer.  (fb
> posted a photo that is irrelevant and got many likes).
>
> I don't have any problems with any other host that is configured the same
> way, and I've tried various incantations of the /etc/ssh/sshd_config file
> that are supposed to help.  Here is what I have currently on the server:
>
> sudo grep -i alive /etc/ssh/sshd_config
> TCPKeepAlive yes
> ClientAliveInterval 60
> ClientAliveCountMax 100000
>
> I also have my Client configured to throw null packets at the server every
> 60 seconds.
> grep -i alive ~/.ssh/config
> ServerAliveInterval 60
>
> At the OS level:
> cat /proc/sys/net/ipv4/tcp_keepalive_time
> 7200
>
> Any ideas what could cause this?
>
> Greg Rundlett
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>



-- 

Grant Mongardi
Senior Systems Engineer
NAPC
gmongardi at napc.comhttp://www.napc.com/blog.napc.com
781.894.3114 phone
781.894.3997 fax

NAPC | technology matters