# "Sidekiq is not running"

**URL:** <https://meta.discourse.org/t/sidekiq-is-not-running/39178>\
**Category:** Self-hosting\
**Created:** [Fevereiro 7, 2016, 1:48pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running/39178 "2016-02-07T13:48:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [Fevereiro 7, 2016, 2:33pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running/39178/2 "2016-02-07T14:33:23Z")

</div>

Do you see any interesting in [http://forum.delimiter.com.au/logs](http://forum.delimiter.com.au/logs)? What does [http://forum.delimiter.com.au/sidekiq](http://forum.delimiter.com.au/sidekiq) show you?

I’d guess that rebuilding the container fixes the issue. SSH into the server, and run

```plaintext
cd /var/discourse
sudo ./launcher rebuild app

```

(This will make your installation unavailable for a few minutes.)

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-is-not-running/39178)._