Re: Connection reset by peer / broken pipe
| От | Tom Lane |
|---|---|
| Тема | Re: Connection reset by peer / broken pipe |
| Дата | |
| Msg-id | 14483.1207084337@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Connection reset by peer / broken pipe ("Jeff Wigal (Referee Assistant)" <jeff@referee-assistant.com>) |
| Ответы |
Re: Connection reset by peer / broken pipe
|
| Список | 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 по дате отправления: