23 days ago
hi,
without any apparent reason, and without anything new from my side, the n8n workflow crashed in prod during the night.
Here are the last logs of the worker:
Worker finished execution 389 (job 971)
[runnner:js] Received SIGTERM signal, shutting down...
[runnner:js] Task runner stopped
[Redis client] read ECONNRESET
Queue errored
read ECONNRESET
[Redis client] read ECONNRESET
Lost Redis connection. Trying to reconnect in 1s... (0s/10s)
Lost Redis connection. Trying to reconnect in 1s... (2.7s/10s)
Lost Redis connection. Trying to reconnect in 1s... (3.7s/10s)
Lost Redis connection. Trying to reconnect in 1s... (6.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (7.5s/10s)
Lost Redis connection. Trying to reconnect in 1s... (8.5s/10s)
Unable to connect to Redis after trying to connect for 10s
Exiting process due to Redis connection error
And Redis database: "The database container is starting up or transitioning. Please wait a moment and try again."
How is it possible?
How could I fix this so it doesn't happen again?
5 Replies
23 days ago
I have fixed this, this was due to our outage here https://blog.railway.com/p/incident-report-february-11-2026 - I restarted Redis and restored your N8N.
Status changed to Awaiting User Response Railway • 23 days ago
23 days ago
Thank you.
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Solved marcados • 23 days ago
23 days ago
Update: fail.
Even if now every worker seem "fine" I cant connect to the app: "Application failed to respond"
Request ID:
Z5jTSP6USPG1WIeCacI7Nw
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Awaiting User Response Railway • 23 days ago
23 days ago
Seems good now. Very concerning. Thank you.
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Solved marcados • 23 days ago