DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13368>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13368 Running IIS and Apache on same server, works on Apache 1.3.27, but not on 2.0.43 (server won't start) Summary: Running IIS and Apache on same server, works on Apache 1.3.27, but not on 2.0.43 (server won't start) Product: Apache httpd-2.0 Version: 2.0.42 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: All AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] We are currently running both MS IIS5 and Apache 1.3.27 simulatenously on several Windows 2000 Advanced Servers (W2K,sp3,current on all service/hotfixes as of 10/04), each web server has its own dedicated IP address. Now we are trying to upgrade to the new 2.x series of Apache and it is not working. FYI: Even with the 1.3.x series, we always have to start MS IIS first, then the Apache service, but at least it works this way, but not at all with 2.x. We have two IPs bound to the same NIC in the machines. I have configured IIS to bind specifically to its own IP in both the FTP and IIS settings within the MS Console. ------------- IIS is bound to 165.xxx.xxx.237 Apache is bound to 165.xxx.xxx.238 ------------- Starting Apache2 from command-line for the moment (starting via services yields the same failure) yields the following: D:\Apache2\bin\Apache.exe -w -n "Apache2" -k start (730048)Only one usage of each socket address (protocol/network address/port) i s normally permitted. : make_sock: could not bind to address 165.xxx.xxx.238:80 no listening sockets available, shutting down Unable to open logs *Please NOTE that is says 238 is occupied and unusable... IIS is bound to 237 not 238. This works fine on 1.3.27 The only change I have made at this point to the stock httpd.conf is around line #124 regarding the LISTEN directive: Listen 165.xxx.xxx.238:80 If I change the LISTEN directive to use a non-80 port, then it fires up just fine with IIS5 running. Once again I repeat, IIS5 is on IP#1 (237), Apache is on IP#2 (238). ------------- If I take a stock Apache 1.3.27 httpd.conf, then I apply the following to the LISTEN and BIND directives: Listen 165.xxx.xxx.238:80 BindAddress 165.xxx.xxx.238 I can run Apache 1.3.x and IIS5 at the same time without any problems. I can replicate this problem on 3 different servers (W2K Server, and (2) W2K Advanced Servers) ------------- My guess is that Apache 2.x is "incorrectly" detecting IIS's bind to the OTHER IP address on port 80, and then failing.... something in the startup bind/logic which was changed in the 2.x seems to be the blame at this point. I have not seen anyone else having similar issues when I have run Google web/group searches, and posting to the HTTP mailing list has yielded no one with a similar setup. -------------- I have confirmed this as working with Apache 1.3.24/26/27 and NOT working with Apache 2.0.42/43. I am using the PRE-compiled binaries provided by Apache.org and at the moment using PURE vanilaa stock httpd.conf setups just to prove the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
