10 months ago
We have the same project services, both in test and in prod. In test, we get the error Redis health check failed. In prod, with the same configuration, same environment variable names, etc, it is working correctly. In test it used to work well up until yesterday, and now it is failing. This is the full error.
We are using this value on both environments for the redis host ${{Redis.RAILWAY_PRIVATE_DOMAIN}}
{"message":"Redis health check failed","attributes":{"APP_NAME":"beel-api","application":"beel-api","level":"warn","level_value":30000,"logger":"org.springframework.boot.actuate.data.redis.RedisReactiveHealthIndicator","stack_trace":"j.n.c.ClosedChannelException: null\n\tat i.n.c.e.AbstractEpollChannel.doClose(AbstractEpollChannel.java:159)\n\tat i.n.c.e.AbstractEpollStreamChannel.doClose(AbstractEpollStreamChannel.java:673)\n\tat i.n.c.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:752)\n\tat i.n.c.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:729)\n\tat i.n.c.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:619)\n\tat i.n.c.DefaultChannelPipeline$HeadContext.close(DefaultChannelPipeline.java:1299)\n\tat i.n.c.AbstractChannelHandlerContext.invokeClose(AbstractChannelHandlerContext.java:755)\n\tat i.n.c.AbstractChannelHandlerContext.access$1200(AbstractChannelHandlerContext.java:61)\n\tat i.n.c.AbstractChannelHandlerContext$11.run(AbstractChannelHandlerContext.java:738)\n\tat i.n.u.c.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)\n\tat i.n.u.c.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)\n\tat i.n.u.c.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)\n\tat i.n.c.epoll.EpollEventLoop.run(EpollEventLoop.java:405)\n\tat i.n.u.c.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)\n\tat i.n.u.i.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat i.n.u.c.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.lang.Thread.run(Thread.java:1583)\nWrapped by: i.l.c.RedisConnectionException: Unable to connect to redis.railway.internal/<unresolved>:6379\n\tat i.l.c.2 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
I'm not sure why it would stop working all of a sudden.
Have you tried specifying the port to see if that helps?
https://docs.railway.com/guides/private-networking#use-internal-hostname-and-port