Re: Connection reset by peer / broken pipe - Mailing list pgsql-general

From Tom Lane
Subject Re: Connection reset by peer / broken pipe
Date
Msg-id 14483.1207084337@sss.pgh.pa.us
Whole thread Raw
In response to Connection reset by peer / broken pipe  ("Jeff Wigal (Referee Assistant)" <jeff@referee-assistant.com>)
Responses Re: Connection reset by peer / broken pipe  ("Jeff Wigal (Referee Assistant)" <jeff@referee-assistant.com>)
List pgsql-general
"Jeff Wigal (Referee Assistant)" <jeff@referee-assistant.com> writes:
> I am running Postgres 8.2.3 and am seeing the following error messages in my
> logs:

> LOG:  SSL SYSCALL error: Connection reset by peer
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  unexpected EOF on client connection
> LOG:  could not send data to client: Broken pipe

Do your client applications tend to leave an open connection sitting
idle for awhile?  If so you might be getting burnt by idle-connection
timeouts in intervening routers.  NAT-capable boxes in particular
will kill a connection that carries no data for "too long".  If you're
lucky the router will offer a way to adjust its timeout ...

            regards, tom lane

pgsql-general by date:

Previous
From: sam
Date:
Subject: Too many commands in a transaction
Next
From: Tom Lane
Date:
Subject: Re: simple update queries take a long time - postgres 8.3.1