net-device-added ($INTERFACE=lo) event missed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
This bug report was originally posted as a comment to bug #497299 (https:/
Problem exists on one of machines with Lucid 10.04.1.
upstart 0.6.5-7
ifupdown 0.6.8ubuntu29.1
It seams that the "net-device-added" event that should have come from upstart-udev-bridge (caused by a udev event) gets lost somewhere.
In a udev logfile there is:
KERNEL[
UDEV_LOG=3
ACTION=add
DEVPATH=
SUBSYSTEM=net
INTERFACE=lo
IFINDEX=1
SEQNUM=1477
UDEV [1285595951.133203] add /devices/
UDEV_LOG=3
ACTION=add
DEVPATH=
SUBSYSTEM=net
INTERFACE=lo
IFINDEX=1
SEQNUM=1477
But system load hangs at network-
As it was said (for example bug #543506), one can do one of at least 3 things to continue the process:
1) telinit 2
2) initctl emit -n net-device-up IFACE=lo LOGICAL=lo ADDRFAM=inet METHOD=loopback
3) initctl emit net-device-added INTERFACE=lo
But there is one more thing that works:
udevadm trigger
This one seams to replay udev events and net-device-added is noticed.
So for me the most interesting part is to find out why upstart-udev-bridge or upstart loses some events.
As an additional project I've created an upstart start map generator: https:/
Results attached.
Changed in upstart (Ubuntu): | |
status: | New → Confirmed |
I have this same issue but on a server I recently upgraded to Maverick. The net-device-added seems to be lost. Resulting in certain NFS mounts not being mounted (show stopper for me).
dpkg -l | grep upstart
ii upstart 0.6.6-3 event-based init daemon