[Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child

[Rich Wales]

I think I'm running into this bug on an Ubuntu Lucid server.  I tried to
install the rsyslog package on this server, but the start / stop /
restart functions would never complete (hangs forever).  In the end, I
had to abandon rsyslog and go back to sysklogd — bad solution, I need
rsyslog, but I obviously don't have a choice if it simply won't work.

There are a bunch of other packages on this same server which use
upstart-job as their init scripts; they seem to work OK as far as I'm
aware, but the fact that rsyslog won't work makes me nervous.

Lucid is supposed to be an LTS release with support until 2015 (server
edition), but is that fact going to help me in practice (i.e., is
upstart ever going to be fixed for Lucid)?  If I were to decide to
upgrade this server to Maverick, is there any realistic reason to
suppose that would help?

Should I simply scrounge around for an old-style init script for rsyslog
to run on this server?

Is there some other solution I should be looking at?

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/406397

Title:
  init: job stuck with expect fork/daemon when parent reaps child

Status in Upstart:
  Triaged
Status in “aiccu” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Invalid
Status in PLD Linux Distribution:
  New

Bug description:
  Hi

  Wrong use of the expect fork stanza can create job with status
    job stop/killled, process nnn
  without any process nnn running on the system.

  As an example the following avahi.conf should have used
  "expect daemon", but will instead create a stuck job.

  stop on stopping dbus-system
  respawn
  expect fork
  exec avahi-daemon -D

  /Emil Renner Berthing

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/406397/+subscriptions