3 hours ago
Hello,
My MySQL service is permanently stuck in the "Creating containers..." phase during deployment and never starts.
Here are the details:
The CPU and Memory metrics are dead at 0.
The attached mysql-volume shows exactly 0 Bytes usage, even though it previously contained data.
The Railway "Database Connection" Data UI loads infinitely and cannot connect.
My Spring Boot backend is throwing a SocketTimeoutException because the DB is unreachable.
I have tried initiating a "Redeploy", but the new deployment also gets stuck in "Creating containers...".
This looks like an infrastructure issue where the node is failing to mount the persistent volume to the container. Could you please investigate the specific node and help unstuck my database volume?
3 Replies
3 hours ago
Your latest MySQL deployment has been waiting for more than ten minutes before its container started, so MySQL itself never got to run. Nothing in your settings, variables or code is involved at that point. The 0 bytes reading on the volume doesn't mean the data is gone, since usage isn't reported while no container is running. Redeploying doesn't delete, reset or roll back volume data.
To get it moving, cancel the stuck deployment. Then open the MySQL service, press CMD + K (CTRL + K on Windows and Linux) and run "Redeploy source image". Use that command instead of the "Redeploy" button on the existing deployment, because the button re-runs that same deployment rather than starting a fresh one from the image.
Status changed to Awaiting User Response Railway • about 3 hours ago
2 hours ago
Hi, I ran the 'Redeploy source image' command via the command palette exactly as instructed, but the new deployment is also permanently stuck at 'Creating containers...'. It seems the automated command isn't enough to bypass the issue, and the volume is still locked on a failing node.
My site can remain offline for a few hours if needed, but please escalate this to an engineer so they can manually unmount the volume and migrate the container to a healthy node. Thank you
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
same to me i woke up with the database connections down, I've tried to redeploy to restore a backup and nothing works , the mysql DB is down and nothing seems to work