In my case, commenting out the following lines in
/etc/network/interfaces fixed this issue as well as the issue of Network
Manager not starting on startup, two issues which had cropped up after
an upgrade to ubuntu 12.04
auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth0
Marking as Won't fix, as unfortunately none of the fixes mentioned
before seem to deal with all the cases and they all sound like they
might cause significant breakage if they go wrong.
So far what was mentioned is that somewhere between 8.04 and 10.04, we
switched from having Network Manager igno
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
Title:
"Waiting for network configuration" due to uncommented 'auto' lines
Yeah, though in this case I don't see how we could have automatically
detected it.
The initial installation (based on kernel versions) was Ubuntu 8.04
which apparently was still writing interface entries in
/etc/network/interfaces even when using Network Manager (we don't do
that anymore).
Now, t
Adam: Can you provide the same information as karaluh then so I can see
what's going on in your case and whether you'd need to report this as a
separate bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
[Another emailed bug comment that never showed up on Launchpad...]
I have encountered this bug on my laptop, which has been running Ubuntu
since early 2008 when I got it, and its hardware has never changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ok, so these logs show that when you installed your machine, you had a single
network interface, called eth0 at the time which was an Nvidia network card
with MAC address:
00:0c:76:7e:fe:89
Nowadays, the only piece of nvidia hardware you seem to have is a graphic card.
Your network cards now ar
/var/log/installer/syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/900903/+attachment/2714817/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
/var/log/kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/900903/+attachment/2714812/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9
/etc/udev/rules.d/70-persistent-net.rules
** Attachment added: "70-persistent-net.rules"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/900903/+attachment/2714811/+files/70-persistent-net.rules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Can you attach the following information?
- /etc/udev/rules.d/70-persistent-net.rules
- /var/log/kernel.log
- /var/log/installer/syslog
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
Reassigning to ifupdown. If this is a problem with some default
/etc/network/interfaces file as produced by the Ubuntu installer at an
earlier date, we should try to track that down and fix up the interfaces
files on upgrade if we can.
** Package changed: upstart (Ubuntu) => ifupdown (Ubuntu)
**
** Summary changed:
- "Waiting for network configuration"
+ "Waiting for network configuration" due to uncommented 'auto' lines in
/etc/network/interfaces (historical installer/upgradebug?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
> So the fix for this is for you to delete the lines showing 'eth0' in
/etc/network/interfaces.
Indeed, that solved the issue.
> Do you know if these lines were added by the system, or if you set
them up manually at some earlier point?
Hard to say, the system was dist-upgraded several times, so
Aha. So your /etc/network/interfaces includes an 'auto' line for eth0,
but your network device's name now is eth2; so the boot waits for an
eth0 that will never be brought up, but in the meantime Network Manager
brings up the real network on eth2.
So the fix for this is for you to delete the line
1334 ?S 0:00 /sbin/dhclient -d -4 -sf
/usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-
eth2.pid -lf /var/lib/dhcp/dhclient-77ab34ef-20a6-48ce-b3d9
-c0bcb29a50bc-eth2.lease -cf /var/run/nm-dhclient-eth2.conf eth2
--
You received this bug notification because you ar
Is dhclient running on this system, then? (ps awx| grep dhclient)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
Title:
"Waiting for network configuration"
To manage notifications about this
> Can you please also attach the otuput of this command:
> grep dhclient /var/log/syslog
No output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
Title:
"Waiting for network configuration"
karaluh,
Ok, that all looks correct, so I don't know what's causing this problem.
Can you please also attach the otuput of this command:
grep dhclient /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
> In both of your cases, is the machine connected to a network at boot time,
> and when the boot finally continues, is the
> network working?
Yes and yes.
> Please show the output of this command:
> ls -ld /var/run
lrwxrwxrwx 1 root root 4 2012-01-14 22:53 /var/run -> /run
--
You received thi
On Wed, Jan 11, 2012 at 02:42:41AM -, Adam Porter wrote:
> This happened on my laptop which is not plugged into an Ethernet
> connection but uses wireless.
> After commenting out these lines:
> #auto eth0
> #iface eth0 inet dhcp
> ...it booted.
Ok. This is all expected behavior then, exce
$ ls -ld /var/run
lrwxrwxrwx 1 root root 4 2012-01-07 20:12 /var/run -> /run
The /var/run->/run transition happened correctly when I upgraded.
This happened on my laptop which is not plugged into an Ethernet
connection but uses wireless.
After commenting out these lines:
#auto eth0
#iface eth0
In both of your cases, is the machine connected to a network at boot
time, and when the boot finally continues, is the network working?
Please show the output of this command:
ls -ld /var/run
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/etc/network/interfaces
** Attachment added: "interfaces"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/900903/+attachment/238/+files/interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I have encountered the same problem immediately upon rebooting after upgrading
to Oneiric. Here is my /etc/network/interfaces file, which is has NOT CHANGED
since upgrading from Natty to Oneiric:
# This file describes the network interfaces available on your system
# and how to activate the
please attach the contents of /etc/network/interfaces from the affected
system.
** Changed in: upstart (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
T
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903
Title:
"Waiting for network configuration"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/9
27 matches
Mail list logo
