MySQL Database Down
chaudharysamirzafar
HOBBYOP

2 years ago

I accidentally stopped a deployment, so had to restart.

Now everytime i try to deploy my Database, I get the following

2024-08-28 18:25:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.

2024-08-28 18:25:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'

2024-08-28 18:25:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.

'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'

2024-08-28T18:25:01.123158Z 0 [System] [MY-015015] [Server] MySQL Server - start.

2024-08-28T18:25:01.370016Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 7

2024-08-28T18:25:01.377756Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

2024-08-28T18:25:01.527826Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90000 to 80402. Downgrade is only permitted between patch releases.

2024-08-28T18:25:01.527867Z 1 [ERROR] [MY-012967] [InnoDB] Cannot open DD tablespace.

2024-08-28T18:25:01.527880Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.

2024-08-28T18:25:01.534238Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine

2024-08-28T18:25:01.534536Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.

2024-08-28T18:25:01.534571Z 0 [ERROR] [MY-010119] [Server] Aborting

2024-08-28T18:25:01.536504Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2)  MySQL Community Server - GPL.

2024-08-28T18:25:01.536524Z 0 [System] [MY-015016] [Server] MySQL Server - end.

20 Replies

chaudharysamirzafar
HOBBYOP

2 years ago

m/A


chaudharysamirzafar
HOBBYOP

2 years ago

N/A


2 years ago

you're trying to downgrade MySQL from v9 to v8 which you can't do


chaudharysamirzafar
HOBBYOP

2 years ago

Right guessing the base image needs to be mysql:9 instead of 8 then?


chaudharysamirzafar
HOBBYOP

2 years ago

What's concerning is I didn't change that myself


2 years ago

exactly!


2 years ago

that's strange 🤔


chaudharysamirzafar
HOBBYOP

2 years ago

Yes I did that and it fixed it, thank you. You saviour.


chaudharysamirzafar
HOBBYOP

2 years ago

Yes, I don't know do deployments auto trigger if the same service from a prev env is deployed successfuly?


chaudharysamirzafar
HOBBYOP

2 years ago

Sorry, this is the project-id. 608a66b4-b749-45dc-b226-05c5a996dae8


2 years ago

(this isn't the first time I've seen this happen, maybe it's reproducible and can be brought up to the team)


2 years ago

I already saw two other ´ppl who restarted their MySql DB and got this error


2 years ago

I've heard something about that from previous reports but not 100% sure about that


chaudharysamirzafar
HOBBYOP

2 years ago

This might've been the root cause


chaudharysamirzafar
HOBBYOP

2 years ago

I suspect it's that


2 years ago

Railway started pinning databases to specific versions recently, I suspect that might have something to do with it


I've had my database stopped, and now trying to restart it I'm getting the same error, didn't update or anything lol


chaudharysamirzafar
HOBBYOP

2 years ago

This was the fix


chaudharysamirzafar
HOBBYOP

2 years ago

And yes very annoying 😄 especially as it’s just a simple restart


Oh I see now, hahaha will try here, thanks! 🙂


Loading...