god icon indicating copy to clipboard operation
god copied to clipboard

Published 20 hours ago • verified publisher icon mojombo

Can not stop after one "stop start" cycle

Open smclelland opened this issue 13 years ago • 5 comments

Simple watch on node.js. I have node writing out a pid file on start and pid_file param is pointing to it. Starting god up using -D, everything fires up perfectly. I threw in some debug output in a proc on the .start/.stop to see what's going on.

"god -c ..." -> myproc up

"god stop myproc" -> debug stop: killing (good so far)

"god status" myproc: unmonitored (good so far)

"god start myproc" -> debug start: starting (good so far)

"god stop myproc" ??????? (no so good)

"god status" myproc: up (huh? up?)

Looking at the god console. There is no "[ok] process is running for 'myproc'", yet status says its up?

Running on ubuntu 11 and ruby 1.9.2.

Basically I have to terminate god and manually kill the processes and start everything back up then I get one round of stopping/starting.

smclelland avatar Mar 31 '12 11:03 smclelland

@smclelland did you ever find out what was causing this issue? @eric I'm looking into this as I've stumbled into this issue, any ideas of what could be the cause of this?

sbryant avatar Mar 25 '13 17:03 sbryant

Okay, it seems that if I kill the process after issuing a stop command the command then proceeds.

sbryant avatar Mar 26 '13 03:03 sbryant

This happens if you specify a pidfile but your start command does not daemonize.

tmm1 avatar Mar 26 '13 03:03 tmm1

That was the problem.

sbryant avatar Mar 26 '13 05:03 sbryant

How do you get centaur On Mar 25, 2013 11:16 PM, "Aman Gupta" [email protected] wrote:

This happens if you specify a pidfile but your start command does not daemonize.

— Reply to this email directly or view it on GitHubhttps://github.com/mojombo/god/issues/91#issuecomment-15438770 .

ewock avatar Mar 26 '13 23:03 ewock