Apache Server configuration support - Apache v2.0.55 Install Problem.

This is Interesting: Free IT Magazines  
Home > Archive > Apache Server configuration support > February 2006 > Apache v2.0.55 Install Problem.





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Apache v2.0.55 Install Problem.
Engelkott

2006-02-20, 5:57 pm



Hi!

When i try to install Apache (in Win XP) i get all the way through the
install and i get the following error message in a command window:

(OS 10048) Only one usage of each socket address (protacol/network
address/port) is normally permitted. : make_sock: could not bind to
address 0.0.0.0:80 no listening sockets available, shutting down.
Unable to open logs.

I am guessing this problem has come about because i installed a
different version of Apache a few days ago which i removed through the
Add/Remove Programs section of the Control Panel.

I know i can edit the Apache config file so the program listens on a
different port but this presents problems for me as i am setting up a
webserver across an internal network and could really do without
having to type :xxxx for the port number each time.

Can any kind soul tell me how to clear the socket reservation (or
whatever it is called) in Windows?

Many thanks,

Engelkott





Robert Ionescu

2006-02-20, 5:57 pm

Engelkott wrote:
> I am guessing this problem has come about because i installed a
> different version of Apache a few days ago which i removed through the
> Add/Remove Programs section of the Control Panel.


Well, if you did remove the other version of apache, it shouldn't run
now at all. Did you check the windows services (services.msc)?

But may be IIS is listening on port 80? Take a look into your windows
services panel. IIS usually runs as "www publishing service".

--
Robert
Engelkott

2006-02-20, 5:57 pm

On Mon, 20 Feb 2006 19:53:29 +0100, Robert Ionescu
<robsiegen@googlemail.com> wrote:

>Engelkott wrote:
>
>Well, if you did remove the other version of apache, it shouldn't run
>now at all. Did you check the windows services (services.msc)?
>
>But may be IIS is listening on port 80? Take a look into your windows
>services panel. IIS usually runs as "www publishing service".


Thanks for your response.

The previous version of Apache (v1.3.34) uninstalled with no reported
problems and ran perfectly fine on port 80.

IIS have never been installed as part of XP and sure enough it is not
listed in the services panel and neither is Apache because of the port
conflict.

Is there any util i can run to see what programs are listening to
which port?

Engelkott




MikeDawg

2006-02-20, 5:57 pm

netstat

frange5tan@onetel.com

2006-02-20, 8:49 pm

Ok. I'm getting a similar problem with Apache on XP Pro.. Go to your
DOS Command Prompt Window. Change the directory to C:\windows by typing
cd c:\windows and pressing Enter. At the new c:windows> prompt type
netstat -ano and press enter You will get a list of Active Connections.
Look down the list for Port 80 (e.g. 127.0.0.1:80) then look across at
the PID. This will tell you the number of the process that is using
Port 80. Then scroll down to your c:windows> prompt again and type
tasklist
Press Enter and you will get a list called Images and PID processes by
name (e.g. apache.exe) Look down the PID column to see the PID number
and in the Images column it'll show you the process that is using Port
80! I hope that helps you...

But in my case, the process using socket 127.0.0.1:80 is PID 1688 which
on the tasklist is, believe it or not, Apache.exe or at least 336K of
it. However, 1,236K of Apache.exe is also using Port 5472 (which may
not be a listening port) and ApacheMonitor.exe is using Port 3704
(which also may not be a listening port). As far as I can see I have
installed Apache 2.0.55 ok, and get the test page at http://local host/
but when I try to start Apache I get the make_sock cannot bind error
message again, as so many people have done. And that's even when
Apache.exe is actually listening to Port 80 through the httpd.conf
config file. So I'm rather confused and cannot see any way of solving
this myself. What should happen when you start Apache anyway? Any
guidance from anyone would be appreciated. TIA. frangepan.

Engelkott

2006-02-21, 5:56 pm

On 20 Feb 2006 17:52:27 -0800, frange5tan@onetel.com wrote:

>Ok. I'm getting a similar problem with Apache on XP Pro.. Go to your
>DOS Command Prompt Window. Change the directory to C:\windows by typing
>cd c:\windows and pressing Enter. At the new c:windows> prompt type
>netstat -ano and press enter You will get a list of Active Connections.
>Look down the list for Port 80 (e.g. 127.0.0.1:80) then look across at
>the PID. This will tell you the number of the process that is using
>Port 80. Then scroll down to your c:windows> prompt again and type
>tasklist
>Press Enter and you will get a list called Images and PID processes by
>name (e.g. apache.exe) Look down the PID column to see the PID number
>and in the Images column it'll show you the process that is using Port
>80! I hope that helps you...
>
>But in my case, the process using socket 127.0.0.1:80 is PID 1688 which
>on the tasklist is, believe it or not, Apache.exe or at least 336K of
>it. However, 1,236K of Apache.exe is also using Port 5472 (which may
>not be a listening port) and ApacheMonitor.exe is using Port 3704
>(which also may not be a listening port). As far as I can see I have
>installed Apache 2.0.55 ok, and get the test page at http://local host/
>but when I try to start Apache I get the make_sock cannot bind error
>message again, as so many people have done. And that's even when
>Apache.exe is actually listening to Port 80 through the httpd.conf
>config file. So I'm rather confused and cannot see any way of solving
>this myself. What should happen when you start Apache anyway? Any
>guidance from anyone would be appreciated. TIA. frangepan.


Hi!

Thanks for your very detailed feedback! I will try your suggestion out
a little later on as i went back to Apache v1.3.34 and that version
works perfectly well.

This annoys me greatly but what can you do? Well, i can and will
install v2.0.55 again and try your suggestion out! :-)

Thanks again,

Engelkott




Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com