God appears to be leaving old god processes around indefinitely about god HOT 9 OPEN

I've been seeing this same issue. I've got 2 processed being monitored by god, but 6 leftover god processes running.

I'm running ruby-1.9.2-p180, god 0.11.0, and Ubuntu 10.04.2 and am also reloading the god config using the god load method.

Also - just saw issue #50 related to this.

from god.

Still having this issue.

$ god -V
Version: 0.12.1
$ ruby -v
ruby 1.8.7 (2011-12-28 MBARI 8/0x6770 on patchlevel 357) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.12

Happens every other load/unmonitor cycle, seemingly at random ...

Unfortunately makes God kinda useless as a watchdog ;(

from god.

+1

from god.

By the way, given this bug, it's particularly unclear whether "god load" is enough to load the new config AND restart current tasks or whether another "god restart" is needed. Another question I can't answer until this issue is resolved is: what's "god monitor" for? I thought putting monitoring behaviors inside my .god file was enough?

from god.

FYI this bug completely dissapeared for us after downgrading to REE 2011.03 (appears to be a known bug in the RVM affecting Ruby programs combining forking an threading).

@emirkin it's also unclear for me, although in my experience god load <config> always start the watch, except if you add the (undocumented) state argument:

god load <config> stop

Doesn't behave very consistently though.

from god.

@emirkin misunderstood your comment I think. Given this bug, if God crashes after spawning proceses (e.g. Rainbows! in our case) and you restart God and reload your config, a new process will be spawned.

Bottom line: a watchdog that crashes so often and doesn't behave properly when restarting isn't very helpful.

from god.

@mezis Based on what you're saying you did understand and answer my concerns. So now, I'm just waiting for the fix too

from god.

+1

from god.

👍

from god.