Rainer Jung wrote: > On 25.07.2009 16:05, Rainer Jung wrote: >> 5) Starting a service only works using the ApacheMonitor or the Windows >> Service Control. Using the commandline httpd.exe I can not start the >> service. The event log shows: >> >> [Sat Jul 25 15:11:03 2009] [notice] Disabled use of AcceptEx() WinSock2 API >> >> (OS 10048)Normalerweise darf jede Socketadresse (Protokoll, >> Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden. : >> make_sock: could not bind to address 127.0.0.1:8000 >> >> no listening sockets available, shutting down >> >> Unable to open logs >> >> So there's a warning about using IP address or port twice. I did check, >> that no other process uses the port and starting via ApacheMonitor with >> the same config is no problem. So I guess (wildly), that we have a bug >> when starting from the commandline, resulting in the parent and the >> child both trying to do the bind. > > Additional logging shows: the commandline process sets up the listeners > for itself, and also the service when it tries to start.
Interesting because I see no similar fault (using 2.2.13-dev and will retest with 2.2.12). How are you invoking httpd.exe? What additional modules had you loaded? (Perhaps one also creates listening sockets?) If you simplify your config to apache httpd shipped modules, is all well again?
