Rainer Jung wrote: > On 25.07.2009 18:36, William A. Rowe, Jr. wrote: >> 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? > > httpd -k uninstall > httpd -k install > httpd -k start
You -do- understand that the service control manager can be very poor at completing a service removal until the next reboot? There are lots of interesting delays to uninstalling. I presume you -k stop'ed first. It has bitten me more than once. Maybe your "shut down now" comment is a really brilliant idea :) > httpd -k install myserv > httpd -k start myserv I hope you mean -n in there ... Cut and paste would give me more confidence in helping you debug instead of chasing ghosts :) > Default config except for the disabled acceptex and non-standard port > 8000. No 3rd-party modules. I disabled acceptex, as you had (standard port though) on a guess that it might be the difference. I never use the mode and deleted it already from trunk. > I'll happily retest with the official windows source archive and I'm > going to narrow it down. > > I saw that there's not really any difference in the winnt mpm between 11 > and 12, so I'll shut down now and come back when I really know the > reason. The above remark about the commandline process opening the > socket is somehow garbage. It was always like that, but the socket is > closed again directly before invoking the service. Give me a little time > for analysis before I broadcast more incomplete incomplete explanations. Sure thing, will look forward to hearing whatever you discover!
