Apache problems (socket)

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Apache problems (socket)

Postby pamfae » 12. April 2003 04:02

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]
pamfae
 
Posts: 1
Joined: 12. April 2003 03:56
Location: Cincinnati

Postby Oswald » 14. April 2003 18:09

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
User avatar
Oswald
Apache Friends
 
Posts: 2718
Joined: 26. December 2002 19:51
Location: Berlin, Germany
XAMPP Version: 5.5.19
Operating System: Linux

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

Postby chanio » 15. April 2003 05:32


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:
Gallactic Firewall
User avatar
chanio
 
Posts: 72
Joined: 18. March 2003 22:05
Location: Argentina

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

Postby Kristian Marcroft » 21. May 2003 12:30

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
User avatar
Kristian Marcroft
AF Moderator
 
Posts: 2962
Joined: 03. January 2003 12:08
Location: Diedorf

Postby AlexPausB » 21. May 2003 16:47

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!
AlexPausB
 
Posts: 471
Joined: 05. February 2003 11:19
Location: Fdorf

Postby Raven » 14. September 2003 16:34

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
Raven
 
Posts: 2
Joined: 14. September 2003 15:53
Location: MAss


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 48 guests