Currently getting this bug Running the latest discourse [image] and here is the /sidekiq [image]

Yup the job only runs once a day so it might take awhile before it clears :wink:

Are you running the recommended Docker-based install?

I’m facing the same problem. I didn’t have any problem before.

This problem is the result of a query not being sent properly from the VersionCheck job. It is failing because when it goes to check the version, the query isn’t included and thus a bad response comes back. There was also an issue with the port number, IIRC. There is a pull request pending on the fix. I did not make the fix, but I did manually apply the code changes to my install and it fixed the issue.

yes its the recommended docker based install

Yes let’s get this fixed asap @tgxworld

geez…I might just switch us to use Ruby’s built-in HTTP library. Just a simple get request and Excon gets in the way. Anyway, this has been fixed by @AlbertA in [image] JSON::ParserError on Jobs::VersionCheck Bug Hi! I just installed a forum on an ubuntu 16.04 linode instance using docker instructions. I also created an instance on a local VM so I could import my old smf2 based forum to it. Once imported I created a backup in the local VM through the discourse backup tab. I then applied this backup onto my linode instance following these instructions: Everything seems to work fine except the version check in the admin dashboard: “A check for updates has not been performed. Ensure sidekiq is running…

Why do we even need a third party library for this?

It has sort of been the convention in our repository to use either RestClient or Excon to make external requests. These third party clients provide a wrapper around the HTTP library which usually makes the code less verbose. While that is true for RestClient, I don’t think the same can be said for Excon. However, we don’t like RestClient because it depends on the mime-type gem that takes up quite a bit of memory. Once the latest mail gem is released, we’ll be able to drop the dependency on mime-type and switch to @sam’s mini-mime gem.

I am currently getting the same issue, even after rebuilding the container from SSH to latest.

Sidekiq not running

Product Support Self-hosting

xiasummer (xiasummer) June 18, 2017, 7:47pm 4

Also encounted such problem. Tried rebuild and restart, both not working.

Topic		Replies	Views
"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
Sidekiq is consuming too much memory, restarting Self-hosting	38	9552	October 13, 2020
Sidekiq stops after some time Self-hosting	7	1363	June 14, 2023
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	3272	May 11, 2020

Sidekiq not running

Related topics