[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#427580: marked as done (apache2: new install failed to start)

Your message dated Sat, 15 Nov 2008 22:51:16 +0100 (CET)
with message-id <Pine.LNX.4.64.0811152249460.32586@eru.sfritsch.de>
and subject line apache2: new install failed to start
has caused the Debian Bug report #427580,
regarding apache2: new install failed to start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
427580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427580
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.2.3-4
Severity: normal

I did a complete purge of apache/apache2
removed all directories and reinstalled apache2

on start (/etc/init.d/apache2 start) I received.
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
 failed!


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages apache2 depends on:
ii  apache2-mpm-worker            2.2.3-4    High speed threaded model for Apac

apache2 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- There is nothing we can do about this problem. The same occurs when some other process occupies port 80. 

Closing the report.

--- End Message ---
Reply to: