httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27869] New: - stopping and starting httpd again immediately causes bind() to fail
Date Tue, 23 Mar 2004 13:30:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27869>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27869

stopping and starting httpd again immediately causes bind() to fail

           Summary: stopping and starting httpd again immediately causes
                    bind() to fail
           Product: Apache httpd-2.0
           Version: 2.0-HEAD
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: worker
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: misiek@pld.org.pl


The problem is that when using threaded MPM (like worker) and do
httpd -k stop
+ immediately start httpd again then it will fail with message
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down

It seems that some threads do not end immediately and still use tcp port so bind 
fails. This happens only when some client is connected. If I stop httpd and wait 
for some time then after disconnection of client thread exits and I can start 
new httpd without any problems.

It seems like setting SO_REUSEADDR on listening sockets is good idea (or making 
httpd -s stop wait for all children/threads to exit).

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message