[09:22] <Lion-Simba> Hi all. Is there any command in Upstart to reset job hanging in "stop/killed" status?
[09:22] <Lion-Simba> I'm trying to write my own job file for my service, and it don't work well yet. So, I need to debug it, but now I've stuck with this "stop/killed" state.
[09:31] <ion> Upstart’s current fork-tracking code is preliminary and gets confused easily. You probably used the ‘expect’ stanza claimin a certain style of daemonizing and the behavior of your main process was different. Can you reboot?
[09:32] <ion> http://heh.fi/tmp/workaround-upstart-snafu if not.
[09:33] <ion> ‘# workaround-upstart-snafu n’, where n is the pid ‘status jobname’ says, given that no such process actually exists.
[09:33] <Lion-Simba> Yes, I can. But I'm not very happy to do it every time during development.
[09:35] <ion> If you’re not absolute sure of the forking behavior of the main process, it’s better to make it not fork and not use the ‘expect’ stanza.
[09:35] <ion> ly
[09:36] <Lion-Simba> WOW! I've just started workaround-upstart-snafu without arguments... and it start output a lot of numbers (pids?) and not interruptable by ctrl+c
[09:37] <Lion-Simba> Not quite good behaviour..
[09:38] <ion> pkill -f workaround
[09:38] <ion> I never said it’s a good program. :-) As the name says, it’s a workaround.
[09:38] <Lion-Simba> Ok. It's died. )
[09:39] <Lion-Simba> But... ‘# workaround-upstart-snafu n' not helped.
[09:39] <Lion-Simba> Same numbers.
[09:41] <ion> Updated the file. Now it shouldn’t behave incorrectly when given no parameters.
[09:41] <ion> Exactly what does ‘status jobname’ print?
[09:42] <Lion-Simba> root@dahari:~# status stargazer
[09:42] <Lion-Simba> stargazer stop/killed, process 12148
[09:43] <ion> What does ‘ps -p 12148’ print?
[09:45] <Lion-Simba> Oh. It's over. I used workaround-upstart-snafu 12148 and wait a bit longer, letting it proceed with numbers. :) Now status is stop/waiting. Thank you. :)
[20:03] <cr3> when I run an upstart job on hary, initctl start doesn't return to the shell and just leave me hanging. if I ctrl-c, the process I exec'ed in my upstart job is running fine though