a year ago
2025-04-23T01:54:07.709954Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2025-04-23T01:54:08.065152Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.3.0) starting as process 1
2025-04-23T01:54:08.086279Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=1073741824. Please use innodb_redo_log_capacity instead.
2025-04-23T01:54:08.095270Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-04-23T01:54:09.685224Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90300 to 80300. Downgrade is only permitted between patch releases.
mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2025-04-23T01:54:09.719214Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-04-23T01:54:09.719541Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-04-23T01:54:09.719570Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-04-23T01:54:09.721858Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.3.0) MySQL Community Server - GPL.
2025-04-23T01:54:09.721872Z 0 [System] [MY-015016] [Server] MySQL Server - end.
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/225fd6ff-172b-431a-a891-e18592a257b8/vol_5qi3j65bk2ycv93t
Pinned Solution
13 days ago
Finally this worked for me:
Changed startup command from :-
sh -c 'rm -f /var/lib/mysql/mysql/#sql-1_4* && docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --sql-mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"'
to:
sh -c 'rm -f /var/lib/mysql/mysql/#sql-* && rm -f /var/lib/mysql/#innodb_temp/* ; docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --upgrade=MINIMAL --sql-mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"'
16 Replies
a year ago
resolved by `docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0`
a year ago
Solved you can close it I am sorry for this!
a year ago
Awesome, glad you solved it!
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved echohack • about 1 year ago
19 days ago
The problem came back again with the same issue. ☹
2026-05-04T00:04:38.790396Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-05-04T00:04:38.916004Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.0.1) starting as process 1
2026-05-04T00:04:38.923733Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-05-04T00:04:49.533213Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90700 to 90001. Downgrade is only permitted between patch releases.
mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2026-05-04T00:04:49.882491Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2026-05-04T00:04:49.882815Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2026-05-04T00:04:49.882846Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-05-04T00:04:49.884310Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.0.1) MySQL Community Server - GPL.
2026-05-04T00:04:49.884329Z 0 [System] [MY-015016] [Server] MySQL Server - end.
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
tried workbench to connect:
Your connection attempt failed for user 'root' to the MySQL server at caboose.proxy.rlwy.net:44901:
Lost connection to MySQL server at 'reading initial communication packet', system error: 0
19 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 19 days ago
snapied
tried workbench to connect: Your connection attempt failed for user 'root' to the MySQL server at [caboose.proxy.rlwy.net:44901](http://caboose.proxy.rlwy.net:44901): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
19 days ago
You shouldn't be using the proxy to connect to your MySQL service. There should be a MYSQL_URL variable you can use to connect over private networking.
Using public networking can incur egress charges, which can rack up pretty quick for databases.
19 days ago
I did that already, the problem is mysql docker image itself.
I don't know wheat happened all of the sudden.
I switched to 9.1.0, got this error.
2026-05-04T03:15:59.343027Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.1.0) MySQL Community Server - GPL.
2026-05-04T03:15:59.343046Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2026-05-04T03:15:59.226812Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90700 to 90100. Downgrade is only permitted between patch releases.
mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2026-05-04T03:15:59.339608Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2026-05-04T03:15:59.340003Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2026-05-04T03:15:59.340033Z 0 [ERROR] [MY-010119] [Server] Aborting
Currently, clueless what should i do?
19 days ago
In Railway, go to MySQL's settings, and change the source image to be mysql:9.7. Redeploy after saving.
0x5b62656e5d
In Railway, go to MySQL's settings, and change the source image to be `mysql:9.7`. Redeploy after saving.
19 days ago
On 9.7:
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2026-05-04T03:18:18.992307Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-05-04T03:18:19.115843Z 0 [Warning] [MY-015655] [Server] Server ignores the discovered container restrictions as --container_aware is OFF
2026-05-04T03:18:19.115897Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.7.0) starting as process 1
2026-05-04T03:18:19.115914Z 0 [System] [MY-015603] [Server] MySQL Server has access to 48 logical CPUs.
2026-05-04T03:18:19.116270Z 0 [System] [MY-015603] [Server] MySQL Server has access to 412550610944 bytes of physical memory.
2026-05-04T03:18:19.124884Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-05-04T03:18:35.091856Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-05-04T03:18:42.230090Z 4 [System] [MY-013381] [Server] Server upgrade from '90600' to '90700' started.
0x5b62656e5d
Seems like your MySQL is up and running now?
19 days ago
Started but, 2026-05-04T03:18:35.091856Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
Database has not started
18 days ago
Hello snapied,
your volume has data written by mysql 9.7.0 so any image below 9.7 will always crash with that downgrade error thats just how mysql works, the data files are locked to the version that last wrote to them you have two options either keep using 9.7 image and share the full logs after "upgrade started" so i can see why it didnt finish or if you dont care about the data just delete the volume from railway dashboard and redeploy fresh with whatever image you want
domehane
Hello **snapied,** your volume has data written by mysql 9.7.0 so any image below 9.7 will always crash with that downgrade error thats just how mysql works, the data files are locked to the version that last wrote to them you have two options either keep using 9.7 image and share the full logs after "upgrade started" so i can see why it didnt finish or if you dont care about the data just delete the volume from railway dashboard and redeploy fresh with whatever image you want
13 days ago
I can't delete it I have data from years.
the logs are :-
You reached the start of the range
May 9, 2026, 4:37 PM
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e624b0fe-5a24-4f82-b9d0-b4fb9d8676d2/vol_6az2cctfsn6uwxz6
Starting Container
2026-05-09 11:09:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.7.0-1.el9 started.
2026-05-09 11:09:17+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2026-05-09 11:09:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.7.0-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2026-05-09T11:09:18.300834Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-05-09T11:09:18.424386Z 0 [Warning] [MY-015655] [Server] Server ignores the discovered container restrictions as --container_aware is OFF
2026-05-09T11:09:18.424428Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.7.0) starting as process 1
2026-05-09T11:09:18.424450Z 0 [System] [MY-015603] [Server] MySQL Server has access to 48 logical CPUs.
2026-05-09T11:09:18.424862Z 0 [System] [MY-015603] [Server] MySQL Server has access to 412550610944 bytes of physical memory.
2026-05-09T11:09:18.434663Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-05-09T11:09:23.728412Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-05-09T11:09:26.082003Z 4 [System] [MY-013381] [Server] Server upgrade from '90600' to '90700' started.
2026-05-09T11:10:10.126979Z 0 [ERROR] [MY-013380] [Server] Failed to upgrade server.
2026-05-09T11:10:10.127015Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-05-09T11:10:11.487245Z 0 [System] [MY-015016] [Server] MySQL Server - end.
0x5b62656e5d
Try MySQL 9.6 instead of 9.7 instead then.
13 days ago
This gave:-
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/171bede3-1ef3-46aa-bb4f-7dfc2e2fdd50/vol_6az2cctfsn6uwxz6
Starting Container
2026-05-09 11:29:46+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.6.0-1.el9 started.
2026-05-09 11:29:47+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2026-05-09 11:29:47+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.6.0-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2026-05-09T11:29:48.077856Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-05-09T11:29:48.195665Z 0 [Warning] [MY-015641] [Server] Server ignores the discovered container restrictions as --container_aware is OFF
2026-05-09T11:29:48.195713Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.6.0) starting as process 1
2026-05-09T11:29:48.195733Z 0 [System] [MY-015590] [Server] MySQL Server has access to 48 logical CPUs.
2026-05-09T11:29:48.196083Z 0 [System] [MY-015590] [Server] MySQL Server has access to 412550610944 bytes of physical memory.
2026-05-09T11:29:48.205501Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-05-09T11:29:52.754106Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-05-09T11:29:52.754262Z 1 [ERROR] [MY-014061] [Server] Invalid MySQL server downgrade: Cannot downgrade from 90700 to 90600. Downgrade is only permitted between patch releases.
2026-05-09T11:29:52.754273Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2026-05-09T11:29:52.754463Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2026-05-09T11:29:52.754478Z 0 [ERROR] [MY-010119] [Server] Aborting
2026-05-09T11:29:53.070605Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.6.0) MySQL Community Server - GPL.
2026-05-09T11:29:53.070628Z 0 [System] [MY-015016] [Server] MySQL Server - end.
13 days ago
Finally this worked for me:
Changed startup command from :-
sh -c 'rm -f /var/lib/mysql/mysql/#sql-1_4* && docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --sql-mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"'
to:
sh -c 'rm -f /var/lib/mysql/mysql/#sql-* && rm -f /var/lib/mysql/#innodb_temp/* ; docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --upgrade=MINIMAL --sql-mode="STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"'
Status changed to Solved brody • 11 days ago