www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave McComb <mcc...@way.com>
Subject general/1791: Server hangs when a socket is hung in a CLOSE_WAIT state
Date Thu, 12 Feb 1998 06:24:07 GMT

>Number:         1791
>Category:       general
>Synopsis:       Server hangs when a socket is hung in a CLOSE_WAIT state
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Feb 11 22:30:00 PST 1998
>Originator:     mccomb@way.com
>Release:        1.2.5
SunOS fun.way.com 5.4 Generic_101945-27 sun4m sparc

The server gets hung on a CLOSE_WAIT state and the entire server must be rebooted
to correct the problem.  Trying to start Apache gives httpd: could not bind to port 80.

netstat -a shows:

home.lookonline.com.80 ww-tr03.proxy.aol.com.42518 61320      0  8335      0 CLOSE_WAIT 
0469                 proxy-155.iap.bryant.webtv.net.40469  8760      0  8395      0 CLOSE_WAIT
9341                 proxy-165.iap.bryant.webtv.net.39341  8760      0  8377      0 CLOSE_WAIT
home.trivialpursuit.com.80 proxy7.idirect.com.2691 17520      0  8204      0 CLOSE_WAIT
home.mlm-mall.com.80 scooter.pa-x.dec.com.3210 33580      0  8580      0 CLOSE_WAIT
problem recurs when a kill -HUP `cat httpd.pid` is issued.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]

View raw message