Skip site navigation (1) Skip section navigation (2)

Re: CentOS & PostgreSQL help re: TIME_WAIT

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Reggie Euser" <reggie(at)busicast(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: CentOS & PostgreSQL help re: TIME_WAIT
Date: 2010-01-28 21:04:00
Message-ID: 4B61A760020000250002ED0B@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
 
> In general, sockets sitting a long time in TIME_WAIT would be a
> network problem.  That state means the user process already closed
> the socket and the network stack is waiting for the other end to
> acknowledge connection closure.  If it's not getting the ACK then
> you have either buggy network code in one kernel or the other, or
> a network-level problem (maybe an overaggressive firewall in
> between?).
 
Not to discount those possibilities, but I've seen one other cause:
a storm of connection attempts.  It could be a DoS attack or a
poorly written client.
 
-Kevin

In response to

Responses

pgsql-admin by date

Next:From: Greg SpiegelbergDate: 2010-01-28 21:11:03
Subject: Re: Restore database from tablespace
Previous:From: Tom LaneDate: 2010-01-28 20:55:33
Subject: Re: CentOS & PostgreSQL help re: TIME_WAIT

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group