Upstart inconsistent state caused by aborting "stop [service]"

[Adam Nelson]

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@domU-12-31-38-00-0F-92:~/pline_render$ initctl status render
render start/killed, process 1248
ubuntu@domU-12-31-38-00-0F-92:~/pline_render$ ps -p 1248
  PID TTY TIME CMD
ubuntu@domU-12-31-38-00-0F-92:~/pline_render$

[Adam Nelson (adam-varud)]

Ubuntu 9.10
Upstart 0.6.3-11

[haraldkl (hk)]

Hi,
got the same with a script starting Xorg:

start on stopped rc
stop on runlevel [016]

expect fork
respawn

exec /usr/bin/Xorg

$ sudo stop basic-xserver
[hangs]

status basic-xserver
basic-xserver stop/killed, process 1611

pgrep Xorg
1545

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.