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

[Stefan Fritsch <sf@sfritsch.de>]

On Wednesday 01 October 2008, you 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

That's not the reason, then.

It seems that the 127.0.0.0/8 subnet is handled specially. I can bind 
to any address in that subnet without it being configured explicitly. 
I don't know where this behaviour comes from and why it does not work 
for you during boot. But I guess explicitly configuring the used ip 
addresses is always a good idea.

Cheers,
Stefan