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[1285595950.929353] add /devices/virtual/net/lo (net) UDEV_LOG=3 ACTION=add DEVPATH=/devices/virtual/net/lo SUBSYSTEM=net INTERFACE=lo IFINDEX=1 SEQNUM=1477 UDEV [1285595951.133203] add /devices/virtual/net/lo (net) UDEV_LOG=3 ACTION=add DEVPATH=/devices/virtual/net/lo SUBSYSTEM=net INTERFACE=lo IFINDEX=1 SEQNUM=1477 But system load hangs at network-interface.conf waiting for net-device- added. 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 a upstart start map generator: https://bitbucket.org/wodny/upstart-map Results attached. ** Attachment added: "Generated SVG map" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/497299/+attachment/1648596/+files/upstart.svg -- upstart not starting init-scripts (event net-device-up IFACE=lo missing) https://bugs.launchpad.net/bugs/497299 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
