On Fri, 19 Jan 2001, Mark Basil wrote:
> Date: Fri, 19 Jan 2001 04:28:10 -0500
> From: Mark Basil <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: RE: Apache port 80 problem
>
> Ok, let me describe this once more. Upon trying to reload Apache (port 80),
> the following is what happens:
>
> Everything appears to be in working order. Httpd is running -- ps aux shows
> this. However, when attempting to view a website, it just hangs. A telnet
> to port 80 give a 'connection refused' error. When I checked the logs, the
> error was something to the effect of "address already in use: cannot bind to
> port 80". I checked httpd.conf, and everything there seems good. When
> checking netstat, nothing shows up under :www or :80. Also, an lsof -i
> returns all secure ports *:443, but NONE at all for *:80. I have no clue
> what this could possibly be. Although, since I can't seem to find anything
> running on port 80, could the "address already in use" be something
> different? Not a port, but something else? Thanks again everyone.
>
> --Mark
>
I recently saw this error myself, so give this a try. First of all, run
the 'ps auxw | grep httpd' command again. Now take a look and see how many
httpd processes you see owned by root. You should only see one. If you
see more than one is because you have two Apache daemons running, hence
the "collission" and the inability to bind to port 80. It's in use by the
other daemon.
This happens some times when you install Apache from both RPM and tarball
and somehow manage to screw the init scripts. At least, this is what
happened the last time I saw the error.
There is another thing you may want to check into too. Take a look at
the httpd.conf file and see if you're specifying an IP address there that
may be incorrect. Perhaps that could explain the "address already in use"
error.
Still, I have a feeling the problem is this. When you start the system,
the httpd daemon starts from the init scripts. However, when you telnet
to the local port 80 or use your browser, your system is _also_ configured
to spawn the _same_ daemon via inetd.conf or xinetd. Check into that,
and make sure that Apache is configured in _only_ one of those two places.
That should do it, I believe.
--
------------------------------------------------------
Nitebirdz
------------------------------------------------------
"We all know Linux is great... it does infinite
loops in 5 seconds." (Linus Torvalds)
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
