[Backgroundrb-devel] trouble stopping backgroundrb
woody at crystalcommerce.com
Wed Sep 17 16:14:18 EDT 2008
I too have been having the same issue. Every time I try to restart
backgroundrb after an update to our application (about once a day), I
have to forcefully kill it myself. However, I haven't been able to
reproduce it in a controlled setting. After I kill and start it, it
all works ok. I tried killing packet_worker processes (even with -9),
but it still shuts down correctly on the stop command. I'll let it run
for a while and try tomorrow, but has anyone been able to predictably
reproduce the issue?
(debian etch, packet 0.1.10)
On Sep 16, 2008, at 9:11 AM, Ryan Case wrote:
> Hi folks -
> I'm having trouble getting backgroundrb to stop after one of the
> packet_worker_r processes dies.
> If backgroundrb is running properly,
> "/path/to/application/script/backgroundrb stop" works fine, but often
> one of the packet_worker_r processes dies, and the stop command no
> longer works after that (it runs, but it does not stop the processes,
> and so then start doesn't work).
> The only thing that seems to work at that point is to manually kill
> the processes that are still running, and then the start works, but
> that is going to make restarting via monit a lot less clean.
> Any ideas would be much appreciated!
> I'm using github version of backgroundrb, and packet 0.1.13 running
> on ubuntu.
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
More information about the Backgroundrb-devel