Hello,
I had an error upgrading my "all in one" container to latest with MariaDB upgrade, I'm posting here in case anybody has the same kind of issue. I skipped a few versions, 10.6.18 => 10.11.13
Here was my error after restarting the upgraded container :
[ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.18. You must start up and shut down MariaDB 10.7 or earlier.
In the installation UI, error "database unreachable".
Turned out I had to "properly" kill MariaDB before updating. docker stop didn't work for me
- in container :
- get mysql PID : ps aux | grep -E "mysql"
- kill process : kill -KILL [PID]
- then stop container and upgrade
Note : I didn't try it but I guess if you are stuck you could try to renaming the ib_logfile0 ib_logfile0.old (=erase redo log) but I wouldn't advise it in production. You could loose latest data.
Hello,
I had an error upgrading my "all in one" container to latest with MariaDB upgrade, I'm posting here in case anybody has the same kind of issue. I skipped a few versions, 10.6.18 => 10.11.13
Here was my error after restarting the upgraded container :
[ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.18. You must start up and shut down MariaDB 10.7 or earlier.
In the installation UI, error "database unreachable".
Turned out I had to "properly" kill MariaDB before updating. docker stop didn't work for me
Note : I didn't try it but I guess if you are stuck you could try to renaming the ib_logfile0 ib_logfile0.old (=erase redo log) but I wouldn't advise it in production. You could loose latest data.