I failed to install Apache 2.0.59 because of the following error (I
translate from Polish language):
(OS 10048)Only one use of each socket address (protocol | network
address/port) is permitted. :make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Note the errors or messages above, and press the
Could you help me please?
/RAM/
R.A.M. wrote:
> I failed to install Apache 2.0.59 because of the following error (I
> translate from Polish language):
>
> (OS 10048)Only one use of each socket address (protocol | network
> address/port) is permitted. :make_sock: could not bind to address 0.0.0.0:80
> no listening sockets available, shutting down
> Unable to open logs
> Note the errors or messages above, and press the
>
> Could you help me please?
> /RAM/
>
>
Something else is already listening on port 80...
Norm
Post removed (X-No-Archive: yes)
"R.A.M."
news:fiemks$hj9$1@news2.task.gda.pl:
> I failed to install Apache 2.0.59 because of the following error (I
> translate from Polish language):
>
> (OS 10048)Only one use of each socket address (protocol | network
> address/port) is permitted. :make_sock: could not bind to address
> 0.0.0.0:80 no listening sockets available, shutting down
> Unable to open logs
> Note the errors or messages above, and press the
> 19...
>
> Could you help me please?
> /RAM/
>
>
>
Something else is already listening on port 80. What OS? Flavor?
>netstat -ln
On Mon, 26 Nov 2007 15:53:13 +0100, R.A.M. wrote:
> I failed to install Apache 2.0.59 because of the following error (I
> translate from Polish language):
>
> (OS 10048)Only one use of each socket address (protocol | network
> address/port) is permitted. :make_sock: could not bind to address
> 0.0.0.0:80 no listening sockets available, shutting down Unable to open
> logs
> Note the errors or messages above, and press the
> 19...
>
> Could you help me please?
> /RAM/
As already stated, you've got a web server running already - or something
else on port 80. If running linux,
lsof -P -i :80 will show ( hopefully ) what's using it.
telnet localhost 80, followed by
get / http/1.1
( that's 2 x return afterwards ) will hopefully show an error message
from the web server that is running, and allow you to identify it.
hth, Steve.
U¿ytkownik "Mark Taylor"
news:Xns99F4982F2AFF7mtaylorxxlrimcom@38.119.97.3...
> Something else is already listening on port 80. What OS? Flavor?
>
>>netstat -ln
I use Windows XP.
netstat -n produces (I use Polish language):
Protokó³ Adres lokalny Obcy adres Stan
TCP 10.0.3.20:1027 142.68.180.132:48617 USTANOWIONO
TCP 10.0.3.20:1071 153.19.250.122:119 USTANOWIONO
TCP 127.0.0.1:1025 127.0.0.1:18350 USTANOWIONO
TCP 127.0.0.1:18350 127.0.0.1:1025 USTANOWIONO
In fact, I have Cassini Web server installed but it is not running. I don't
have IIS, nor any other webserver.
Please help.
/RAM/
I have tried to reinstall apache using port 8080. Unfortunately I receive
the same problem with port 80 (!). Why 80, not 8080?
Could you help me please?
/RAM/
On Fri, 30 Nov 2007 12:37:59 +0100, R.A.M.
wrote:
> U¿ytkownik "Mark Taylor"
> news:Xns99F4982F2AFF7mtaylorxxlrimcom@38.119.97.3...
>> Something else is already listening on port 80. What OS? Flavor?
>>
>>> netstat -ln
>
> I use Windows XP.
> netstat -n produces (I use Polish language):
>
> Protokó³ Adres lokalny Obcy adres Stan
> TCP 10.0.3.20:1027 142.68.180.132:48617 USTANOWIONO
> TCP 10.0.3.20:1071 153.19.250.122:119 USTANOWIONO
> TCP 127.0.0.1:1025 127.0.0.1:18350 USTANOWIONO
> TCP 127.0.0.1:18350 127.0.0.1:1025 USTANOWIONO
netstat -a -n -b
search for the process hogging port 80
--
Rik
"Rik Wasmus"
news:op.t2rqt0cs3yk0ne@metallium.lan:
> On Fri, 30 Nov 2007 12:37:59 +0100, R.A.M.
> wrote:
>
>> U¿ytkownik "Mark Taylor"
>> news:Xns99F4982F2AFF7mtaylorxxlrimcom@38.119.97.3...
>>> Something else is already listening on port 80. What OS? Flavor?
>>>
>>>> netstat -ln
>>
>> I use Windows XP.
>> netstat -n produces (I use Polish language):
>>
>> Protokó³ Adres lokalny Obcy adres Stan
>> TCP 10.0.3.20:1027 142.68.180.132:48617 USTANOWIONO
>> TCP 10.0.3.20:1071 153.19.250.122:119 USTANOWIONO
>> TCP 127.0.0.1:1025 127.0.0.1:18350 USTANOWIONO
>> TCP 127.0.0.1:18350 127.0.0.1:1025 USTANOWIONO
>
> netstat -a -n -b
>
> search for the process hogging port 80
That should be
netstat -ln
You missed the lower case "L"