Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.security.ssh > #208

Re: OpenSSH "Write failed: Broken pipe"

From um <nospam@mutluit.com>
Newsgroups comp.security.ssh
Subject Re: OpenSSH "Write failed: Broken pipe"
Date 2011-10-19 21:21 +0200
Organization mutluit.com
Message-ID <j7n7vo$10o$1@speranza.aioe.org> (permalink)
References <7eb364a2-a56c-4285-8962-a4cfe2924f19@p25g2000yqh.googlegroups.com>

Show all headers | View raw


spork wrote, On 2011-10-18 02:01:
> This is sort of a general question, and I don't think I'm looking at
> any sort of OpenSSH bug, but figuring out what the "write failed"
> message means might help me track down whatever network/firewall issue
> I'm dealing with.
>
> I've noticed that in general when I lose a session due to a state
> timeout in the firewall or simple loss of connectivity, I'll get an
> error message like this:
>
> "Timeout, server not responding."
>
> Recently we've been seeing this message:
>
> "Write failed: Broken pipe"
>
> Is there anything I can infer from that second message about what the
> root cause of the failure is?  Just looking for a general answer about
> what each error message is trying to tell me.

Timeout and/or Connection drop.

To increase the default timeout I use these settings in /etc/ssh/sshd_config :
   ClientAliveInterval 60
   ClientAliveCountMax 3

There is another solution as described here:
   http://dan.hersam.com/2007/03/05/how-to-avoid-ssh-timeouts/

Back to comp.security.ssh | Previous | NextPrevious in thread | Find similar


Thread

OpenSSH "Write failed: Broken pipe" spork <spork.sporkman@gmail.com> - 2011-10-17 17:01 -0700
  Re: OpenSSH "Write failed: Broken pipe" um <nospam@mutluit.com> - 2011-10-19 21:21 +0200

csiph-web