initctl stop doesn't kill post-start?

Asked by Alex Nekrasov on 2009-04-16

Upstart 0.3.9

I have a service that hangs in post-start, so that both main and post-start are running forever.

I do initctl stop <service>.

- initctl status displays it as (stop) post-start
- pre-stop is never called
- if I don't provide a pre-stop, post-stop isn't called and main isn't killed

Is that intended behavior?

thanks,
Alex

Question information

Language:
English Edit question
Status:
Solved
For:
upstart Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Nekrasov
Solved:
2009-05-05
Last query:
2009-05-05
Last reply:
2009-05-05
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

no answer yet

It's intended behaviour, you can kill the errant post-start script with "kill" and that will stop the job. I agree that we need some kind of "forced stop" facility

Alex Nekrasov (ennnot) said : #4

Thanks.