Home / ubuntu / Questions / 63456
Accepted
Léo Léopold Hertz 준영
Asked: 2011-09-29 11:56:55 +0800 CST

"Waiting for network configuration" adding 3 to 5 minutes to boot time

  • 772

I get the following pieces of information at the startup, takes about 3 to 5 minutes, while normally about 1 minute:

Waiting network configuration
Booting system without full network configuration

I found after googling that I should change /etc/networks/interface. I commented out everything there but the problem remains:

# auto lo
# iface lo inet loopback

# auto eth0
# iface eth0 inet dhcp
# address 192.168.0.2
# netmask 255.255.255.0
# gateway 192.168.0.1
# broadcast 192.168.0.255

How can you make the startup of Ubuntu 11.10 faster?

boot

7 Answers

  1. First off, this is a new behavior, documented in the 11.10 release notes, that I actually developed together with Scott Moser as an effort to make server boot more reliable.

    Commenting out lo will mean you have no local network capability, which will break some programs when they try to use the network. It will also cause your system to never boot because it is so critical. So leave these two lines:

    auto lo
iface lo inet loopback

    The bits about eth0 meant that your machine was configured to wait for a dynamic address to be assigned to it before the network is considered UP. In pre-upstart versions of Ubuntu (8.10 and earlier), the system would have waited up to 60 seconds for this before continuing the boot. When upstart was added, this condition wasn't waited for anymore, because network interfaces that were not always expected to be plugged in are better managed by something like network-manager.

    So, if you have a server, you probably want to wait for a dynamic address, otherwise the system will boot without all of its networks available (which it does if it takes more than 2 minutes to get an address). If you have a laptop that you don't always expect to be plugged in to eth0, then configure eth0 in network manager, and remove only those lines from /etc/network/interfaces, which should get rid of your boot delay.

    Keep in mind, there's a known bug with VMware and dbus that also causes this message.

    • 38

  2. If you moved your OS from one machine to another it might be a good guess that udev created a configuration containing the mac address of your old network device which is different from the mac address of the network device from your new system.

    Try removing the following file then reboot your system and see if this solves the problem:

    /etc/udev/rules.d/70-persistent-net.rules
    • 8

  3. You're mixing 2 incompatible ways of assigning an address to a network interface.

    iface eth0 inet dhcp

    says "send out a DHCPDISCOVER packet to the physical local network, wait for a DHCPOFFER packet from a physically local DHCP server, and get the IP address from it (see http://www.rfc-editor.org/rfc/rfc1531.txt), while the rest of the lines assign values to the interface "manually". It's important that one gets the IP address assignment method right. If there is a DHCP server on your local network, you should use it. To do so, delete the "address", "netmask", "gateway", and "broadcast" lines.

    If you're not connected to an "administered" local area network (and don't have a DHCP server), and want to assign the IP address parameters manually, change the first line to:

    iface eth0 inet static

    and keep the "address", "netmask", "gateway", and "broadcast" lines. See http://www.rfc-editor.org/rfc/rfc5735.txt for details about which IP addresses are available for use. The parameters you have look OK to me.

    Read 

    man 5 interfaces

    simply commenting everything out is not the best path to happiness.

    • 6

  4. Seems like for me, the best solution for this problem was found at this linux site

    Basically, still calling /etc/init/failsafe.conf , but commenting out the two sleep calls that caused the delay. I don't really see why they were added, since my network is configured fine without the need for a delay.

    • 5

  5. I use 

    eth0 inet dhcp

    I don't see the point of waiting when there is no link (the cable is missing) There is no way dhcp can get the address if there is no media. This is a bug

    • 3

  6. I recently just had this same problem. I tried to go in and comment out the sleep time in /etc/init/failsafe.conf file and ended up with the system just continuously trying to boot. I fixed this error by booting into safe mode and droping into a root shell and doing the following so that I had rw privleges: 

    mount -o remount,rw /

    I then issued the following command which brought up the file so that I could edit it back to it's orginal state:

    sudo nano /etc/init/failsafe.conf

    Save and exit, then reboot the system.

    • 2
  7. Best Answer

    Use allow-hotplug instead of auto in the /etc/network/interfaces file, e.g., allow-hotplug enp0s25 then iface enp0s25 inet dhcp. This tells the server to not wait for the interface to light up with a dhcp answer. - - Dr. Zim's comment.

    • 2