Edit Question - KnowledgeHub

Title Body

I'm trying to understand how to monitor the resque worker for travis-ci with god in such a way that stopping the resque watch via god won't leave a stale worker process. In the following I'm talking about the worker process, not forked job child processes (i.e. the queue is empty all the time). When I manually start the resque worker like this: $ QUEUE=builds rake resque:work I'll get a single process: $ ps x | grep resque 7041 s001 S+ 0:05.04 resque-1.13.0: Waiting for builds And this process will go away as soon as I stop the worker task. But when I start the same thing with god ( exact configuration is here , basically the same thing as the resque/god example ) like this ... $ RAILS_ENV=development god -c config/resque.god -D I [2011-03-27 22:49:15] INFO: Loading config/resque.god I [2011-03-27 22:49:15] INFO: Syslog enabled. I [2011-03-27 22:49:15] INFO: Using pid file directory: /Volumes/Users/sven/.god/pids I [2011-03-27 22:49:15] INFO: Started on drbunix:///tmp/god.17165.sock I [2011-03-27 22:49:15] INFO: resque-0 move 'unmonitored' to 'init' I [2011-03-27 22:49:15] INFO: resque-0 moved 'unmonitored' to 'init' I [2011-03-27 22:49:15] INFO: resque-0 [trigger] process is not running (ProcessRunning) I [2011-03-27 22:49:15] INFO: resque-0 move 'init' to 'start' I [2011-03-27 22:49:15] INFO: resque-0 start: cd /Volumes/Users/sven/Development/projects/travis && rake resque:work I [2011-03-27 22:49:15] INFO: resque-0 moved 'init' to 'start' I [2011-03-27 22:49:15] INFO: resque-0 [trigger] process is running (ProcessRunning) I [2011-03-27 22:49:15] INFO: resque-0 move 'start' to 'up' I [2011-03-27 22:49:15] IN

Tags (comma-separated) Cancel