Over a million developers have joined DZone.
Platinum Partner

Ssh "Write failed: Broken pipe"

· DevOps Zone

The DevOps Zone is brought to you in partnership with New Relic. Improving the performance of your app is easy with New Relic's SaaS-based monitoring.

I started to get this error “Write failed: Broken pipe” when I was leaving the terminal alone.
Since plumbers are still expensive, despite the crisis, I decided to fix the pipe by myself.
Very easy, just add the following line to /etc/ssh/sshd_config:

ClientAliveInterval 60

This will send a “keep-alive” packet from the server to the terminal client every 60 seconds so that the connection doesn’t get dropped.

If you can’t fix it on the server, for example if you don’t have administrative rights, you can fix your client to send the “keep-alive” packet to the server every 60 seconds, adding this line to ~/.ssh/config

ServerAliveInterval 60

It’s also possible to specify the ServerAliveInterval at the ssh command line:

$ ssh -o ServerAliveInterval=60 user@sshserver

More info about ClientAliveInterval and ServerAliveInterval can be found typing at the command line:

$ man 5 sshd_config
$ man 5 ssh_config
$ man ssh

Another reference here.

Your pipes should be safe now, and the plumbers out of business.

The DevOps Zone is brought to you in partnership with New Relic. Know exactly where and when bottlenecks are occurring within your application frameworks with New Relic APM.


Published at DZone with permission of Luigi Viggiano , DZone MVB .

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}