4 months ago
2026-02-11T14:30:01.045406Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 9.3.0).
2026-02-11T14:30:07.188495Z 0 [Warning] [MY-010909] [Server] /usr/sbin/mysqld: Forcing close of thread 36455 user: 'root'.
2026-02-11T14:30:08.829585Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.3.0) MySQL Community Server - GPL.
2026-02-11T14:30:08.829612Z 0 [System] [MY-015016] [Server] MySQL Server - end.It happened at 14h35, 14h40 and 14h45 too, and in between I upgraded Mysql to 9.6.0 hoping there was any security patches.
14 Replies
@Brody @Medim Please help, this is urgent!
Anything you enabled today that started killing processes?
I had to restart the Db already 5 times, it's being killed every 5 mins
4 months ago
Don't ping team members #🛂｜readme 5).
4 months ago
Have you tried redeploying instead of restarting? I've forwared these issues to the team.
4 months ago
Team is aware and looking into it
As I said, along the way mysql was upgraded to 9.6.6, which triggered a deployment. That didn't solve the issue, which already happened for the 6th time
4 months ago
Version bump isn't correlated with the ongoing incident
4 months ago
Hey, can you share your service URL? The one that appears in the URL bar (the one that starts with railway.com) when you have the service in focus.
GPT noticed this!
2️⃣ Check if Railway is auto-restarting due to memory
Your log says:
MySQL Server has access to 270467727360 bytes of physical memory.
That’s 270GB. Obviously fake inside a container.
But on staging the same is happening:
4 months ago
Don't ping team members #🛂｜readme 5). -> Instead of giving us directives how about you do your job and don't affect my production environment?
4 months ago
Same here, and me not only MySQL but also Redis. This is quite urgent, we mean it.
4 months ago
An incident has been called: https://status.railway.com/cmli5y9xt056zsdts5ngslbmp.
Status changed to Solved medim • 4 months ago