a month ago
Edit: After doing a little more research, it seems like this was definitely related to the major Railway outage, as the timing lines up pretty perfectly
https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage
Hi there,
Weird issue I just ran into this week - a production MySQL database just randomly shut down out of nowhere. It's been running fine for a month, and this wasn't a case of the usage limits being hit or anything. Pretty low traffic in general.
The bizarre thing is that I have a nearly identical production MySQL database running for another customer that's roughly 8x larger, and that one has been running just fine for almost a full year now. No idea why this one shut down.
I was able to get it up and running by redeploying the container (restarting the container didn't work), so I'm mostly just looking to make the Railway team aware of this and see what I can do to avoid this scenario in the future.
Here's the output of the deploy logs when it randomly shut down (user changed to ***** for this posting):
2026-05-19T22:19:46.571147Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 9.4.0).
2026-05-19T22:19:48.574783Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 39666 user: '*****'.
2026-05-19T22:19:48.574975Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 39667 user: '*****'.
2026-05-19T22:19:48.575047Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 39668 user: '*****'.
2026-05-19T22:19:48.575112Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 39669 user: '*****'.
2026-05-19T22:19:48.575171Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 39670 user: '*****'.
2026-05-19T22:19:49.151935Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.4.0) MySQL Community Server - GPL.
2026-05-19T22:19:49.151952Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
You're right, the shutdown lines up with the May 19 GCP account outage. The logs confirm MySQL received a graceful shutdown signal from the platform (not a crash or OOM), which is consistent with the infrastructure disruption described in that postmortem. Your data on the attached volume was not affected, and the redeploy was the correct fix. If this happens again and the service doesn't auto-recover, you can trigger "Redeploy source image" from the command palette (Cmd+K / Ctrl+K) to re-pull a fresh copy of the MySQL image.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved mykal • about 1 month ago
mykal
You're right, the shutdown lines up with the May 19 GCP account outage. The logs confirm MySQL received a graceful shutdown signal from the platform (not a crash or OOM), which is consistent with the infrastructure disruption described in that postmortem. Your data on the attached volume was not affected, and the redeploy was the correct fix. If this happens again and the service doesn't auto-recover, you can trigger "Redeploy source image" from the command palette (Cmd+K / Ctrl+K) to re-pull a fresh copy of the MySQL image.
a month ago
Sounds good, thanks for the feedback! Much appreciated. I just wanted to confirm that there's nothing else I should've been doing. Have a great weekend!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved musser004 • about 1 month ago