Mysql Down
oligirling
HOBBYOP
25 days ago
Keep getting this
2026-02-11T14:23:08.837528Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2026-02-11T14:23:09.837700Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2026-02-11T14:23:10.837874Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2026-02-11T14:23:11.838039Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2026-02-11T14:23:12.838378Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
Stopping Container
2026-02-11T14:25:02.357477Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.4.8).
2026-02-11T14:25:02.807933Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.8) MySQL Community Server - GPL.
2026-02-11T14:25:02.807957Z 0 [System] [MY-015016] [Server] MySQL Server - end.
Stopping ContainerRestarting it doesnt fix it
1 Replies
25 days ago
Hey there!
It looks like this was a part of a recent incident we have. I just checked and it should be good to go now. Can you give it a look and let me know what you're seeing?
Post mortem is here in case you're interested in reading it.
https://blog.railway.com/p/incident-report-february-11-2026
Status changed to Awaiting User Response Railway • 25 days ago
Railway
BOT
17 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 • 17 days ago