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

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

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?

Reply to:

Follow-Ups:
- Bug#500558: apache2.2-common: Apache fails to start on boot after upgrade Etch -> Lenny
  - From: Micha Lenk <micha@lenk.info>

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>

Prev by Date: apache2_2.2.9-10_i386.changes ACCEPTED
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