Re: unexpected EOF on client connection / could not send data to client: Broken pipe
От | Kevin Grittner |
---|---|
Тема | Re: unexpected EOF on client connection / could not send data to client: Broken pipe |
Дата | |
Msg-id | 4FA127FF0200002500047700@gw.wicourts.gov обсуждение исходный текст |
Ответ на | unexpected EOF on client connection / could not send data to client: Broken pipe (Hariraman Jayaraj <hariraman.ocp@gmail.com>) |
Список | pgsql-admin |
Hariraman Jayaraj <hariraman.ocp@gmail.com> wrote: > We are using postgres 8.3 in Open Suse 11 server. > Front end - Java, struts > Middle ware - Jboss > Backend - Postgres 8.3 DB. It helps to know the exact version number and PostgreSQL configuration settings. http://wiki.postgresql.org/wiki/Server_Configuration > Recently I am encoutering below mentioned error. Also by the time > this error occuring, Linux server / Postgres Server is too slow > and at times it is not responding at all. Can you run `vmstat 1` while things are slow? It sounds like you might be getting into heavy swapping due to memory over-commit. Can you show us the result of running `free -m`? > 2012-05-02 12:14:09 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:09 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:09 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:10 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:11 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:11 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:12 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:12 IST LOG: unexpected EOF on client connection > 2012-05-02 12:14:13 IST LOG: could not send data to client: > Broken pipe Those messages mean that the TCP connection from the client was broken by something other than the PostgreSQL server. -Kevin
В списке pgsql-admin по дате отправления: