runsvdir does not start on boot

I can confirm this bug appearing on an i386 karmic install upgraded from jaunty.

On my system, editing /etc/init/runsvdir.conf so that

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

was replaced by

start on runlevel [2345]

seems to have fixed it.

I confirm that the fix works. This seems like an upstart bug though, isn't it?

Without a full specification of the conf file, it's impossible to say for certain. I couldn't find one, but I did find this:

http://upstart.ubuntu.com/wiki/ComplexEventConfig?highlight=((CategorySpec))

which suggests with the foo and bar example that multiple "start on" lines should be supported.

Regardless, we seem to have a fix and Karmic's been released. Is there someway we can get this fix pushed to the package?

Impact: runit is a collection of tools for process supervison. The bug causes runsvdir not to start. This causes all services managed by runit not to start defeating the entire purpose of the tool.

Patch Description: The bug appears to occur because of upstart not accepting multiple "start on runlevel" lines. The patch replaces these lines with a single line matching the format of other upstart scripts.

TEST CASE: Upon the system entering runlevels 2,3,4 or 5, the runsvdir process should be active.

Regression Potential: none foreseen.

+runit (2.0.0-1ubuntu4) karmic; urgency=low

Please version to 1ubuntu3.1, and target karmic-proposed instead of karmic.

As long as these are fixed, consider this an ACK from motu-sru and proceed with uploading the fixed debdiff!

Attached debdiff with suggested changes.

Thanks, taking for sponsoring

Uploaded now

This bug was fixed in the package runit - 2.0.0-1ubuntu4

---------------
runit (2.0.0-1ubuntu4) lucid; urgency=low

  [ Francis Russell ]
  * Upstart doesn't appear to accept multiple "start on runlevel" lines. Replace
    Upstart script with a version that uses a single line (closes LP: #439049).
 -- Chris Coulson <email address hidden> Sat, 07 Nov 2009 16:55:18 +0000

Accepted into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

The version in karmic-proposed works fine for me.

I manually added this fix and that worked for me. No problems so far.

This bug was fixed in the package runit - 2.0.0-1ubuntu3.1

---------------
runit (2.0.0-1ubuntu3.1) karmic-proposed; urgency=low

  * Upstart doesn't appear to accept multiple "start on runlevel" lines. Replace
    Upstart script with a version that uses a single line (closes LP: #439049).
 -- Francis Russell <email address hidden> Fri, 30 Oct 2009 14:43:13 +0000

Paket: runit
Zustand: Installiert
Automatisch installiert: ja
Version: 2.0.0-1ubuntu3.1

Still doesn't start when having multiple lines for runlevels. Works fine with the runlevels in one line as proposed in the first comment.

Ulf Klose,

the 2.0.0-1ubuntu3.1 package does precisely that. It defines a new config file with the runlevels on one line.

OK, sorry for the misunderstanding. Everything runs fine now.

Has anybody recently have problems with this? Since updating to 10.04, I can't even start the daemon manually. I'm looking around for the scripts but haven't found yet.

I'm running 10.04 and have had no issues. This bug specifically relates to to the issue that was caused by a broken upstart config file. Checking the source package right now, I see that the problem causing this bug is still fixed. Can I suggest you open a different bug against runit if you still can't solve your problem.