Public bug reported: 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. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043332 Title: Upstart jobs can enter “zombie” state that require reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1043332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
