Very slow boot when no internet connection is available

[Rodrigo Pinheiro]

Binary package hint: upstart

When I do not have a internet connection available the booting process halts at the middle and stops for almost a 1 minute. I used to have this problem at Ubuntu Edgy but it stopped when I upgraded my system to Feisty. I don't know why, but with last Feisty update this problem showed up again.

ProblemType: Bug
Architecture: i386
Date: Wed Apr 4 23:01:36 2007
DistroRelease: Ubuntu 7.04
Uname: Linux rodrigo-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

[Guillaume ARCHAMBAUD (drarchy)]

Hello,
have you seen this bug ?
https://launchpad.net/bugs/69941
Do you experience the same problem ?
Thanks.

[Rodrigo Pinheiro (ametade)]

Hi there,

I don't have that problem with my laptop. After booting my Feisty works
perfectly. I just have a very slow Feisty boot.

Thanks.

Qua, 2007-04-04 às 22:26 +0000, Guillaume ARCHAMBAUD escreveu:
> Hello,
> have you seen this bug ?
> https://launchpad.net/bugs/69941
> Do you experience the same problem ?
> Thanks.
>

[Scott James Remnant (Canonical) (canonical-scott)]

Please install the bootchart package, then reboot; once the boot completes, you should have a file in /var/log/bootchart - please attach that to the bug.

Also please attach your /etc/network/interfaces file

[Rodrigo Pinheiro (ametade)]

Hi there,

I sent you four bootchart images. The first one is without internet connection at eth0 but with the wireless interface on (Intel Pro/Wireless 3945). The second is with no eth0 connection and with the wireless card disconnected. The third is with internet connection available at eth0 and with the wireless card on. Finally, the fourth is with eth0 on and with wireless off.

It seams that the problem happens when there is no internet connection at eth0.

[Rodrigo Pinheiro (ametade)]

I noticed that I had an extra ip configured for eth1. I commented it out but the problem still exists.

My /etc/network/interfaces now looks like:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth2 inet dhcp

#iface eth1:1 inet static
#address 192.168.1.226
#netmask 255.255.255.0
#broadcast 192.168.1.255

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

[Tom Inglis (tominglis)]

Hi Guys,

I am also having this bug in Kubuntu Feisty after recent updates. It seems to occur when eth0 is not connected.

Bestest,

Tom

[Unai Goikoetxeta (bockbilbo)]

I also have the same problem on my laptop.

In my opinion, it seems to be something related with the network configuration, more specifically with the fact that Ubuntu tries to get a dhcp offer from the eth0 interface when it's not connected.

At least, that's what it first came out of my mind after looking at my one bootcharts and Rodrigo's, which are almost the same.

[Fred_D (fdonelly)]

I noticed this as well after doing updates on my test disc. It looks like everything is waiting for the network initialization to timeout before continuing startup.

I have only used this machine wireless network, which has WPA running, so it can't connect until I log in and enter my key manager password.

[Sero (sero4linux)]

I can confirm this problem on Dell Inspiron 6000 with up-to-date Feisty install. Boot hangs for more then one minute on networking. I have no cable attached to eth0 and WPA2 setup on eth1 (ipw2200).

Let me know if anymore input is needed.

[Unai Goikoetxeta (bockbilbo)]

I also have a wpa2 setup on eth1 using ipw2200... not sure if this is a common setup for all of us who are having this problem.

[Tom Inglis (tominglis)]

No, I have ath0 using Atheros 5006EG. But it happens when there is no eth0
plugged in and whether or not ath0 is connected.

On Monday 9 April 2007 17:39:27 Unai wrote:
> I also have a wpa2 setup on eth1 using ipw2200... not sure if this is a
> common setup for all of us who are having this problem.

[David Fokkema (dfokkema)]

Shouldn't this be a bug of the initscripts package (and not sysvinit?). Initscripts is installed on Feisty by default, superseding sysvinit.

[Launchpad Janitor (janitor)]

[Expired for sysvinit (Ubuntu) because there has been no activity for 60 days.]