Problem with connection dropping

--000e0cd2be6e2bee6d04673efb03
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I'm seeing some intermittent issues with a client who is trying to connect
to my Postgres server using the ODBC driver. I have about 15 customers who
are able to connect without issue, but one seems to be having problems.

Here's what I'm seeing in the server's log file

xx.xxx.xxx.xxx(1351) 2009-04-10 21:08:20 EDT LOG: connection authorized:
user=xxx database=xxx
....
xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: could not receive data
from client: Connection timed out
xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: unexpected EOF on client
connection
xx.xxx.xxx.xxx(1089) 2009-04-10 21:25:49 EDT LOG: process 24517 acquired
ShareLock on transaction 2282399 after 609040.428 ms
xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: disconnection: session
time: 0:17:30.678 user=xxx database=xxx host=xx.xxx.xxx.xxx port=xxxx

My best guess is that they are connecting, something is getting hung up, and
when they try to reconnect, they aren't able to do so.

I'm somewhat stuck as to where to start looking for a solution. Can anyone
assist?

Thanks in advance--

Jeff Wigal

--000e0cd2be6e2bee6d04673efb03
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I'm seeing some intermittent issues with a client who is trying to conn=
ect to my Postgres server using the ODBC driver.=A0 I have about 15 custome=
rs who are able to connect without issue, but one seems to be having proble=
ms.=A0


Here's what I'm seeing in the server's log file


xx.xxx.xxx.xxx(1351) 2009-04-10 21:08:20 EDT LOG:=A0 connection authori=
zed: user=3Dxxx database=3Dxxx
...
xx.xxx.xxx.xxx(1351) 2009-04-10 21=
:25:49 EDT LOG:=A0 could not receive data from client: Connection timed out=


xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG:=A0 unexpected EOF on clie=
nt connection
xx.xxx.xxx.xxx(1089) 2009-04-10 21:25:49 EDT LOG:=A0 proce=
ss 24517 acquired ShareLock on transaction 2282399 after 609040.428 ms
x=
x.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG:=A0 disconnection: session =
time: 0:17:30.678 user=3Dxxx database=3Dxxx host=3Dxx.xxx.xxx.xxx port=3Dxx=
xx


My best guess is that they are connecting, something is getting hung up=
, and when they try to reconnect, they aren't able to do so.=A0
>I'm somewhat stuck as to where to start looking for a solution.=A0 Can=
anyone assist?


Thanks in advance--

Jeff Wigal


--000e0cd2be6e2bee6d04673efb03--

Re: Problem with connection dropping

"Jeff Wigal (Referee Assistant)" writes:
> I'm seeing some intermittent issues with a client who is trying to connect
> to my Postgres server using the ODBC driver. I have about 15 customers who
> are able to connect without issue, but one seems to be having problems.

> Here's what I'm seeing in the server's log file

> xx.xxx.xxx.xxx(1351) 2009-04-10 21:08:20 EDT LOG: connection authorized:
> user=xxx database=xxx
> ...
> xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: could not receive data
> from client: Connection timed out
> xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: unexpected EOF on client
> connection

Is he allowing the connection to sit idle? If so, this might represent
a router timeout. What network hardware is between your machine and
this customer's?

regards, tom lane

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Fwd: Problem with connection dropping

--000e0cd6ac102a9dda04677949fa
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Not 100% sure what's going on with the network between here and there. He's
on a Time Warner or Comcast residential network between his PC in Colorado
and my server down in Georgia.

He's not intentionally leaving a connection open. When things go as they
should, the entire transaction lasts about 3-4 minutes from connection to
disconnect. From a programming perspective, I'm pretty careful to
explicitly open and close connections with the program.

Any ideas?


On Fri, Apr 10, 2009 at 11:27 PM, Tom Lane wrote:

> "Jeff Wigal (Referee Assistant)" writes:
> > I'm seeing some intermittent issues with a client who is trying to
> connect
> > to my Postgres server using the ODBC driver. I have about 15 customers
> who
> > are able to connect without issue, but one seems to be having problems.
>
> > Here's what I'm seeing in the server's log file
>
> > xx.xxx.xxx.xxx(1351) 2009-04-10 21:08:20 EDT LOG: connection authorized:
> > user=xxx database=xxx
> > ...
> > xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: could not receive data
> > from client: Connection timed out
> > xx.xxx.xxx.xxx(1351) 2009-04-10 21:25:49 EDT LOG: unexpected EOF on
> client
> > connection
>
> Is he allowing the connection to sit idle? If so, this might represent
> a router timeout. What network hardware is between your machine and
> this customer's?
>
> regards, tom lane
>

--000e0cd6ac102a9dda04677949fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Not 100% sure what's going on with the network between here and there.=
=A0 He's on a Time Warner or Comcast residential network between his PC=
in Colorado and my server down in Georgia.=A0

Re: Fwd: Problem with connection dropping

"Jeff Wigal (Referee Assistant)" writes:
> Not 100% sure what's going on with the network between here and there. He's
> on a Time Warner or Comcast residential network between his PC in Colorado

Ick ...

> He's not intentionally leaving a connection open. When things go as they
> should, the entire transaction lasts about 3-4 minutes from connection to
> disconnect.

Well, your log shows about 17 minutes between connection and timeout,
so apparently things didn't go well. I'd like to think that Comcast
doesn't cut connections after just a minute or two of idle time, but
they might well drop 'em at ten or so minutes.

If your server platform supports it, setting tcp_keepalives_interval
to a few minutes might prevent the drop.

regards, tom lane

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc