New Apache 2.0.40 install - (99) cannot bind address

[BobMCT]

Apache Guru's;

I am attempting to start a development httpd server on RH8.0 using the
latest Apache 2.0.x distro from RHN. All seems to be installed
correctly.

When I try to start Apache I receive the error:
=================================================
(99)Cannot assign requested address: make_sock: could not bind to
address 65.86.41.245:80
no listening sockets available, shutting down
=================================================
Interestingly enough the referenced IP is the public IP of another
server running Apache 1.3.x and more importantly my /etc/hosts file,
the /etc/httpd/conf/httpd.conf file make NO reference to that IP or
any name resolving to that IP.

The public IP of the subject server is 65.86.41.247 and the FQDN for
this new server points to it. Also, the actual DOMAIN name resolves
to the same correct IP. Only ONE DNS entry (for mail) resolves to the
referenced IP address.

I've been working on this for a week, can get no answers from the
"Free" RH support (email or phone) and every hint suggestion or
otherwise I find on google groups, the web, tons of apache manuals,
etc. that I've tried will NOT rectify this issue.

Can some kind helpful Apache admin PLEASE provide some more detailed
recommendations other than RTFM to help a frustrated sysadm???

Thank so much.

(I shoulda been an underwater welder!)

 

[RhythmAce]

Check your httpd.conf file again and look for the 'Listen' directive. It should be uncommented and set to the eth0 ip for that machine. The 'ServerName' will be the name that machine is known as on your intranet. It seems to already be listening on port 80 so that is ok unless ALL port 80 traffic is forwarded to the other server. I'm gonna assume the machine knows its own ip address.

 

[BobMCT]

RythmAce (what do you play?);
The Listen directive is/was set to the public IP of the server in question. I tried both the public AND the private addresses. Also the servername is the FQDN of that server (fdcx1.financialdatacorp.com). Our DNS and /etc/hosts file points properly.

And, check this, I even dropped apache on the referenced server and the startup still complains that it cannot bind to that other servers address.

Go figure!

I searched again and there appears to be nothing in my httpd.conf file that refers to either the IP address supposedly conflicting nor any domain references that point to that IP.

Any other ideas as to what to look for? I'm really STUMPED!

Thanks for any suggestions.

 

[BobMCT]

For any frustrated newbies reading this you might want to save for
future reference. In my httpd.conf file there was an Include conf.d/*
directive which instructs apache to include ALL the conf files in the
specified directory. Well, deeeeep within the SSL conf was a hard
reference to the conflicting IP address. Stupidly, as I was NOT
starting with SSL I assumed that the SSL would not matter. Well, we
ALL know what "assume" means.

Hope this resolution helps someone else in the future...


Bob