470,568 Members | 1,535 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,568 developers. It's quick & easy.

Connection reset by peer

I'm seeing this message a couple times per day in my postgres log:

2004-04-20 14:47:46 LOG: could not receive data from client:
Connection reset by peer

What does it mean? I've seen in the archives that it seems to be some
kind of system error. Does anyone know how serious this message is?
Does it mean that one of my clients is failing to connect or, worse,
losing data in transit?

I have about 200 clients and I'd like to reassure myself that nothing
is going drastically wrong. I have not had any complaints from users.

Joe

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 23 '05 #1
4 14884
Joe Lester <jo********@sweetwater.com> writes:
I'm seeing this message a couple times per day in my postgres log:

2004-04-20 14:47:46 LOG: could not receive data from client:
Connection reset by peer

What does it mean? I've seen in the archives that it seems to be some
kind of system error. Does anyone know how serious this message is?
Does it mean that one of my clients is failing to connect or, worse,
losing data in transit?


It generally means a client is exiting, or getting killed, without
shutting down the PG connection properly.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nov 23 '05 #2
Joe Lester <jo********@sweetwater.com> writes:
I'm seeing this message a couple times per day in my postgres log:

2004-04-20 14:47:46 LOG: could not receive data from client:
Connection reset by peer

What does it mean? I've seen in the archives that it seems to be some
kind of system error. Does anyone know how serious this message is?
Does it mean that one of my clients is failing to connect or, worse,
losing data in transit?


It generally means a client is exiting, or getting killed, without
shutting down the PG connection properly.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nov 23 '05 #3
That makes sense since the "connection reset by peer" statement is
always followed immediately by

"unexpected EOF on client connection"

I should have noticed that before :-0

Thanks!

On Apr 20, 2004, at 10:04 PM, Doug McNaught wrote:
Joe Lester <jo********@sweetwater.com> writes:
I'm seeing this message a couple times per day in my postgres log:

2004-04-20 14:47:46 LOG: could not receive data from client:
Connection reset by peer

What does it mean? I've seen in the archives that it seems to be some
kind of system error. Does anyone know how serious this message is?
Does it mean that one of my clients is failing to connect or, worse,
losing data in transit?


It generally means a client is exiting, or getting killed, without
shutting down the PG connection properly.

-Doug

---------------------------(end of
broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 23 '05 #4
That makes sense since the "connection reset by peer" statement is
always followed immediately by

"unexpected EOF on client connection"

I should have noticed that before :-0

Thanks!

On Apr 20, 2004, at 10:04 PM, Doug McNaught wrote:
Joe Lester <jo********@sweetwater.com> writes:
I'm seeing this message a couple times per day in my postgres log:

2004-04-20 14:47:46 LOG: could not receive data from client:
Connection reset by peer

What does it mean? I've seen in the archives that it seems to be some
kind of system error. Does anyone know how serious this message is?
Does it mean that one of my clients is failing to connect or, worse,
losing data in transit?


It generally means a client is exiting, or getting killed, without
shutting down the PG connection properly.

-Doug

---------------------------(end of
broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Donnal Walter | last post: by
3 posts views Thread by mirandacascade | last post: by
reply views Thread by Joe Lester | last post: by
3 posts views Thread by Van_Gogh | last post: by
reply views Thread by xristoph | last post: by
5 posts views Thread by chrispoliquin | last post: by
2 posts views Thread by gigs | last post: by
1 post views Thread by livre | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.