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

**URL:** <https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936>\
**Category:** Self-hosting\
**Created:** [2015年九月30日 13:31 UTC](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936 "2015-09-30T13:31:09Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![clay](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/clay/32/102156_2.png) [@clay](https://meta.discourse.org/u/clay)\
**Post date:** [2015年十月2日 19:27 UTC](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936/19 "2015-10-02T19:27:15Z")

</div>

@codinghorror @neil @sam

I fixed it. Here’s what I had to do:

```plaintext
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, so the item remaining in the Redis queue was invalid and triggering an error in the logs. That’s total speculation.

---

_[View the full topic](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936)._