[Bug 504989] Re: Upstart inconsistent state caused by aborting "stop [service]"

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 406397 ***
    https://bugs.launchpad.net/bugs/406397

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

** Changed in: upstart (Ubuntu)
       Status: New => Confirmed

-- 
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/504989

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

Status in “upstart” package in Ubuntu:
  Confirmed

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

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