Jaunty server 9.04 hangs on Configuring interfaces

try adding:

broadcast 192.168.13.255
gateway 192.168.13.1

to eth1, just humour it, the config will change nothing logically but may make the boot continue.

btw, nice trial and error to diagnose what part of the config is causing the issue :D

I've had similar problems. There is definitely a bug somewhere in the code which handles /etc/network/interfaces at boot up.

I've got the following setup:-

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.254

auto eth0:1
iface eth0:1 inet static
address 192.168.1.11
netmask 255.255.255.0

It get to 'Congifureing Interfaces' and just stays there for ever. If I comment out the eth0:1 alias, it boots up fine. I've tried adding network, broadcast and gateway parameters to the alias, but it just won't have it.

That said, I've found something which may be helpful. If I use /etc/init.d/networking stop to stop all my devices, it works fine, but ifconfig reports that lo is still present. With lo present I can type /etc/init.d/networking start and it works fine.
However if I use 'ifconfig lo down' to shut down all my loopback devices, then I call /etc/init.d/networking start, it hangs just like on boot up.
If I do the same, but instead type ifup -a (which is essentially what networking does), it hangs also.

I've tracked my problem down to /etc/network/if-pre-up.d/dhclient3-apparmor. If I remove it, everything boots just fine.

It looks like there is a line in dhclient3-apparmor which tests to see if apparmor is loaded and if not, it checks the runlevel. If that runlevel is either the first runlevel (ie booting up) or its in runlevel S, then it exits. If not, it sleeps for a second and tries again.

Problem is, in Ubuntu, the runlevel is 'unknown' so dhclient3-apparmor never gets out of that loop.

Changing the line in dhclient3-apparmor from:-

runlevel | grep -E -q '( [0-9]|[0-9] S)' && exit 0

to:-

runlevel | grep -E -q '( [0-9]|[0-9] S|unknown)' && exit 0

seems to fix it.

If you suspect this is a bug then I'd report it. If it is unique to your setup then leave it

Glad you got the gold :D

Simon Bazley: Your solutions solved my problem to.. after changing what you suggested it worked.. Im very happy, not funny to call the hosting operator to often and tell him to go and fix the problem :).

Thanks alot!

Thats why forums are great :D