Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I found the solution to this after I looked at hirefire source. The issue in my case was that there was a locked job in the job queue. Because of this, delayed_job.working turned out to be 1 and not 0. Also, because of the locked job, delayed_job.jobs was also 1. And hence no worker was hired. I cleared all the jobs from the queue and then hirefire worked like a charm.
I think this check should be modified to check for number of jobs that are not locked or something of a similar nature.