# 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:** 13

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

</div>

> [@pfaffman](#):
>
> once it dies hangs redis-cli won’t give me any stats. I’ll try to see what’s up with that next.

Hmm, yeah, I guess once Redis stops talking to the world, you’re going to have a hard time connecting to it to get stats… although if you run `redis-cli` while everything is hunky-dory, then stay connected, you should be able to keep running `info stats` (assuming Redis hasn’t _completely_ lost its tiny mind).

Another thing to check is the Redis logs; from memory, I think we’ve got Redis logging to Docker, so `./launcher logs app` is what you want there. If Redis is really playing up hard, that should tell you what’s what.

I’d also like to definitively rule out swapping as a contributing factor; can you collect the output of `free -m` from just before and just after the problem occurs, and run `sar -W 1` (on the host) before and after 🔥.

---

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