I would like to second that this problem is active in 14.10.
System: Custom server with dual Intel Xeon E5-2630 CPU and dual ethernet ports
OS: Bare metal install of Ubuntu server 14.10 plus xfce4 (xubuntu) desktop
After the OS install, the system has consistently been hanging as
reported
This issue is manifesting itself again in 14.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
To manage
Dear Clint,
You are right. This is not an nm-applet issue, nm-applet not showing up
was an indicator of the problem.
It is however an upstart issue that happens with a fresh install as I
described in #22. I had not touched /etc/network/interfaces, its
settings were generated during system
Same problem here, not fixed at all in 12.04
History:
I did a fresh CLI install using wired ethernet connection (eth1)
Then update upgrade xubuntu-desktop
I enabled WIFI (eth0)
reboot
waiting for network configuration message
changed in /etc/network/interfaces to eth0 as primary network adapter,
Best workaround sofar:
http://askubuntu.com/questions/213614/waiting-for-network-configuration-problem
and
http://askubuntu.com/questions/144743/ubuntu-server-12-04-waiting-for-network-configuration-and-network-down
edit /etc/network/interfaces
Remove (or comment out) everything, only leave:
taj, I'm sorry that you're having issues. What you describe is not
related to this bug. If you have configured anything in
/etc/network/interfaces, then it has nothing to do with nm-applet or
NetworkManager. You will need to choose, either /etc/network/interfaces,
or NetworkManager. I recommend
hi.. I have the same problem on a pppoe connection.
pppoeconf adds
auto dsl-provider
to /etc/network/interfaces to start the pppoe connection at boot
but when there is a problem (dsl modem or provider) I have to wait every
time when I reboot.
Its there no may to add NET_NO_WAIT to
This bug seems to be a duplicate of bug 950662.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
To manage
Sorry, this is already the bug 950662.
I also experience this issue and here is my findings:
The delays are caused by failsafe boot delay (/etc/init/failsafe.conf)
which is started on:
start on filesystem and net-device-up IFACE=lo
and stopped on:
stop on static-network-up or starting rc-sysinit
static-network-up is emitted by /etc/network/if-up.d/upstart when all
static interfaces from /etc/network/interfaces are configured.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Excerpts from Uwe Mock's message of Sat May 12 11:11:02 UTC 2012:
This bug appeared on my brother's Samsung NC10 after an ubgrade from
Kubuntu 10.04 to 12.04. I have checked the interfaces file for invalid
entries, but everything was ok.
Hi Uwe. Please open a new bug report from the affected
This bug appeared on my brother's Samsung NC10 after an ubgrade from
Kubuntu 10.04 to 12.04. I have checked the interfaces file for invalid
entries, but everything was ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please consider reopening this bug. I have the most recent upstart for
precise:
ii upstart1.5-0ubuntu7 event-based init daemon
...and still see this issue if there's an invalid network interface
specified in /etc/network/interfaces using auto.
--
You received this bug notification
On Mon, May 07, 2012 at 05:45:41PM -, Alexander List wrote:
Please consider reopening this bug. I have the most recent upstart for
precise:
ii upstart1.5-0ubuntu7 event-based init daemon
...and still see this issue if there's an invalid network interface
specified in
I have the latest upstart as well (1.5-0ubuntu7). I do not have any
invalid network interfaces. I do have the Waiting for network
configuration..., the Waiting up to 60 more seconds for network
configuration..., and the Booting system without full network
configuration... messages every time I
Since Ubuntu 11.04 this message appear at boot, if there are static networks in
/etc/network/interfaces.
The bug (I prefer call it bad coding) continues in Ubuntu 12.04.
I had a static firewire network in /etc/network/interfaces:
auto firewire0
iface firewire0 inet static
address
This bug was fixed in the package upstart - 1.4-0ubuntu9
---
upstart (1.4-0ubuntu9) precise; urgency=low
[ Steve Langasek ]
* debian/conf/failsafe.conf: instead of waiting for the 'runlevel' event
before considering failsafe done, stop this job as soon as we're
starting
Error message has disappeared and it now takes only 10 seconds from when
the Ubuntu logo first appears to login prompt.
Many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Please show the output of the following commands on this system:
ls -ld /run
ls -ld /var/run
ls -l /run/network/
Please also attach the current /etc/network/interfaces file from the
system.
** Package changed: upstart (Ubuntu) = ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Output of commands:
$ ls -ld /run
drwxr-xr-x 21 root root 780 Mar 10 06:40 /run
$ ls -ld /var/run
lrwxrwxrwx 1 root root 4 Mar 9 22:31 /var/run - /run
$ ls -l /run/network
total 4
-rw-r--r-- 1 root root 6 Mar 10 06:39 ifstate
-rw-r--r-- 1 root root 0 Mar 10 06:39 ifup.lo
-rw-r--r-- 1 root root
So according to the contents of /run/network, all of your static
networks came up quickly and as intended, and the /run/network/static-
network-up-emitted directory confirms that the 'static-network-up' event
should have been generated.
This should have been sufficient to stop the 'failsafe' job
/etc/init/failsafe.conf is in the upstart package, so reassigning back
:)
** Package changed: ifupdown (Ubuntu) = upstart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
I agree with your position Steve. starting rc-sysinit is actually a
more accurate representation of the intent of failsafe anyway. Once rc-
sysinit has been started, we're no longer in danger of waiting forever.
There is the danger that some other job that is 'start on starting rc-
sysinit' then
Output of ls -l /etc/rcS.d:
$ ls -l /etc/rcS.d
total 4
-rw-r--r-- 1 root root 447 Feb 17 18:17 README
lrwxrwxrwx 1 root root 16 Mar 8 20:00 S25brltty - ../init.d/brltty
lrwxrwxrwx 1 root root 18 Mar 8 19:53 S37apparmor - ../init.d/apparmor
lrwxrwxrwx 1 root root 17 Mar 8 19:29 S55urandom -
** Branch linked: lp:ubuntu/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
To manage notifications about
Ah, apparmor also runs in /etc/rcS.d, so that could explain the delay
entirely. For now I'll assume that our change to failsafe.conf fixes
this.
** Changed in: upstart (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
28 matches
Mail list logo
