4 months ago
Subject: Repeated Command timed out / Connection is closed after periodic health check (instance IDs: <ids>, timestamps: <times>)
Hi Railway support,
We observe repeated Command timed out immediately followed by Failed to create streams client: Connection is closed in our realtime worker logs. This happens around the same window as our periodic Redis health check. When this occurs, pooled connections tear down and the streams consumer disables, causing HTTP fallback.
Attached: full server logs (with timestamps), CLIENT LIST snapshot and Redis diagnostic outputs.
Please check for any TCP/egress limits, proxy-level timeouts for blocking XREADGROUP commands, or connection kill policies that might close pooled connections during repeated connect/disconnect sequences.
Thanks.
2 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 TCP Proxy for PostgreSQL not accepting connections - Connection timeout
🧵 Persistent SIGTERM Error 502 on Next.js Application Deployment
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
Hey, Railway has no limits on TCP proxies. Also, is there any reason why you're not using Private Networking? https://docs.railway.com/reference/private-networking.
If you can provide information about how many disconnect/connect sequences you're performing, along with logs or any other relevant context, it would greatly help us debug this issue.