[Bug 526940] Re: Typo in /etc/network/interfaces prevents system from booting
Stéphane Graber
stgraber at stgraber.org
Thu Jan 12 15:06:57 UTC 2012
Since Ubuntu 11.10, we now have a one minute timeout in our network
initialisation jobs.
** Changed in: ifupdown (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/526940
Title:
Typo in /etc/network/interfaces prevents system from booting
Status in “ifupdown” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: ifupdown
Hi,
I found an issue whereby a typo in /etc/network/interfaces can prevent
lucid from booting. I apologise if this should have been reported
against upstart or something different. I'm still getting used to
Lucid.
1. I'm using Ubuntu Lucid Server AMD64 - Alpha 2
2. Package version is ifupdown 0.6.8ubuntu29 (upstart 0.6.5-3)
3. I expect the system to boot, regardless of any errors in /etc/network/interfaces
4. A simple typo in /etc/network/interfaces will prevent the system from booting properly
This is the typo (note eth4 is used instead of eth3 in the second
line):
auto eth3
iface eth4 inet manual
up ifconfig eth3 0.0.0.0 up
The system will not boot with the above lines in the file...it gets
stuck. All I can see is the progress indicator which eventually turns
completely white. I would expect an error message or the system to
simply boot but this didn't happen.
This took quite a while to debug as there were no error messages that
let me know that my interfaces file was wrong. I only figured this
out by chance.
The fix is to boot the live CD, mount the system and fix the file.
Thanks,
Mark
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/526940/+subscriptions
More information about the foundations-bugs
mailing list