Skip to content

May 16, 2012


Disable “Waiting for network configuration” messages on Ubuntu boot

I was just creating a custom live CD for Ubuntu 12.04 and was having a problem with the boot process hanging for several minutes while waiting for the network to be configured. I was trying to see if I could fix it but I have no idea why it is happening for now. I found a bug logged on LaunchPad here that describes a workaround for oneric (11.10) but this fix/workaround is there by default in precise so obviously it didn’t fix my problem.

I didn’t really need networking setup at all and just wanted to skip waiting for the network to be configured. In order to do this you just need to edit the file /etc/init/failsafe.conf. In that file is where it sleeps for several minutes waiting for the network to come up. All I did was:

sudo vim /etc/init/failsafe.conf

I changed the first sleep command to

sleep 5

and then commented out the following lines:

$PLYMOUTH message --text="Waiting for network configuration..." || :
sleep 40
$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :
sleep 59

Just place a ‘#’ character at the beginning of each of those lines. Now it will just wait 5 seconds and then continue on.

To my surprise, the network was actually working just fine even though the script thinks it is not.

Just a note, do NOT remove the failsafe.conf file, otherwise it will hang the boot process indefinitely waiting for the network to be “configured.”

Read more from Uncategorized
19 Comments Post a comment
  1. Thomas
    May 18 2012

    thx thx thx!! :)

  2. May 24 2012

    This does work to make it faster, but have you had any luck actually finding the root cause of the problem?

  3. Daniel
    May 28 2012

    Thanks for this information. It really works
    But actually why does boot waits?

    For me, this wait situation only happens when I change interface configuration file. (it’s network configuration)

    So it might be related, thought my network still works as I want.

    I don’t understand the need for this boot delay and for this messages

  4. Brandon
    May 28 2012

    yeah I don’t know…I wish I could find the root cause but this is as close as I could get

  5. nicoxxl
    Jun 18 2012
  6. Brandon
    Jun 18 2012

    I only had the local interface in /etc/network/interfaces as described in the post in your link and it still gave me the error and made me wait

  7. Alvaro
    Oct 24 2012

    check the file /etc/network/interfaces, the form correct is

    auto lo
    iface lo inet loopback

  8. Jan 24 2013

    @nicoxxl, @Alvaro, the suggestion to delete all but local loopback info from interfaces does not work in many situations. For instance, I get this extra wait when starting a KVM guest.. The network settings are properly configured with static IP (dhcp can’t be used as the guest is a server). But apparently network access is not available to the KVM guest at that stage of boot, hence the error. Commenting out the delays in failsafe.conf worked for me perfectly (the network works as expected upon completion of the boot sequence).

  9. nadrimajstor
    Mar 6 2013

    Here you can find some rationale on introducing failsafe.conf
    And a set of nice looking workarounds

  10. tim
    Aug 6 2013

    Thanks, this helped me!

  11. kiran
    Oct 26 2013

    Thank you

  12. Oct 27 2013

    腕時計 販売

  13. mcm セール デュベティカ クリーニング

  14. Steve
    Jan 9 2014

    Thank you for this perfect fix!!!!

  15. Jun 16 2014

    It’s a shame you don’t have a donate button! I’d definitely donate to this brilliant blog!
    I suppose for now i’ll settle for book-marking and adding your RSS feed to my Google account.

    I look forward to new updates and will share this site with my Facebook group.
    Talk soon!

  16. tuxmm
    Jul 8 2014

    Thank you for the workaround. This issue starting happening to me when I disabled networkmanager and instead installed wicd. Networkmanager would absolutely not connect to my WPA protected wifi, while wicd has no problem.

    So, I think the problem is related to networkmanager not finding a connection during the boot process. I love the failsafe workaround.

Trackbacks & Pingbacks

  1. Sta per essere rilasciata ABCbuntu 12.04f! | Abcbuntu's Blog
  2. Disable “Waiting for network configuration” messages on Ubuntu boot | Daniel M. Lofaro
  3. Ubuntu 14.04 Basic Setup | KAURI BLOG

Share your thoughts, post a comment.


Note: HTML is allowed. Your email address will never be published.

Subscribe to comments