# הגרסה החדשה ביותר של Discourse שוברת את ה-rebuild, ה-Redis Port כבר בשימוש

**URL:** <https://meta.discourse.org/t/newest-discourse-version-breaks-rebuild-redis-port-already-in-use/172008>\
**Category:** Self-hosting\
**Created:** [2 בדצמבר,‏ 2020,‏ 5:08pm UTC](https://meta.discourse.org/t/newest-discourse-version-breaks-rebuild-redis-port-already-in-use/172008 "2020-12-02T17:08:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Lagger\_Gandalf](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lagger_gandalf/32/128962_2.png) [@Lagger\_Gandalf](https://meta.discourse.org/u/Lagger_Gandalf)\
**Post date:** [2 בדצמבר,‏ 2020,‏ 5:24pm UTC](https://meta.discourse.org/t/newest-discourse-version-breaks-rebuild-redis-port-already-in-use/172008/2 "2020-12-02T17:24:59Z")

</div>

This problem really turned into a Paradox.  
Discourse starts the redis-server pid in Docker and then crashes, because it started the process already:

 ![image](https://global.discourse-cdn.com/meta/original/3X/c/2/c2909b91363b7ad9fcb0fc2572894b9fe86ef14e.png)

I have a main Redis Installation on the Host running, but that one is on Port 6800, so it shouldn’t interferre.

It clearly looks, like the Check fails on itself, because Redis Starts itself succesfull and then reports failed, adress in use:

 ![image](https://global.discourse-cdn.com/meta/original/3X/4/c/4cfb8b951d9b3268f4e970333320e8e14ce3b511.png)

---

_[View the full topic](https://meta.discourse.org/t/newest-discourse-version-breaks-rebuild-redis-port-already-in-use/172008)._
