Upstart inconsistent state caused by aborting "stop [service]"
Bug #504989 reported by
Adam Nelson
This bug report is a duplicate of:
Bug #406397: init: job stuck with expect fork/daemon when parent reaps child.
Edit
Remove
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
I can't exactly reproduce this yet, but if you create a new service "render" that hangs:
exec Xvfb :25 -screen 0 1024x10000x24
Then:
sudo start render
[hangs Ctrl+c]
sudo stop render
[hangs Ctrl+c]
sudo stop render
stop: Job has already been stopped: render
However, since the process was killed, even though the PID is gone, initctl doesn't recognize that the PID is dead:
ubuntu@
render start/killed, process 1248
ubuntu@
PID TTY TIME CMD
ubuntu@
To post a comment you must log in.
Ubuntu 9.10
Upstart 0.6.3-11