-
Notifications
You must be signed in to change notification settings - Fork 21
sidekiq not processing queues in 3.16 #246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks, I will have a look. |
There may be a fix in the works, probably related to file permissions. I'll
|
File permissions would indeed be a good explanation, as I have exactly the same code running in multiple lagotto instances. |
seeing the same behaviour on an AWS instance now. the user being used to run sidekiq has full rwx on the /var/www/lagotto and it's subdirs where sidekiq is storing logs and pids, so not being limited by permissions there. HOWEVER I am seeing activity in the sidekiq log (attached). Once an hour at 10mins past the hour it appears to queue ~8 jobs and finish them. This is the hourly cron. The number of processed jobs goes up, but so does the number enqueued - this means it will never reach the end of the 'critical' queue. The daily cron job is giving an error that appears to be related to the database:
All migrations have been run. Does the daily cron event process the jobs in the 'high' queue and the hourly event those in the 'critical' queue? |
@lsh-0 I have identified two issues. The first is an issue with passing ENV variables to the Sidekiq configuration file The other issue is the path to the Sidekiq config, log and pid files. I have rewritten the logic to be more robust for different server configurations. Let me know if you still have problems after deploying the latest code from the |
I'll update now and let you know On Tue, Feb 17, 2015 at 10:26 AM, Martin Fenner notifications@github.com
Luke Skibinski eLife Sciences Publications, Ltd is a limited liability non-profit |
after shifting to The daily cron is still giving me the same error as above though:
I can raise this as a separate bug if you'd like. |
Ok, some progress. To run sidekiq manually (-d to run as daemon), use this command from your root folder: RAILS_ENV=production bundle exec sidekiq -C ./config/sidekiq.yml -d And make sure you have |
I killed off the existing sidekiq process and then ran that command, which appears to work. I killed the process off again and did what my script is running ( |
Closing the issue. Please reopen if there are still issues. |
I'm trying to import our articles from crossref. I can see the crossref import jobs accumulating in sidekiq, but nothing happens - Sidekiq isn't processing anything.
Sidekiq is running with no errors or warning or much of anything in the log file.
I remove all other jobs in all other queues, stop and start sidekiq but nothing.
Import jobs:

Queues:

The text was updated successfully, but these errors were encountered: