Thread: LOG: unexpected EOF on client connection

Hi list,

I am doing a benchmark in my database but it is spent too much time.

I was looking for my log file but I could not understad clearly what it says.

The log is like this:

INT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (4 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (5 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (5 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (8 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index 
"branches_pkey" for table "branches"
NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index 
"tellers_pkey" for table "tellers"
NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index 
"accounts_pkey" for table "accounts"
ERROR:  conversion between latin9 and LATIN1 is not supported
STATEMENT:  set client_encoding to 'latin9'
FATAL:  sorry, too many clients already
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection
LOG:  unexpected EOF on client connection

Does anyone have any suggestion ?


--
Ezequias Rodrigues da Rocha
http://ezequiasrocha.blogspot.com

<ezequias@fastcon.com.br> writes:
> FATAL:  sorry, too many clients already

You need a larger max_connections setting.

> LOG:  unexpected EOF on client connection

I think pgbench just dies ungracefully if it gets a connection failure.
        regards, tom lane

Hello,

A client application written in C# + npgsql 2.0.6 causes reproducable
log entries like this:

LOG:  unexpected EOF on client connection
LOG:  could not receive data from client: Die Verbindung wurde vom
Kommunikationspartner zurückgesetzt(*)

(*) Connection reset by peer

The responsable Programmer claims autovacuum caused the malfunction.
But after disabling autovacuum the same error occured. Another
program, written Python + psycopg2, which invokes exactly the same
function resulting the above connection reset in the C# program runs
without any problem while inserting far more than 10 times the amount
of data the C# program should do. Even running 2 parallel instances of
the Python program does not result in any error.


Server is version 8.4 + Postgis 1.4 (both compiled with gcc 4.3), OS
is Debian Lenny running on a Quadcore-Xeon Dell Precision 690 with 2
GB RAM. When the above error occurs the C# program is the only client
connecting to the server.


What may be the most probable cause of that?



Bernd

-- 
No time toulouse

Bernd Nawothnig <Bernd.Nawothnig@t-online.de> writes:
> A client application written in C# + npgsql 2.0.6 causes reproducable
> log entries like this:

> LOG:  unexpected EOF on client connection
> LOG:  could not receive data from client: Die Verbindung wurde vom
> Kommunikationspartner zurückgesetzt(*)

This just indicates that the client application closed the connection
without sending a Terminate message.  It's harmless, but if the log
chatter annoys you, you should fix the application to close its PG
connection cleanly before it quits.

> The responsable Programmer claims autovacuum caused the malfunction.

Nonsense ...
        regards, tom lane