# "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:** 12

<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年十月1日 18:03 UTC](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936/12 "2015-10-01T18:03:09Z")

</div>

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:

![](https://global.discourse-cdn.com/meta/optimized/3X/9/d/9d57a6ca809d2d1c72d9ddc97f3355f957bb5b9f_2_690x44.png)

For the second, I see:

```plaintext
/var/www/discourse/lib/scheduler/schedule_info.rb:79:in `schedule!'
/var/www/discourse/lib/scheduler/manager.rb:221:in `schedule_next_job'
/var/www/discourse/lib/scheduler/manager.rb:199:in `block in tick'
/var/www/discourse/lib/scheduler/manager.rb:246:in `block in lock'
/var/www/discourse/lib/distributed_mutex.rb:21:in `synchronize'
/var/www/discourse/lib/scheduler/manager.rb:245:in `lock'
/var/www/discourse/lib/scheduler/manager.rb:198:in `tick'
/var/www/discourse/config/initializers/sidekiq.rb:35:in `block (2 levels) in <top (required)>'

```

For the heartbeat warning, I see:

```plaintext
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.0.3.pre/lib/logster/logger.rb:74:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.0.3.pre/lib/logster/logger.rb:35:in `add'
/usr/local/lib/ruby/2.0.0/logger.rb:445:in `warn'
config/unicorn.conf.rb:129:in `check_sidekiq_heartbeat'
config/unicorn.conf.rb:146:in `master_sleep'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:295:in `join'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

```

Sidekiq shows this on the Statistic tab. The orange was the `Jobs::RunHeartbeat` that no longer seems to be running.

 ![](https://global.discourse-cdn.com/meta/original/3X/b/e/be1c7d0620420d65cd6b3f065fdf39c320fd9b7c.png)

Everything seems to be working normally except for failed backups.

Related to [this](https://meta.discourse.org/t/disk-space-and-backup-failure-notifications/24162)?

---

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