This was related to a Ruby concurrency issue fixed in a patch for version 2.3 Your logs suggests your app is running 2.0.0. Updating the language version to at least the stable version of 2.3 would fix that problem. This can be easily done by changing your Gemfile Ruby declaration: ruby ‘2.3.8’
if you want to list all currently running jobs from console, try this workers = Sidekiq::Workers.new workers.each do |_process_id, _thread_id, work| p work end a work is a hash. to list all queue data. queues = Sidekiq::Queue.all queues.each do |queue| queue.each do |job| p job.klass, job.args, job.jid end end for a specific queue change this … Read more
Check if your redis server is running, start redis by using the following command in the terminal: redis-server
Short answer is they are the same thing. ActiveJob calls it a Job whereas Sidekiq calls it a Worker. I’ve decided to keep the terminology different so that people can distinguish the two. You can use either one. Note that ActiveJob does not provide access to the full set of Sidekiq options so if you … Read more
No you do not need any config with Heroku for Sidekiq, just add the RedisToGo plugin and you’re on. Do not forget to attribute at least 1 worker to your app in your Heroku config. Here is my default Procfile: web: bundle exec thin start -p $PORT worker: bundle exec sidekiq -c 5 -v
We also faced a similar issue. Looks like someone scanned AWS, connected to all public redis servers, and possibly ran “CONFIG SET REQUIREPASS ””, thus locking down the running instance of redis. Once you restart redis, the config is restored to normal. Best thing would be to use AWS security group policy and block port … Read more
bundle exec sidekiq -d -L log/sidekiq.log -C config/sidekiq.yml -e production -d, Daemonize process -L, path to writable logfile -C, path to YAML config file -e, Application environment
Please check if sidekiq process is actually running: ps aux | grep sidekiq If it is not, try to run sidekiq in foreground first and check the output. bundle exec sidekiq -e production
According to this Sidekiq documentation page to delete a job with a single id you need to iterate the queue and call .delete on it. queue = Sidekiq::Queue.new(“mailer”) queue.each do |job| job.klass # => ‘MyWorker’ job.args # => [1, 2, 3] job.delete if job.jid == ‘abcdef1234567890’ end There is also a plugin called sidekiq-status that … Read more
To reset statistics: Sidekiq::Stats.new.reset ref: Add reset stats to Web UI summary box and method to API Also, you can now clear specific stats: single stat by Sidekiq::Stats.new.reset(‘failed’) or multiple stats by Sidekiq::Stats.new.reset(‘failed’, ‘processed’) (Thanks https://stackoverflow.com/users/2475008/tmr08c for update)