Describe the bug ..... 9:M 07 Feb 2024 07:11:40.138 * Redis version found by RedisSearch : 7.2.4 - oss 9:M 07 Feb 2024 07:11:40.138 * RediSearch version 2.8.11 (Git=2.8-7368bb3) 9:M 07 Feb 2024 07:11:40.138 * Low level api version 1 initialized successfully 9:M 07 Feb 2024 07:11:40.138 * concurrent writes: OFF, gc: ON, prefix min length: 2, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results: 10000, search pool size: 20, index pool size: 8, ================= Then the log stop in here, no more log can be seen. And the status of container is up But all request for Redis will be : redis.exceptions.ConnectionError: Error while reading from {ip}:6379: (104, 'Connection reset by peer')

To reproduce GCP vm setting: Linux version 4.18.0-477.27.1.e18.x86_64 gcc version 8.5.0 20210514 Red had 8.5.0-18 run: docker pull redis/redis-stack-server docker run -itd --name redis -p 6379:6379 redis/redis-stack-server

Expected behavior

After docker run -itd --name redis -p 6379:6379 redis/redis-stack-server run, the final log will be like:

9:M 07 Feb 2024 07:11:40.145 * Module 'redisgears_2' loaded from /opt/redis-stack/lib/redisgears.so 9:M 07 Feb 2024 07:11:40.146 * Server initialized 9:M 07 Feb 2024 07:11:40.146 * Ready to accept connections tcp

Additional information

I use the same image run in another platform, and it works. So I don't it is the issue about GCP.

Comment From: madolson

Redis stack is a separate offering from redis, and it's maintained https://github.com/redis-stack/redis-stack. Redis stack is mostly just a distribution of Redis with some modules, so not sure what is going on. I would create the issue over there first though, please re-open back here if they determine it's something related to Redis.

Worth noting it's "Connection reset by peer" and not connection refused, so a port is up and listening.