[Bug 771372] Re: procps runs too early in the boot process

[Clint Byrum]

Andreas, its likely that the update just fixed it for some use cases.
However, I would have expected it to fix your particular use case,
because your VLAN trunks should be up as soon as 'stopped networking' is
emitted, since that is emitted as soon as 'ifup -a' exits.

The error you see is likely because there are modules loaded later that
support your sysctl.conf settings, so some of them don't exist yet. It
shouldn't cause serious issues, but if you want to debug it, perhaps add
a 2> /run/sysctl.errors to see why it exitted.

As far as the libvirt issue, thats caused by libvirt's start on:

start on runlevel [2345] and stopped networking

This presents a potential race condition since 'stopped networking' may
happen after runlevel [2345]

Your best bet for a workaround is probably to add another condition to
procps so it reads

start on virtual-filesystems or stopped networking or starting libvirt-
bin

That will ensure that it runs before libvirt-bin is started.

I do actually think the fix for this is not complete, as we should still
be trying to set these sysctl settings before any services start on
them. I think this will require a larger refactoring, which we've been
discussing for the "Q" release cycle, so that there is a barrier between
bootup activities and starting of services.. and that would be an
abstract 'network-services' job.

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

Title:
  procps runs too early in the boot process

Status in “procps” package in Ubuntu:
  Fix Released
Status in “procps” source package in Lucid:
  Fix Released
Status in “procps” source package in Maverick:
  Fix Committed
Status in “procps” source package in Natty:
  Fix Committed
Status in “procps” source package in Oneiric:
  Fix Committed
Status in “procps” source package in Precise:
  Fix Released

Bug description:
  Binary package hint: upstart

  The start on criteria is for procps.conf is:
  start on virtual-filesystems

  This runs before some kernel modules are loaded, and procps applies
  the settings before they "exist", this is most noticed with network
  and network-related jobs (nfs, bridge).

  This bug may be considered a duplicate of LP Bug #690433.  I am
  opening a new one anyway, however because I think it's worth
  considering a more robust solution that would work for any possible
  kernel module.

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