Hi Everybody,
I see in serverlog many entries that read:
gadb 2007-11-09 13:13:47 PST idle in transactionLOG: unexpected EOF on
client connection
gadb 2007-11-09 13:23:08 PST idle in transactionLOG: unexpected EOF on
client connection
gadb 2007-11-09 13:23:44 PST idle in transactionLOG:
On Nov 9, 2007 3:58 PM, Tena Sakai [EMAIL PROTECTED] wrote:
Hi Everybody,
I see in serverlog many entries that read:
gadb 2007-11-09 13:13:47 PST idle in transactionLOG: unexpected EOF on
client connection
gadb 2007-11-09 13:23:08 PST idle in transactionLOG: unexpected EOF on
client
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tena Sakai
Sent: Friday, November 09, 2007 3:58 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] idle in transaction...unexpected EOF on client
connection
Hi Everybody,
I see in serverlog many entries that read:
gadb 2007-11-09 13:13:47 PST idle
Campbell, Lance wrote:
I notice this in my log file as well. I do not have a fire wall that
would impact this.
It could be a monitoring tool that's opening the socket to check whether
Postgres is listening. If it connects then closes the socket without
actually talking the PG protocol, this
On Nov 9, 2007 4:29 PM, Alvaro Herrera [EMAIL PROTECTED] wrote:
Campbell, Lance wrote:
I notice this in my log file as well. I do not have a fire wall that
would impact this.
It could be a monitoring tool that's opening the socket to check whether
Postgres is listening. If it connects
: [ADMIN] idle in transaction...unexpected EOF on client connection
On Nov 9, 2007 3:58 PM, Tena Sakai [EMAIL PROTECTED] wrote:
Hi Everybody,
I see in serverlog many entries that read:
gadb 2007-11-09 13:13:47 PST idle in transactionLOG: unexpected EOF on
client connection
gadb 2007-11-09 13
Scott Marlowe [EMAIL PROTECTED] writes:
Hmmm. Well, when you see an error like unexpected EOF on client
connection then that means that the client disappeared without
closing the connection, or the network connection went away.
More specifically, the client didn't send the expected terminate
On Nov 9, 2007 4:36 PM, Tena Sakai [EMAIL PROTECTED] wrote:
Hi Scott,
Most likely what is happening is that you have a firewall between your
app and your db server that is closing idle connections after x minutes.
Thanks for your comment.
I hate to be disagreeable, but the app and
in transaction...unexpected EOF on client connection
Scott Marlowe [EMAIL PROTECTED] writes:
Hmmm. Well, when you see an error like unexpected EOF on client
connection then that means that the client disappeared without
closing the connection, or the network connection went away.
More
Tena Sakai escribió:
Aside from that, can this be caused by many deleted
rows from tables (and having neglected to vacuum)?
No.
--
Alvaro Herrerahttp://www.advogato.org/person/alvherre
Major Fambrough: You wish to see the frontier?
John Dunbar: Yes sir, before it's
10 matches
Mail list logo