This started today out of the blue. [image] I’ve searched the forum and tried all this: Upgrading manually to the latest git and rebuilding the app Rebooting the machine as @codinghorror suggested Checked diskspace, over 20GB free Trying what @clay suggested - trying to flush the queue (and then restarted and EVEN rebooting the machine) and I got: [1] pry(main)> Sidekiq.redis { |r| puts r.flushall } Passing ‘flushall’ command to redis as is; administrative commands cannot be effectively namespaced and should be called on the redis connection directly; passthrough has been deprecated and will be removed in redis-namespace 2.0 (at (pry):1:in `block in pry’) OK => nil Taking my clues from here, nothing seems to work. Any ideas what’s going on and how to fix it? [image] "Ensure sidekiq is running." when it is definitely running Self-hosting @codinghorror @neil @sam I fixed it. Here’s what I had to do: cd /var/discourse ./launcher ssh app rails c Sidekiq.redis { |r| puts r.flushall } Then I had to exit the container and ./launcher restart app That cleared the Sidekiq Redis queue and everything started back up. If I had to guess, I upgraded Discourse when there was a backup job in the queue in Redis and somehow, upon restarting the app, the name of a class or something associated with Redis, Sidekiq, or backing up had changed, s…

First upgrade to the latest version (there are some new patches related to this I think that went in a few hours ago). Open yourwebsite/admin/upgrade and upgrade to the latest version (+101 is working for me now, so you’re good there) Then from the terminal cd /var/discourse sudo ./launcher enter app rails c Sidekiq.redis { |r| puts r.flushall } exit exit sudo ./launcher restart app Then reboot the machine. I did this loop 2 times and it solved the issue. I think someone also mentioned you can try a few things Leave it for 24 hours and the scheduler should kick off again and this error should go away Force the schedules to start, open yourwebsite/sidekiq, goto scheduler and trigger the schedule Jobs::VersionCheck

Here’s what finally worked: I ran this again Sidekiq.redis { |r| puts r.flushall } Then I restarted the app sudo ./launcher restart app Then I rebooted the machine (again) And now it started working. Oddly, my logs are completely empty.

I have the same issue. This ‘solution’ is not satisfying since: it does not tell why this happened. it does not make clear which steps are required, and what they do exactly. it requires a reboot!!! I would expect restart to fix it, and I certainly do not plan on rebooting the machine.

[image] hellekin: This ‘solution’ is not satisfying since I would agree, I really don’t know why it happened and what exactly fixed it. Just that repeating the steps over a few times and rebooting a few times fixed it, but like you said I’m not convinced that’s the long term solution.

Hello. So what actions should I take? [image]

I simply upgraded to the latest version (now running v1.9.0.beta2 +98), and didn’t have to reboot.

Ensure sidekiq is running?

Product Support Self-hosting

fefrei (Felix Freiberger) June 20, 2017, 12:33pm 7

Yeah, simply updating and waiting 24 hours (or manually triggering Jobs::VersionCheck in the web UI as you suggested) should suffice, no messing within Rails necessary

Topic		Replies	Views
Sidekiq heartbeat test failed, restarting Self-hosting	11	2339	January 12, 2020
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	3275	May 11, 2020
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	8267	October 2, 2015
After a clean install : Sidekiq error Bug	17	2743	December 7, 2015
Error: Ensure sidekiq is running Bug	2	620	October 30, 2021

Ensure sidekiq is running?

Related topics