# A check for updates has not been performed lately. Ensure sidekiq is running
**URL:** https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726
**Category:** Self-hosting
**Created:** [Setembro 9, 2017, 5:10pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726 "2017-09-09T17:10:14Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@kyle\_boyce](https://meta.discourse.org/u/kyle_boyce)
#### Post date: [Setembro 9, 2017, 5:10pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/1 "2017-09-09T17:10:14Z")
A check for updates has not been performed lately. Ensure sidekiq is running.
I tried this
> [@sam](#):
>
> Does this fix it?
>
> cd /var/discourse && git pull && ./launcher rebuild app
and it didn’t work any help would be appreciated!
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [Setembro 9, 2017, 7:12pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/2 "2017-09-09T19:12:15Z")
What do you mean it didn’t work? That command will upgrade your site.
It won’t repair a broken sidekiq/setup.
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [Setembro 10, 2017, 12:54pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/3 "2017-09-10T12:54:58Z")
How did you install Discourse? Is this a Docker-based [standard install](https://meta.discourse.org/t/142537?silent=true)?
---
### Author:  [@kyle\_boyce](https://meta.discourse.org/u/kyle_boyce)
#### Post date: [Setembro 10, 2017, 3:22pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/4 "2017-09-10T15:22:37Z")
Turns out all I had to do was wait 12 hours or so and it worked 😅
---
### Author:  [@kimardenmiller](https://meta.discourse.org/u/kimardenmiller)
#### Post date: [Fevereiro 25, 2019, 6:59pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/5 "2019-02-25T18:59:57Z")
> [@fefrei](#):
>
> How did you install Discourse? Is this a Docker-based [standard install](https://meta.discourse.org/t/142537?silent=true)?
I have a standard / local / dev install. What’s the procedure to update?
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [Fevereiro 25, 2019, 9:15pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/6 "2019-02-25T21:15:07Z")
If you have a dev install, pull the repository, run migrations and restart the server. These steps are very similar to the [initial installation](https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-ubuntu-for-development/14727).
Note that a dev install should not be used in production. If the instance is publicly accessible, the proper upgrade procedure is to take a backup, install using [these](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) instructions, and restore the backup 🙂
---
### Author:  [@kimardenmiller](https://meta.discourse.org/u/kimardenmiller)
#### Post date: [Fevereiro 25, 2019, 9:46pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/7 "2019-02-25T21:46:35Z")
Ah, yes, of course. Did not even think of that since we were targeting a certain release we are about to install on our production system vs. whatever happens to be the Github master right now.
But, it looks as if the currently recommended update, _2.3.0.beta2_ is what you get with the current master, correct?
> **[Commits · discourse/discourse](https://github.com/discourse/discourse/commits/master)**
>
> A platform for community discussion. Free, open, simple. - Commits · discourse/discourse
> **[Releases · discourse/discourse](https://github.com/discourse/discourse/releases)**
>
> A platform for community discussion. Free, open, simple. - discourse/discourse
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [Fevereiro 25, 2019, 10:31pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/8 "2019-02-25T22:31:39Z")
You should never install `master` directly. Always use `tests-passed`, the default; `beta`, for a more regular release cadence (every few weeks) with no changes in-between; or `stable`, if you absolutely require minimal changes between rarer, larger releases and are willing to live with only security and major bugfixes in between.
---
### Author:  [@kimardenmiller](https://meta.discourse.org/u/kimardenmiller)
#### Post date: [Fevereiro 26, 2019, 7:02pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/9 "2019-02-26T19:02:09Z")
Thanks for being so helpful, @fefrei! So `beta` is about 10 commits past [v2.3.0.beta2](https://github.com/discourse/discourse/releases/tag/v2.3.0.beta2), which ends on this commit?
```
0e8dbbd8e48363e4a771de1c65dc5c8b4cdf282b
```
You recommend pulling `beta` to a local `beta` branch, resetting the branch to the above commit, and … working with that, or merging that into my `master`?
I’m trying to get a sandbox of [v2.3.0.beta2](https://github.com/discourse/discourse/releases/tag/v2.3.0.beta2) to test on before installing that version on our live system. Eager to learn the best practice here 😃 .
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [Fevereiro 26, 2019, 7:10pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/10 "2019-02-26T19:10:06Z")
I’d just do a normal Docker-based install locally. The closer you are to your production install, the less surprises when moving to production 😀
---
### Author:  [@kimardenmiller](https://meta.discourse.org/u/kimardenmiller)
#### Post date: [Fevereiro 26, 2019, 7:36pm UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/11 "2019-02-26T19:36:37Z")
Right, I wondered about that in hindsight, but I’m also developing a couple plugins … will I find it annoying being in a Docker Container?
---
### Author:  [@randallcoding](https://meta.discourse.org/u/randallcoding)
#### Post date: [Novembro 1, 2019, 5:36am UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/12 "2019-11-01T05:36:53Z")
Estou enfrentando esse problema agora como o autor original (OP). Instalei a branch **tests-passed**.
Iniciei o sidekiq com `bundle exec sidekiq` e, em seguida, reiniciei o servidor Rails enquanto o sidekiq estava em execução, mas isso não resolveu o problema.
Acho que isso está relacionado ao erro que estou recebendo com um plugin, onde, ao iniciar o servidor, recebo a mensagem:
> constante Jobs::jobs::Scheduled não inicializada
> Você quis dizer? Scheduler (NameError)
>
> \*\* PLUGIN INCOMPATÍVEL \*\*
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [Julho 18, 2023, 3:50am UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/13 "2023-07-18T03:50:16Z")
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [Julho 18, 2023, 8:02am UTC](https://meta.discourse.org/t/a-check-for-updates-has-not-been-performed-lately-ensure-sidekiq-is-running/69726/14 "2023-07-18T08:02:48Z")