a month ago
Hello Railway team,
My MySQL service is failing because the volume cannot be mounted during container creation.
Railway diagnostics says this is an infrastructure-level issue. The platform failed to attach the volume after 10 retry attempts over approximately 10 minutes.
Deployment ID:
afa1dfd6-c746-4b33-930a-8561a510b7f7
The same image, configuration, and volume were working in a previous deployment around 20:29 UTC. There were no configuration changes, and other services in the environment are running normally.
Could you please investigate the volume scheduling / mounting issue and help recover access to the MySQL volume?
Thank you.
2 Replies
a month ago
Many others are reporting the same issue here. No response from Railway team yet, though https://station.railway.com/questions/unable-to-redeploy-database-786b9064
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Apologies for the disruption here. We've redeployed your service and it's now online and healthy. The failure was caused by an underlying hardware issue on the host your service was deployed on, not anything in your configuration. To be more resilient against host-level issues like this going forward, we'd recommend looking into a high availability database setup.
Please let me know if there anything else we can help with!
Status changed to Awaiting User Response Railway • 26 days ago
19 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 19 days ago