Upstart jobs can enter “zombie” state that require reboot
Bug #1043332 reported by
Armin Ronacher
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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:/
strace of init and the service command: https:/
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.
Revision history for this message
| Armin Ronacher (mitsuhiko) wrote | #1 |
Revision history for this message
| Cameron Norman (cameronnemo) wrote | #2 |
To post a comment you must log in.
The pid wraparound trick works btw. I got it to start applications until it spawned a new dummy with that pid: https:/
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?)