[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects

[yota]

Ok, I've experienced again the problem on a new machine on which quantal was installed from scratch.
This is everything I've done to solve all issues and get back to a fast 5 seconds shutdown with no filesystem corruption:

- rm /etc/init/modem-manager.conf (it's started by network manager via dbus, we don't need a separate conf...)
- edit /etc/init/modem-manager.conf and /etc/init/dbus.conf to stop also on "runlevel [06]" (i.e. add "or runlevel [06]" at the end of "stop on" line
- add a "cleanup" script (chmod 755) in /etc/network/if-down.d/ which does "killall dhclient" and "killall dnsmasq"

If the machine is upgraded from older ubuntu versions check that there
are no more references to /etc/init.d/networking from /etc/rc*.d
directories.

Probably at this point is not ifupdown that should be patched anymore, but I decided to post here since this is one of the bug that most users should land searching for the problem.
If the above changes work for other users then separate bugs against each involved package should be filed. I hope someone else can eventually take care of it.

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

Title:
  Upstartification of /etc/init.d/networking has lost deconfiguring-
  networking event causing bad side-effects

Status in “ifupdown” package in Ubuntu:
  Fix Released
Status in “ifupdown” source package in Quantal:
  Fix Released

Bug description:
  In precise, /etc/init.d/networking was a true SysV service script that
  did the following:

  initctl emit deconfiguring-networking

  In quantal, /etc/init.d/networking is now using the upstart-job
  symlink back to the upstart job /etc/init/networking.conf.

  The problem is that the 'deconfiguring-networking' is no longer being
  emitted. This causes dbus to fail to stop on system shutdown which
  causes a cascading effect whereby other Upstart jobs are also not shut
  down. Eventually, the system halt with the message:

  mount: / is busy

  This results in a unclean shutdown which can result in FSCK being run
  / slow / bad user boot experience.

  The two main options here are:

  1) Re-instate the 'deconfiguring-networking' event.
  2) Change the dbus 'stop on' condition and update upstart-events.7 to remove 'deconfiguring-networking'.

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