Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny

To: Stefan Fritsch <sf@sfritsch.de>
Cc: 500558@bugs.debian.org
Subject: Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
From: Micha Lenk <micha@lenk.info>
Date: Wed, 01 Oct 2008 13:08:00 +0200
Message-id: <[🔎] 48E35A10.2090107@lenk.info>
Reply-to: Micha Lenk <micha@lenk.info>, 500558@bugs.debian.org
In-reply-to: <[🔎] 200810011303.07562.sf@sfritsch.de>
References: <20080929105319.5406.95704.reportbug@ian.lenk.info> <[🔎] 48E34DA6.8080800@lenk.info> <[🔎] 48E352E0.80701@lenk.info> <[🔎] 200810011303.07562.sf@sfritsch.de>

Hi Stefan,

Stefan Fritsch schrieb:
> On Wednesday 01 October 2008, Micha Lenk wrote:
>> I wonder why Apache is able to start without these explicitly added
>> addresses after boot has finished. What's the difference?
> 
> Yes, that's strange. What is the output from
> 
> cat /proc/sys/net/ipv4/ip_nonlocal_bind
> 
> after boot?

0

Regards
  Micha

Reply to:

Follow-Ups:
- Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
  - From: Stefan Fritsch <sf@sfritsch.de>

References:
- Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
  - From: Micha Lenk <micha@lenk.info>
- Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
  - From: Micha Lenk <micha@lenk.info>
- Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
  - From: Stefan Fritsch <sf@sfritsch.de>

Prev by Date: Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
Next by Date: Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
Previous by thread: Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
Next by thread: Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
Index(es):
- Date
- Thread