Page 1 of 1

Apache problems (socket)

PostPosted: 12. April 2003 04:02
by pamfae
I get this error when starting Apache.

C:\wampp2>apache\bin\apache.exe
[Fri Apr 11 23:04:57 2003] [crit] (OS 10038)Socket operation on non-socket: make
_sock: for address 127.0.0.1:81, apr_socket_opt_set: (SO_KEEPALIVE)
no listening sockets available, shutting down
Unable to open logs




I have modified the listen file many times and I still get that error.

Can anyone tell me how to get rid of this?

I am using WinME, does that make a difference?

I am not running another server, so far as I know...definitely not pws although it is installed.

Thanks for any help,

PFJ[/quote]

PostPosted: 14. April 2003 18:09
by Oswald
Dear pamfae!

I'm sorry to say, but I've no answer. It seems to be a very seldom and exotic problem. :( I tried out many things and searched many web sites. Only found a another similar - unanswered - posted by yourself in another forum.

(Just wanted to know you that your message was not lost and somebody tried to take care of your problem..)

Greetings,
Oswald

Let me try a hint (it doesn't hurt, does it?) :o

PostPosted: 15. April 2003 05:32
by chanio

Imagine that there is another previous thing listening to the :80 port.
Your smart Apache2 would try to find another socket to listen. What one? port 80 + 1 (81).
If you could scan your sockets (with some tool, see some freeware at www) you would be able to detect what is listening to that port:80. Actually a very common one (I think that is used for proxies, etc.).
Try selecting a 8765 port for Apache and see what happens.
The https uses a higher port (so both should be reserved).
Please, I appologize if I am speaking nonsence. I just tried to help from my limited (and newbie) experience.:oops:

Re: Let me try a hint (it doesn't hurt, does it?) :o

PostPosted: 21. May 2003 12:30
by Kristian Marcroft
chanio wrote:Imagine that there is another previous thing listening to the :80 port.
Your smart Apache2 would try to find another socket to listen. What one? port 80 + 1 (81).
If you could scan your sockets (with some tool, see some freeware at www) you would be able to detect what is listening to that port:80. Actually a very common one (I think that is used for proxies, etc.).
Try selecting a 8765 port for Apache and see what happens.
The https uses a higher port (so both should be reserved).
Please, I appologize if I am speaking nonsence. I just tried to help from my limited (and newbie) experience.:oops:


Hi chanio,

maybe you could try and post a bit smaller next time :)
I don't think we're blind here?

Thx
KriS

PostPosted: 21. May 2003 16:47
by AlexPausB
I think the NMap Portscanner is an useful tool for this... you can download a linux / windows version here:

http://www.insecure.org/nmap/

Greetings!

PostPosted: 14. September 2003 16:34
by Raven
i got the same problem, is there a way to make this work?

because from the answers above i didnt see any type of answer