Same issue here with latest update, no changes other than just updating via a rebuild, admin dashboard says sidekiq is not running. I have postgres/redis in a container and the app in another, have restarted them all again as well. Queues have a couple hundred, but nothing is processing.
EDIT1: Clearing all queues did not fix or help anything, they are refilling and still not processing.
EDIT2: And rebuilt the forum with all the downtime that entails and still have this message:
And the queues are not processing in /sidekiq. This was all working without issue before the update to 2.4.0.beta9 from beta7.
EDIT3: Over 50gigs of free space. Manually running a backup (just shy of 300 megs) works successfully, and it says it pauses and unpauses sidekiq and no error reported in the log, but sidekiq still doesn’t seem to be running?
EDIT4: Only log of note in /logs is the Sidekiq heartbeat test failed, restarting that keeps repeating.
EDIT5: Redis seems to be up and working fine, at least it’s log file is busy saying it doesn’t have much to do… And for clarity:
[3] pry(main)> Sidekiq.paused?
=> false
EDIT6: I have cleared the queue’s a bit ago, back up to 10 queued but not processing tasks.
EDIT7: Found that bundle exec sidekiq is the usual way to start sidekiq in a normal project, so let’s try running it to see what it does:
root@vps198273-forum:/var/www/discourse# bundle exec sidekiq
2020-01-06T05:10:18.814Z pid=31242 tid=gn383wxbu INFO: Booting Sidekiq 6.0.4 with redis options {:host=>"forum-data", :port=>6379, :namespace=>"sidekiq", :id=>"Sidekiq-server-PID-31242", :url=>nil}
You are connecting to Redis v3.0.6, Sidekiq requires Redis v4.0.0 or greater
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/cli.rb:62:in `run'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/bin/sidekiq:12:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/bin/sidekiq:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.6.0/bin/sidekiq:23:in `<top (required)>'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli/exec.rb:63:in `load'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli/exec.rb:63:in `kernel_load'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli/exec.rb:28:in `run'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli.rb:476:in `exec'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli.rb:30:in `dispatch'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/cli.rb:24:in `start'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/exe/bundle:46:in `block in <top (required)>'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors'
/usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.1/exe/bundle:34:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
You are connecting to Redis v3.0.6, Sidekiq requires Redis v4.0.0 or greater
Well, this looks interesting? Let’s try rebuilding the data container and praying from the terror of touching the data, lol…
EDIT8: Well it seems to be running Redis 5.0.5 (why aren’t postgresql pubsub used for this instead?), which is definitely 4.0.0 or newer… and it’s done rebuilding, testing the forums, their data seems to still be there, and we have a spike!
Looks fixed! Maybe this post will come in useful for someone. I wish the forums gave me the error that sidekiq was giving about an out of date redis, but I’m guessing those logs are just going into the abyss somewhere as I didn’t see them anywhere. ^.^