Re: CentOS & PostgreSQL help re: TIME_WAIT

No...


----- Original Message -----
From: "Renato Oliveira" <renato.oliveira@grant.co.uk>
To: "Reggie Euser" <reggie@busicast.com>; <pgsql-admin@postgresql.org>
Sent: Friday, January 29, 2010 10:15 AM
Subject: Re: [ADMIN] CentOS & PostgreSQL help re: TIME_WAIT


Do you have an F5 load balancer in front of these web servers?



Renato Oliveira
Systems Administrator
e-mail: renato.oliveira@grant.co.uk

Tel: +44 (0)1763 260811
Fax: +44 (0)1763 262410
http://www.grant.co.uk/

Grant Instruments (Cambridge) Ltd

Company registered in England, registration number 658133

Registered office address:
29 Station Road,
Shepreth,
CAMBS SG8 6GB
UK

-----Original Message-----


From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Reggie Euser
Sent: 29 January 2010 15:14
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] CentOS & PostgreSQL help re: TIME_WAIT

Thanks to both of you. Kevin, it's not a DoS, I'm certain; client problem,
maybe .

Tom - sorry for my confusion. I'm chasing the network/firewall possibilities
as most likely causes.  PostgreSQL is running quite smoothly.

FWIW, what little I know about PostgreSQL, I've picked up by using it,
reading documentation on the web and, most helpfully, reading your comments.
Many thanks again.


----- Original Message -----
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
>
> 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

>"Reggie Euser" <reggie@busicast.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


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



-----Original Message-----


P Please consider the environment before printing this email
CONFIDENTIALITY: The information in this e-mail and any attachments is
confidential. It is intended only for the named recipients(s). If you are
not the named recipient please notify the sender immediately and do not
disclose the contents to another person or take copies.

VIRUSES: The contents of this e-mail or attachment(s) may contain viruses
which could damage your own computer system. Whilst Grant Instruments
(Cambridge) Ltd has taken every reasonable precaution to minimise this risk,
we cannot accept liability for any damage which you sustain as a result of
software viruses. You should therefore carry out your own virus checks
before opening the attachment(s).

OpenXML: For information about the OpenXML file format in use within Grant
Instruments please visit our http://www.grant.co.uk/Support/openxml.html


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