# Can't restore because sidekiq won't let go

**URL:** <https://meta.discourse.org/t/cant-restore-because-sidekiq-wont-let-go/253515>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [January 31, 2023, 3:32pm UTC](https://meta.discourse.org/t/cant-restore-because-sidekiq-wont-let-go/253515 "2023-01-31T15:32:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 31, 2023, 4:36pm UTC](https://meta.discourse.org/t/cant-restore-because-sidekiq-wont-let-go/253515/3 "2023-01-31T16:36:42Z")

</div>

That’s what I’d have thought, but even after I shut down the container running sidekiq postgres was still showing active connections. Similarly, I had done an `sv stop unicorn` on the ECS instance but postgres was still showing active connections.

I rebooted the RDS server, cranked up the container on the EC2 (the instances in ECS don’t have enough disk spare for a restore), `sv stop unicorn`, then drop, create, restore the database and now, I’m attempting a restore.

Thanks very much for your help. I do appreciate it!

---

_[View the full topic](https://meta.discourse.org/t/cant-restore-because-sidekiq-wont-let-go/253515)._