Ubuntu
upstart package

Random "Waiting for network configuration"

Bug #994862 reported by sefs on 2012-05-04

16

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	upstart (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

While booting (it does not happen all the time but enough to be annoying) I get the error...

"Waiting for network configuration"

After a few moments it would then say

"Waiting up to 60 more seconds for network configuration"

Then after it would say something along the lines of booting without a complete network configuration.

If i did a ifconfig then my network interface eth0 is not present. I would have to do a "/etc/init.d/networking restart" and then eth0 would appear in the ifconfig.

This does not happen all the time but enough to be an annoyance.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.5-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 4 17:52:56 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

sefs (sefsinc) wrote on 2012-05-04:

#1

Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")

Revision history for this message

sefs (sefsinc) wrote on 2012-05-04:

#2

interfaces Edit (635 bytes, text/plain)

interfaces

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-10:

#3

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upstart (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniil Ivanov (daniil-ivanov) wrote on 2012-06-21:

#4

This bug seems to be a duplicate of bug 940485.

Revision history for this message

sefs (sefsinc) wrote on 2012-09-08:

#5

Are you sure it's a dup? In that other case the guy does not seem to be concerned about the bug in itself, just that he can't skip it.

Revision history for this message

sefs (sefsinc) wrote on 2012-09-08:

#6

I need to have this as I boot computers over the LAN to admin them and if one boots with this bug then I would actually have to go to the machine or ask someone at the location to reboot until the message goes away.

A temporary measure I am using to get around this problem is this

create a file in /etc/init.d that forces the network to restart on each boot so no matter what after it reaches the login screen ever after the 60 second time out I will have a working network connection with out having to manually log in and restart the network to bring up ethX.

> sudo -i
> cd /etc/init.d
> nano forcenetworkrestartonboot

----
in this file place the script

      #!/bin/bash
      /etc/init.d/networking restart
      exit
---------
> chmod a+x forcenetworkrestartonboot
> update-rc.d -f forcenetworkrestartonboot defaults

So if I get that bug after the 60 seconds the network will restart by the time it hits the login screen I believe.

to remove this from runing on start up ...
> update-rc.d -f forcenetworkrestartonboot remove

and then delete /etc/init.d/forcenetworkrestartonboot

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.