Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Issues with CLOSE_WAIT state

1 view
Skip to first unread message

arnab

unread,
Sep 3, 2008, 3:48:03 AM9/3/08
to
Hi All,
My webserver plugin module hangs when I do a lsof -i:listening port
output gives lots of CLOSE_WAIT.
Initially the state comes out as ESTABLISHED but as the CLOSE_WAIT
grows my server hangs.
What would be procedure in order to prevent this.Could it be causing
the web server to hang?
Apache Webserver version is 2.2.8 with MPM=worker and OS=Red-Hat
Release 3.0
Any help would be very much appreciated.
Thanks and regards
Arnab

Barry Margolin

unread,
Sep 3, 2008, 10:38:54 PM9/3/08
to
In article
<902554d4-131a-4afa...@z66g2000hsc.googlegroups.com>,
arnab <agang...@gmail.com> wrote:

> Hi All,
> My webserver plugin module hangs when I do a lsof -i:listening port

I assume there's a missing period there, not that doing lsof causes it
to hang.

> output gives lots of CLOSE_WAIT.
> Initially the state comes out as ESTABLISHED but as the CLOSE_WAIT
> grows my server hangs.
> What would be procedure in order to prevent this.Could it be causing
> the web server to hang?
> Apache Webserver version is 2.2.8 with MPM=worker and OS=Red-Hat
> Release 3.0
> Any help would be very much appreciated.
> Thanks and regards
> Arnab

It means that the module isn't closing the connection when the client
disconnects. It needs to detect the EOF from the client and call
close(). Another thing that can cause this is forking a child process
to handle the connection, and not closing the socket in the parent
(because the socket isn't really closed until all processes close their
fd).

--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

0 new messages