Ok, I'm marking the bug in ifupdown as invalid because there isn't
anything to fix in ifupdown.
As for boot logging issues with upstart, it's a known issue and upstart
1.4 that will ship in 12.04 has a feature called "job logging" that will
populate /var/log/boot.log and /var/log/upstart/.log with
In summary, the root cause of the problem was a line in
/etc/network/interfaces which tried to run a non existent command (up
flush-mail).
ifup silently fails in that case, and although it has done almost
everything to start the interface, and the interface is fully
functional, it does not create
** Package changed: ubuntu => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885909
Title:
Boot process hangs in Ubuntu 11.10 server after upgrade
To manage notifications about thi
This turns out to have been a result of the following line in
/etc/network/interfaces:
up flush-mail
Removing this line allows the ifup command to complete and fully
configure the eth0 interface, which does emit the necessary events to
allow the boot process to continue.
Messages alerting the f
In searching the net, it has become obvious that Ubuntu 11.10 is
severely bug ridden, that the status of bugs that prevent the system
fully starting is trivialised, and there doesn't look to be a fix
anytime soon.
My system is 11.10 server, it has one external network interface, eth0
using on boar
