# La conexión a Redis agotó el tiempo de espera

**URL:** <https://meta.discourse.org/t/redis-connection-timed-out/76348>\
**Category:** Self-hosting\
**Created:** [18 Diciembre, 2017 20:58 UTC](https://meta.discourse.org/t/redis-connection-timed-out/76348 "2017-12-18T20:58:44Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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:** [18 Diciembre, 2017 23:44 UTC](https://meta.discourse.org/t/redis-connection-timed-out/76348/14 "2017-12-18T23:44:23Z")

</div>

Well, I got the multisite instance to crash the database again during a rebuild when compiling css. `sar` showed a couple seconds of 30 swaps, but free still said only about 150M of the 2027M of swap available. ops/sec was less than 100 up until it died. I’m pretty stumped on this one. I keep thinking that it’s my imagination, but it always dies on a rebuild and most nights it crashes a couple times. It didn’t crash the one night I had all of the backups turned off.

Meanwhile, the big sidekiq backlog site keeps functioning.

---

_[View the full topic](https://meta.discourse.org/t/redis-connection-timed-out/76348)._