touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #44989
[Bug 950662] Re: Waiting for network message on bootup when all network devices are up
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 above during the boot sequence.
Following the boot message: "Starting configure network device"
/etc/init/failsafe.conf displays these messages with the associated two
minute sleeps:
Waiting for network configuration...
Waiting up to 60 more seconds for network configuration...
Booting system without full network configuration...
However, shortly after the original "Starting configure network device"
message, I am able to ping both network interfaces from a remote
machine. It appears that although the interfaces are configured and
active, plymouth remains confused and fails to issue a successful
return code. This system was automatically configuring the two
interfaces as p1p1 and p2p1, so I have written an /etc/udev/rules.d/70
-persistent-net.rules file to rename these back to a more respectable
eth0 and eth1. However, the hanging problem preceded any of this
renaming activity.
This delay is a real pain and appears to affect quite a few people. It
would be good to pin down the nature of the problem and fix it once and
for all. This appears to extend back to at least 2011 and can be found
elsewhere under bug-ids 885596 and 881079.
Here are the particulars for my configuration:
-----------------------------------------------------------------
# cat /etc/network/interfaces
#
auto lo
iface lo inet loopback
#
auto eth0
iface eth0 inet static
address 204.107.91.3
netmask 255.255.255.0
gateway 204.107.91.254
dns-nameservers 199.181.164.1 199.181.164.2 68.87.69.146 68.87.85.98
#
auto eth1
iface eth1 inet static
address 204.107.91.4
netmask 255.255.255.0
gateway 204.107.91.254
dns-nameservers 199.181.164.1 199.181.164.2 68.87.69.146 68.87.85.98
-----------------------------------------------------------------
# ifconfig -a
eth0 Link encap:Ethernet HWaddr e0:3f:49:e8:1a:31
inet addr:204.107.91.3 Bcast:204.107.91.255 Mask:255.255.255.0
inet6 addr: fe80::e23f:49ff:fee8:1a31/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5704 errors:0 dropped:0 overruns:0 frame:0
TX packets:4706 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2651217 (2.6 MB) TX bytes:707849 (707.8 KB)
Interrupt:16 Memory:b3f00000-b3f20000
eth1 Link encap:Ethernet HWaddr e0:3f:49:e8:1a:32
inet addr:204.107.91.4 Bcast:204.107.91.255 Mask:255.255.255.0
inet6 addr: fe80::e23f:49ff:fee8:1a32/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1117 errors:0 dropped:0 overruns:0 frame:0
TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:140077 (140.0 KB) TX bytes:14374 (14.3 KB)
Interrupt:17 Memory:b3e00000-b3e20000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:893 (893.0 B) TX bytes:893 (893.0 B)
virbr0 Link encap:Ethernet HWaddr 56:ac:3d:07:64:e8
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
-----------------------------------------------------------------
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default router 0.0.0.0 UG 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0
cjsanet * 255.255.255.0 U 0 0 0 eth0
cjsanet * 255.255.255.0 U 0 0 0 eth1
-----------------------------------------------------------------
# cat /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="e0:3f:49:e8:1a:31", ATTR{dev_id}=="0x0",
ATTR{type}=="1", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="e0:3f:49:e8:1a:32", ATTR{dev_id}=="0x0",
ATTR{type}=="1", NAME="eth1"
-----------------------------------------------------------------
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
Status in upstart package in Ubuntu:
Fix Released
Bug description:
Machine is an Asus EeePC 900, running a fresh (post-beta1) install of
Precise.
I get a "waiting for network" message on bootup, even though eth0 is
connected and wlan0 is active and within range of the access point.
Commenting out lines in /etc/network/interfaces doesn't make any
difference.
The message doesn't appear every time but bootup is still annoyingly
slow.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.4-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Fri Mar 9 22:19:09 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120306)
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/950662/+subscriptions
