Thread: Help on "unexpected EOF..client reset by peer" errors

Help on "unexpected EOF..client reset by peer" errors

From
Don Isgitt
Date:
Environment: Server running Redhat 3.2.3-20 on quad Xeon 2.4
                        Postgresql 7.4 compiled from source (gcc 3.2.3)
                        Application written in Perl (5.8.0) using Tk,
DBI and DBD
                        Client accessing DB using ODBC (7.03.02) from
Win XP box
Sample of errors follows:

2004-04-26 10:15:38 [24335] LOG:  00000: connection authorized:
user=djisgitt database=gds2
LOCATION:  BackendFork, postmaster.c:2451
2004-04-26 10:20:02 [24335] LOG:  08006: could not receive data from
client: Connection reset by peer
LOCATION:  pq_recvbuf, pqcomm.c:678
2004-04-26 10:20:02 [24335] LOG:  08P01: unexpected EOF on client connection
LOCATION:  SocketBackend, postgres.c:281
2004-04-26 10:22:39 [24339] LOG:  00000: connection received:
host=10.0.1.55 port=1337
LOCATION:  BackendFork, postmaster.c:2389
2004-04-26 10:22:39 [24339] LOG:  00000: connection authorized:
user=djisgitt database=gds2
LOCATION:  BackendFork, postmaster.c:2451

It happens sporadically; some days, maybe once or twice a day. However,
other days, like today, as you can see from this sample, it happens
exceedingly often , and is driving the user crazy.

The references in the archive only relate to JDBC, and I am not using that.

Any help greatly appreciated.

Don

p.s. Running the application on the same machine as the db, I do not get
these errors; but, that is local and linux, versus remote (lan, not
really remote) and windows.


Re: Help on "unexpected EOF..client reset by peer" errors

From
Doug McNaught
Date:
Don Isgitt <djisgitt@soundenergy.com> writes:

> 2004-04-26 10:20:02 [24335] LOG:  08006: could not receive data from
> client: Connection reset by peer
> LOCATION:  pq_recvbuf, pqcomm.c:678
> 2004-04-26 10:20:02 [24335] LOG:  08P01: unexpected EOF on client connection
> LOCATION:  SocketBackend, postgres.c:281

This means the client is crashing or dropping the connection--you need
to be looking at the client end for the problem.

-Doug