[Bug 881079] Re: "Waiting up to 60 more seconds for network configuration" at startup

Steve Langasek steve.langasek at canonical.com
Tue Oct 25 23:15:08 UTC 2011


Your kernel log shows:
Oct 26 00:14:20 marius-T1005 kernel: [   29.834585] init: networking pre-start process (882) exited normally
Oct 26 00:14:20 marius-T1005 kernel: [   29.834792] init: networking state changed from pre-start to spawned
Oct 26 00:14:20 marius-T1005 kernel: [   29.836729] init: networking main process (883)
Oct 26 00:14:20 marius-T1005 kernel: [   29.836878] init: networking state changed from spawned to post-start
Oct 26 00:14:20 marius-T1005 kernel: [   29.837730] init: networking state changed from post-start to running
Oct 26 00:14:20 marius-T1005 kernel: [   29.838538] init: mountall main process (330) exited normally
Oct 26 00:14:20 marius-T1005 kernel: [   29.838695] init: mountall goal changed from start to stop
Oct 26 00:14:20 marius-T1005 kernel: [   29.839091] init: mountall state changed from running to stopping
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.841294] init: networking main process (883) exited normally
Oct 26 00:14:20 marius-T1005 kernel: [   29.841447] init: networking goal changed from start to stop
Oct 26 00:14:20 marius-T1005 kernel: [   29.841902] init: networking state changed from running to stopping
Oct 26 00:14:20 marius-T1005 kernel: [   29.842391] init: Handling filesystem event
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.847223] init: failsafe goal changed from stop to start
Oct 26 00:14:20 marius-T1005 kernel: [   29.847592] init: failsafe state changed from waiting to starting
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.849781] init: rc-sysinit goal changed from stop to start
Oct 26 00:14:20 marius-T1005 kernel: [   29.850153] init: rc-sysinit state changed from waiting to starting
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.852407] init: mountall state changed from stopping to killed
Oct 26 00:14:20 marius-T1005 kernel: [   29.852810] init: mountall state changed from killed to post-stop
Oct 26 00:14:20 marius-T1005 kernel: [   29.854145] init: mountall post-stop process (885)
Oct 26 00:14:20 marius-T1005 kernel: [   29.854314] init: Handling stopping event
Oct 26 00:14:20 marius-T1005 kernel: [   29.854847] init: networking state changed from stopping to killed
Oct 26 00:14:20 marius-T1005 kernel: [   29.855591] init: networking state changed from killed to post-stop
Oct 26 00:14:20 marius-T1005 kernel: [   29.856230] init: networking state changed from post-stop to waiting
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.867779] init: failsafe state changed from starting to pre-start
Oct 26 00:14:20 marius-T1005 kernel: [   29.868357] init: failsafe state changed from pre-start to spawned
Oct 26 00:14:20 marius-T1005 kernel: [   29.869757] init: failsafe main process (890)
Oct 26 00:14:20 marius-T1005 kernel: [   29.870003] init: failsafe state changed from spawned to post-start
Oct 26 00:14:20 marius-T1005 kernel: [   29.871893] init: failsafe post-start process (891)
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.876002] init: Handling starting event
Oct 26 00:14:20 marius-T1005 kernel: [   29.876681] init: rc-sysinit state changed from starting to pre-start
Oct 26 00:14:20 marius-T1005 kernel: [   29.877185] init: rc-sysinit state changed from pre-start to spawned
Oct 26 00:14:20 marius-T1005 kernel: [   29.878751] init: rc-sysinit main process (893)
Oct 26 00:14:20 marius-T1005 kernel: [   29.878999] init: rc-sysinit state changed from spawned to post-start
Oct 26 00:14:20 marius-T1005 kernel: [   29.879409] init: rc-sysinit state changed from post-start to running
<snip>
Oct 26 00:14:20 marius-T1005 kernel: [   29.888296] init: mountall post-stop process (885) exited normally
Oct 26 00:14:20 marius-T1005 kernel: [   29.888547] init: mountall state changed from post-stop to waiting
Oct 26 00:14:20 marius-T1005 kernel: [   29.890138] init: failsafe post-start process (891) exited normally
Oct 26 00:14:20 marius-T1005 kernel: [   29.890389] init: failsafe state changed from post-start to running
<snip>
Oct 26 00:14:26 marius-T1005 kernel: [   36.841940] init: mountall-net state changed from stopping to killed
Oct 26 00:14:26 marius-T1005 kernel: [   36.842163] init: mountall-net state changed from killed to post-stop
Oct 26 00:14:26 marius-T1005 kernel: [   36.842353] init: mountall-net state changed from post-stop to waiting
Oct 26 00:14:26 marius-T1005 kernel: [   36.842755] init: Handling stopped event
Oct 26 00:14:35 marius-T1005 kernel: [   45.648127] wlan0: no IPv6 routers present
Oct 26 00:14:39 marius-T1005 kernel: [   50.094478] CE: hpet increased min_delta_ns to 20113 nsec
Oct 26 00:15:32 marius-T1005 kernel: [  103.090560] init: Connection from private client
Oct 26 00:15:32 marius-T1005 kernel: [  103.104503] init: Handling runlevel event
Oct 26 00:15:32 marius-T1005 kernel: [  103.105133] init: rc goal changed from stop to start
Oct 26 00:15:32 marius-T1005 kernel: [  103.105543] init: rc state changed from waiting to starting

So the rc-sysinit job has started already at 29.879 seconds after boot,
but doesn't actually hit the "telinit" command until 103.09 seconds
after boot.  That means something is going wrong while running
/etc/init.d/rcS.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/881079

Title:
  "Waiting up to 60 more seconds for network configuration" at startup

Status in “upstart” package in Ubuntu:
  Incomplete

Bug description:
  At bootup, while displaying the Ubutu logo, it says waiting for
  network configuration. Then it says: "Waiting up to 60 more seconds
  for network configuration", but seems to be stuck until enter key is
  pressed. Out of the syslog file it seems like it tries to start the
  wireless network already at bootup, but fails since the key to the
  network is only available in my user account after logging in.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.1.90-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] Ingen slik fil eller filkatalog
  Date: Mon Oct 24 21:36:06 2011
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   iface wwan0 inet dhcp
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 10.0.0.138 dev wlan0  proto static 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.1  metric 2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  Keyfiles: Error: [Errno 2] Ingen slik fil eller filkatalog
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, user)
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/881079/+subscriptions




More information about the foundations-bugs mailing list