[Bug 1043332] Re: Upstart jobs can enter “zombie” state that require reboot

[Armin Ronacher]

The pid wraparound trick works btw.  I got it to start applications
until it spawned a new dummy with that pid:
https://gist.github.com/d55199e9b1ad7fc65504

Interestingly enough the pid shown in the status message was not the pid
that it actually tried to kill.  I suppose the problem is that on salt
update upstart expected it to demonize but the update did not go fully
through and the process instead did something else.  (Died after the
first fork?)

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

Title:
  Upstart jobs can enter “zombie” state that require reboot

Status in “upstart” package in Ubuntu:
  New

Bug description:
  It appears that a job can enter a special zombie state where it's
  neither alive nor dead and requires a system reboot to recover.

  IRC log with the discussion: https://gist.github.com/3512329
  strace of init and the service command: https://gist.github.com/5f9061af79bb8b38d240

  System environment: precise64 from the ubuntu cloud package (the amazon eu west AMI).
  After an upgrade of a service an upstart job corrupted and left it in a state where it neither starts now stops.

  It was later suggested on IRC that this might be by design.

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