`Try to set innodb_force_recovery to 1 and start mariadb. At the bottom of the link it provides, it shows this section which you should follow to a tee I had to use 2 for it to properly work as 1 didn't allow MySQL to start, do NOT use anything higher unless absolutely necessary, and also double check you make a proper backup before deleting everything. Please refer to for information about forcing recovery.įollowing that exact link it gave you, edit my.cnf with the option it gives you below. 22:01:33 0 InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. I was able to read /var/log/mysql/error.log and it has the same error: Set the environment variable for debugging the docker, then check your mariadb error logs, if it's the same issue as I'm getting, I can walk you through it, just involves setting an Innodb variable to enter recovery mode, backing up the database, deleting innodb log files, then importing the database back into mariadb, and then everything works fine. I might just start over from scratch, but it's kind of a bummer because it was working fine for a while. I'm not sure what steps to take, since I can't connect to mysql in the container. I tried disabling apparmor (based on some old posts), but it didn't work. * Starting MariaDB database server mysqld. Not sure if it's related, but it updated recently and now I'm getting:
0 kommentar(er)
