Open vivianxu08 opened 9 years ago
Try turning on the VERBOSE
mode with VERBOSE=true
and see if any additional output. Not having a schedule should not terminate the process, it should log that (see https://github.com/resque/resque-scheduler/blob/v4.0.0/lib/resque/scheduler.rb#L88).
I'm setting up resque scheduler, only for a delayed job, on AWS ec2 instance. So I wrote a script to run at start time during deploy,
Everything works fine if I run rake resque:scheduler manually,
However, after sometime the resque-scheduler process will just die, specifically. the first a few jobs after the new worker is deployed will be able to be processed, but the sub sequential jobs are not, as the resque-scheduler dies itself.
for example,
After a while if there is no incoming jobs, the process 111668 will just die.
Notice, my Resque.schedule is empty, as I have nothing scheduled to run, but only delayed job.
Why is that? Is there anyway to help me debug?