It's me again!
Otto,
I found out that it is an Akonadi problem: Akonadi uses Mariadb as default
database, but does not provide mysqlcheck through dependencies.
Now I could repair the table structure with that knowledge, see the attached
file.
Would you please add the Akonadi maintainer to this
Otto,
I don't have the crashed database available. What I say is, that I have 3
working Akonadi databases, one in a fresh Bullseye install.
In any case the call of mysql_upgrade fails.
bequimao@bullseye-kde-vm:~$ mysql_upgrade --defaults-file=/home/
bequimao/.local/share/akonadi/mysql.conf
The user in the forum has already recovered his mails and data, so he won't
risk the test.
My point is, that in 2 of my 3 debian installations there are errors in the
MariaDB system tables (see mysql.err). Only the fresh Bullseye installation is
without errors. Akonadi/Contact/KMail works in
Control: tags -1 moreinfo
Hello!
This is not a bug in the Debian packaging and not really an upstream bug either.
The error message seems pretty clear:
> [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was
> created with MariaDB 10.3.27.
Before you upgrade, you need to
4 matches
Mail list logo
