Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 96545 invoked by uid 500); 3 Dec 2002 05:44:48 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 96523 invoked from network); 3 Dec 2002 05:44:48 -0000 Received: from leveltwo.com (HELO mail.leveltwo.com) (207.108.197.10) by daedalus.apache.org with SMTP; 3 Dec 2002 05:44:48 -0000 Received: from rje (rje.lti [10.127.61.3]) by mail.leveltwo.com (Postfix) with ESMTP id 10BA9B229A for ; Mon, 2 Dec 2002 19:03:49 -0800 (PST) Reply-To: From: "Bob Eby" To: Date: Mon, 2 Dec 2002 18:50:29 -0800 Message-ID: <4BB02C541824D311921600902765DB7B02F50E18@LTISERVER> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: [users@httpd] Apache 2 installation issues The apache2.0 installer can't successfully install a default apache service if port 80 is not available during installation. This is true whether a default .msi install is done, or whether apache.exe is invoked at the command line. I can see no reason for this user-unfriendly behaviour, especially during .msi installation. After encountering this problem myself on a stock Win2k machine (which I'd forgotten to down IIS services for) I searched the bug database to see what was being done. Bug #14382 at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14382 was very interesting. The initial bug seemed to be someone who wasn't aware of this issue, trying to install and getting no service. The response pointed out after fixing a port problem, the following command could be used to install the service: "bin\apache -k install -n Apache2". What is the root problem here? 1) The .msi installer for apache 2.0 can't install the apache service if port 80 is already locked during installation. Further, the error reporting is marginal at best in this situation(30 second dialog), and recovery is "extremely lacking". At the very least, it would seem appropriate to address this in the .msi installer and/or associated distributables. 2) The command "bin\apache -k install -n Apache2" won't install the apache service if port 80 is already open for listening. Perhaps this is all well and good, but I have to wonder exactly why the process can't be installed anyway. Whether it works or not would seem to be an issue for when the service is actually started. (Yes, I should always run at the command line before installing the service, but I still don't see how that applies to this marginal failing in user-friendliness for win NT/2K/XP users) -Bob beby@leveltwo.com P.S. - Perhaps I should have put this in a bug report, but the FAQ said to contact the community first... --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org