Re: [GENERAL] unexpected EOF on client connection vs 9.0.3

2011-03-08 Thread Francisco Figueiredo Jr.
Indeed those messages appear when the client closes the socket connection only. Npgsql has connection pooling and if the app domain is unloaded and there are connections in the pool, those connections don't get a chance to have the Close message sent to backend server. So, even when you are corre

Re: [GENERAL] unexpected EOF on client connection vs 9.0.3

2011-03-08 Thread rsmogura
On Tue, 08 Mar 2011 11:30:10 +0800, Craig Ringer wrote: On 08/03/11 02:49, Piotr Czekalski wrote: I've checked and verified that all connections are closed within the code, what's more, the problem has appeared just as I've moved server from Fedora Linux x86_64 running Postgres 8.4.2 to the Wi

Re: [GENERAL] unexpected EOF on client connection vs 9.0.3

2011-03-07 Thread Craig Ringer
On 08/03/11 02:49, Piotr Czekalski wrote: > I've checked and verified that all connections are closed within the > code, what's more, the problem has appeared just as I've moved server > from Fedora Linux x86_64 running Postgres 8.4.2 to the Windows and 9.0.3 > (details above) thus I conclude this

[GENERAL] unexpected EOF on client connection vs 9.0.3

2011-03-07 Thread Piotr Czekalski
Hello there, I'm getting regular Postgres log entries with the following error: 2011-03-07 01:00:01 CET LOG: could not receive data from client: No connection could be made because the target machine actively refused it. 2011-03-07 01:00:01 CET LOG: unexpected EOF on client connection They a

Re: [GENERAL] unexpected EOF on client connection

2010-09-20 Thread Vick Khera
On Mon, Sep 20, 2010 at 8:31 AM, Eric Ndengang wrote: > 2010-09-20 14:21:51 CEST [31492]: [1-1] user=edarling,db=edarlingdb LOG: > unexpected EOF on client connection > > What really strange is, is that every  Application get connected through the > Database using the Users 'edarlingapp' or edarli

[GENERAL] unexpected EOF on client connection

2010-09-20 Thread Eric Ndengang
Hello everybody, Our Company get two Cluster environment with postgres 8.4.4 installed. Both Clusters have the same Structure (Tables, Functions, ...) In one of them I am recently getting many entries in the log on this type: 2010-09-20 14:21:25 CEST [31010]: [1-1] user=edarling,db=edarlingdb

Re: [GENERAL] Unexpected EOF on client connection

2009-12-04 Thread Howard Cole
David Boreham wrote: Sampling the number of connections on my database I decided that the number of connections settled at 6 so I changed my MinPoolSize from 3 to 6. I checked the current state of the database and the number of connections is currently 12. Tonight I shall change the MinPoolSize

Re: [GENERAL] Unexpected EOF on client connection

2009-12-03 Thread David Boreham
Howard Cole wrote: Howard Cole wrote: Thanks Francisco - I currently have MinPoolSize set to 3 (I have a lot of databases on this cluster), I think this copes 90% of the time but I shall set it to 10 and see what happens. Sampling the number of connections on my database I decided that the n

Re: [GENERAL] Unexpected EOF on client connection

2009-12-03 Thread Howard Cole
Howard Cole wrote: Thanks Francisco - I currently have MinPoolSize set to 3 (I have a lot of databases on this cluster), I think this copes 90% of the time but I shall set it to 10 and see what happens. Sampling the number of connections on my database I decided that the number of connections

Re: [GENERAL] Unexpected EOF on client connection

2009-12-02 Thread Howard Cole
Francisco Figueiredo Jr. wrote: Presumably I should never get this error if I use Npgsql? That's correct. But there may be a bug in Npgsql code itself. That's why I asked you to try to raise minpoolvalue to check if you see less errors. I hope it helps. Thanks Francisco - I curren

Re: [GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Francisco Figueiredo Jr.
On Tue, Dec 1, 2009 at 21:39, Howard Cole wrote: > Howard Cole wrote: >> >> Interesting what Francis says about the pool connections being closed >> before disposal. > > Apologies "Francisco" >> :) No problem. >> Presumably I should never get this error if I use Npgsql? >> That's correct. But

Re: [GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Howard Cole
Howard Cole wrote: Interesting what Francis says about the pool connections being closed before disposal. Apologies "Francisco" Presumably I should never get this error if I use Npgsql? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscrip

Re: [GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Howard Cole
Richard Broersma wrote: On Tue, Dec 1, 2009 at 7:52 AM, Howard Cole wrote: I am getting many entries in my log of this type: 2009-12-01 00:13:19 GMTLOG: unexpected EOF on client connection 2009-12-01 00:13:19 GMTLOG could not receive data from client: No connection could be made because the

Re: [GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Francisco Figueiredo Jr.
On Tue, Dec 1, 2009 at 13:52, Howard Cole wrote: > I am getting many entries in my log of this type: > > 2009-12-01 00:13:19 GMTLOG: unexpected EOF on client connection > 2009-12-01 00:13:19 GMTLOG could not receive data from client: No connection > could be made because the target machine activel

Re: [GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Richard Broersma
On Tue, Dec 1, 2009 at 7:52 AM, Howard Cole wrote: > I am getting many entries in my log of this type: > > 2009-12-01 00:13:19 GMTLOG: unexpected EOF on client connection > 2009-12-01 00:13:19 GMTLOG could not receive data from client: No connection > could be made because the target machine activ

[GENERAL] Unexpected EOF on client connection

2009-12-01 Thread Howard Cole
I am getting many entries in my log of this type: 2009-12-01 00:13:19 GMTLOG: unexpected EOF on client connection 2009-12-01 00:13:19 GMTLOG could not receive data from client: No connection could be made because the target machine actively refused it. I tend to get these message in batches of