Re: httpd driving me crazy.

On Tue, 2007-01-30 at 22:39 +0000, Andy Green wrote:
Aaron Konstam wrote:

Starting httpd: (98)Address already in use: make_sock: could not bind to
address [::]:80
(98)Address already in use: make_sock: could not bind to address

Which shows nothing Listening on port 80. One again FC6 has done me in.
Any explanations?

It's not FC6's fault :-)

The behavior is to do with a TCP connection that was made to the server
while it was alive, that hangs around for some time, 60 seconds or
whatever after the connection was closed on one side... that is what it
is meant to do.

If you amend your netstat to just -n and grep on :80, you should see the
client connection shown in TIME_WAIT. After the timeout completes, you
will be able to start Apache again.

-Andy

That is an interesting explanation but this error occurred the first
time I tried to start Apache so the connection was never opened in the
first place. netstat -n |grep :80
returns nothing.
and:
fuser -a -n tcp 80
returns: 80/tcp:

Anyone have any further ideas?

--
Aaron Konstam <akonstam@xxxxxxxxxxxxx>

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: httpd driving me crazy.
    ... Any explanations? ... The behavior is to do with a TCP connection that was made to the server ... If you amend your netstat to just -n and grep on:80, ... will be able to start Apache again. ...
    (Fedora)
  • SUMMARY: Lots of TIME_WAIT connection
    ... it worth to reduce a /dev/tcp parameter. ... Look a the following link for explanations: ... Subject: Lots of TIME_WAIT connection ... running Apache 1.3.31 to serve about 10 websites (http and https). ...
    (SunManagers)
  • Re: httpd driving me crazy.
    ... Address already in use: make_sock: could not bind to address ... Any explanations? ... The behaviour is to do with a TCP connection that was made to the server while it was alive, that hangs around for some time, 60 seconds or whatever after the connection was closed on one side... ...
    (Fedora)
  • Re: Why does socket:read() take so long to determine broken connection?
    ... That was one of the best explanations I have ever read. ... Doesn't explain "Connection reset by peer" though. ...
    (comp.lang.java.programmer)
  • Re: Sockets stuck in FIN_WAIT_1
    ... I did kill off Apache, and all the FIN_WAIT_1's stuck around, so the kernel is in fact sending these probe packets, every 60 seconds, which the client responds to... ... I don't think this helps since Apache sees the connection as long gone. ... This may be proved by killing off Apache, the connection still lives and while Apache is running, I have the max clients connected most of the time... ... server were talking about which caused the client to hang with a live ...
    (freebsd-stable)