# "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:** [9월 30, 2015, 1: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:** 18

<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:** [10월 2, 2015, 6:59오후 UTC](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936/18 "2015-10-02T18:59:50Z")

</div>

> [@codinghorror](#):
>
> I’ve seen failure of internal DNS to work (internally we can’t resolve, say [google.com](http://google.com)) cause all kinds of bizarre problems in the past. Have you checked that?

Yeah, I checked that. I can ping from inside the container to any address.

The logs are full of errors about the backup scheduler failing - that seems to be choking the `Jobs::RunHeartbeat` task, causing all of the recurring tasks to fail.

 ![](https://global.discourse-cdn.com/meta/original/3X/4/a/4aaba526bdb39fa324b1438934da89e3cbb7b7eb.png)

 ![](https://global.discourse-cdn.com/meta/original/3X/6/6/666635ec90fffec1a002e9499eeb3be8aed0a166.png)

I just turned off backups in the settings and rebuilt the app, but the same problem is happening. I also tried the trick the @sam [mentioned here](https://meta.discourse.org/t/number-of-scheduled-jobs-is-near-2-000/15362/8) but it doesn’t seem to have helped.

---

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