# Locks up while running Sidekiq after migration

**URL:** https://meta.discourse.org/t/locks-up-while-running-sidekiq-after-migration/76640
**Category:** Self-hosting
**Created:** [December 22, 2017, 7:36pm UTC](https://meta.discourse.org/t/locks-up-while-running-sidekiq-after-migration/76640 "2017-12-22T19:36:53Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [December 23, 2017, 12:34pm UTC](https://meta.discourse.org/t/locks-up-while-running-sidekiq-after-migration/76640/4 "2017-12-23T12:34:18Z")

</div>

OOOH! OOOH! I think I know this one!

Check `/var/docker/shared/standalone/log/rails/*.log` for mentions of `Redis::TimeoutError`. If they’re in there, you’ve probably hit [this doozy of a Docker bug](https://meta.discourse.org/t/discourse-web-interface-becomes-unresponsive-a-few-minutes-after-starting/76643/11). The workaround is to restart Docker (`service docker restart`) and the problem seems to go away.

---

_[View the full topic](https://meta.discourse.org/t/locks-up-while-running-sidekiq-after-migration/76640)._