Upstart - handling stop when the process is killed

Question

I have upstart configuration for my java process:

/etc/init/myjar.conf

description "my jar"
author "me"

start on runlevel [2345]
stop on shutdown

expect fork

script
    chdir /opt/myjar/
    java -jar myjar.jar >/var/log/myjar/myjar.log 2>&1
end script

post-start script
    emit myjar-local_running
end script

The service works fine, apart from the following scenario:

1. process is killed from outside, i.e: killall java
2. trying to stop the service: sudo service myjar stop <--- hanging......

The process is in the following state:

myjar start/killed, process 123

Can't restart it either...

Any help would be appreciated.

Answer 1

According to upstart manual expect fork:

   Upstart will expect the process executed to call fork(2) exactly once.

and according to comment 5 in init: job stuck with expect fork/daemon when parent reaps child bug:

when you use "expect fork" or "expect daemon" combined with "script", Upstart ends up following the first spawned child whose exit status is reaped by the shell.

In your case, upstart probably follows chdir pid.

Your upstart script seems a task job because neither chdir nor java command fork, so, removing expect fork should fix the issue.