In the past few weeks, The Admin page has shown: [afbeelding] Visiting the …/sidekiq page shows that it is definitely running and processing jobs. I just tried rebuilding the app, but it remains in a frowny-face status. Any idea what’s going on here or why the admin page isn’t seeing Sidekiq?

Is this a dev instance or using docker? As I’ve come across that in my dev instance and it remains to always show that message, but on my prod docker instance it indicates it correctly as running.

It’s Docker. The last time this happened, I rebuilt Discourse and it started to find Sidekiq again. However, this time it won’t.

Oops. Wrong link. I meant this problem: [afbeelding] Docker problem after machine restart Support I had to reboot the machine I have Discourse running on to replace a bad graphics card. However, Discourse won’t restart. When I try ./launcher restart app f…

Seems unlikely unless you think it is running an old version of Discourse again. As sidekiq I think is stored within the docker image, so it should be running within the same container that is running Discourse. However, we’re reaching my level of expertise on this…

Hmm… I’m not sure why you’re seeing that. Can you open the rails console and get the output of DiscourseUpdates.check_version.as_json for me? root@dfp-neil:~$ cd /var/discourse/ root@dfp-neil:/var/discourse$ ./launcher enter app root@dfp-neil-app:/$ rails c [1] pry(main)> DiscourseUpdates.check_ver…

[afbeelding] neil: DiscourseUpdates.check_version.as_json Here’s what it shows: root@moxie-app:/# rails c [1] pry(main)> DiscourseUpdates.check_version.as_json => {"latest_version"=>"1.5.0.beta1", "critical_updates"=>false, "installed_version"=>"1.5.0.beta1", "installed_sha"=>"0f7aaf5ab19…

¯\_(ツ)_/¯ Ummm… What does the timestamp at the bottom of your dashboard say? Dashboard last updated: September 30, 2015 11:33 AM

Dashboard last updated: September 30, 2015 11:19 AM

Could it be that a failed backup is killing the Sidekiq heartbeat test? I don’t even really know what the Sidekiq heartbeat test is. Anyhow, I’m seeing this now: [afbeelding] For the second, I see: /var/www/discourse/lib/scheduler/schedule_info.rb:79:in `schedule!' /var/www/discourse/lib/schedule…

"Ensure sidekiq is running." when it is definitely running

Support Self-hosting

clay (Clay Heaton) 30 september 2015 om 14:02 5

Oops. Wrong link. I meant this problem:

Topic		Antwoorden	Weergaven
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	2988	11 mei 2020
"Sidekiq is not running" Self-hosting	6	3097	7 februari 2016
Sidekiq heartbeat test failed, restarting Self-hosting	11	2192	12 januari 2020
Sidekiq not launching Jobs Support	1	1768	25 april 2016
Sidekiq not running Self-hosting	21	5456	19 juni 2017

"Ensure sidekiq is running." when it is definitely running

Gerelateerde topics