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

Re: CentOS & PostgreSQL help re: TIME_WAIT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Reggie Euser" <reggie(at)busicast(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: CentOS & PostgreSQL help re: TIME_WAIT
Date: 2010-01-28 20:55:33
Message-ID: 13891.1264712133@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Reggie Euser" <reggie(at)busicast(dot)com> writes:
> Zombie PostgreSQL processes in a "TIME_WAIT" state are consuming all
> available sockets on a web server I'm running. I've Googled & RTFM'ed but am
> still stumped.  Sure would appreciate any ideas.

That seems a bit confused.  There's no such thing as a "process in a
TIME_WAIT state".  A TCP network socket could be in TIME_WAIT but
it's not a process, and certainly not zombie.  Please be a little
clearer.

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?).

Postgres processes sitting in zombie state would indicate that the
postmaster has somehow gotten wedged and is failing to notice its
dead children.  That shouldn't happen really --- are you still able
to make connections to the database?  It doesn't seem like there'd be
any direct linkage between that and a network problem, but ...

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Kevin GrittnerDate: 2010-01-28 21:04:00
Subject: Re: CentOS & PostgreSQL help re: TIME_WAIT
Previous:From: Reggie EuserDate: 2010-01-28 19:36:32
Subject: CentOS & PostgreSQL help re: TIME_WAIT

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