Bug#463783: It doesn't start only if eth1 is not properly configured.

On Monday 04 February 2008, Aleksey Zapparov wrote:
> Today I've found out that if my eth1 is configured upon boot
> via DHCP or manually (depends on /etc/interfaces) then
> everything is ok and apache is starting up.
>
> By default my eth1 is configured to get config from DHCP.
> But when I run my laptop at home - I have no LAN with DHCP
> there yet - it is not starts.
>
> I've tried to start it manualy (sudo invoke-rc.d apache2 start) and
> it throwed error:
> ixti@msi-s300:~$ sudo invoke-rc.d apache2 start
> Starting web server: apache2[Mon Feb 04 17:15:12 2008] [crit] (EAI
> 9)Address \
> family for hostname not supported: alloc_listener: failed to set up
> \ sockaddr for 127.0.0.1

Maybe you are missing the loopback interface? Is something like

auto lo
iface lo inet loopback

present in your /etc/network/interfaces? When apache refuses to start, does /sbin/ifconfig show that 127.0.0.1 is configured?

Cheers,
Stefan

-- 
To UNSUBSCRIBE, email to debian-apache-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org