a month ago
My MySQL service won't start after your build-queue incident. Container shows 'Deployment Online' but the database process never starts — logs stop at 'Mounting volume', and your Data tab says 'unable to connect, application not running or in an unexpected state'. Restart didn't fix it and I have no backups. The volume vol_0uil5duf5qddqfvc still has my production data. Please help recover the database without losing the volume
1 Replies
a month ago
We can confirm your MySQL service's logs show that after a container restart on May 20 at 04:31 UTC, the process stalled immediately after mounting your volume - MySQL never began its initialization sequence. Prior to the disruption, MySQL 9.4.0 was running normally (last healthy logs from May 11). Your volume is still attached and being mounted, so your data is intact. This is a known issue tied to an ongoing platform disruption that our team is actively resolving. Please do not delete or recreate the service, as that would detach the volume. Once the underlying issue is resolved, triggering a fresh redeploy from your service's deployments page should bring MySQL back online with your existing data. Going forward, we strongly recommend enabling automated backups on your volume for added protection.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago