[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"

[Martin Schnitkemper]

https://bugs.kde.org/show_bug.cgi?id=454948

--- Comment #16 from Martin Schnitkemper <martin.schnitkemper at nexgo.de> ---
I have now run the update on two systems and in both cases akonadi no longer
starts. I didn't get the "unknown error" error, but the file "ib_logfile0" was
missing after the first login.

A "touch $HOME/.local/share/akonadi/db_data/ib_logfile0" as suggested here
several times was not a solution because after the second logon I had 3200+
entries in mysql.err like
| [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number
1447482201 is in the future! Current system log sequence number 1378510903.
| [ERROR] InnoDB: Your database may be corrupt or you may have copied the
InnoDB tablespace but not the InnoDB log files. Please refer to
https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about
forcing recovery.

A "recovery" was not an option for me because it seems complicated to me, is
only insufficiently described in the MariaDB knowledgebase and I am not sure if
it solves the problem at all.

I had already completed the update to mariadb 10.8.3 last week and also updated
the structures with "mariadb-upgrade --socket=/run/user/$(id
-u)/akonadi/mysql.socket", it came therefore only the "KDE Gear 22.04.2" update
with akonadi and its accompanying components.

Based on the experience of the first system, I copied now the "ib_logfile0"
file to a safe place before updating the second system. After the file was
missing again after the update and the first logon, the easiest solution for me
was to copy the file back after the update and restart akonadi. It also
survived a reboot.

My recommendation is therefore to back up the file before an update or restore
it from a current backup. If it has already happened then it also helps to
delete (or rename) the "db_data" folder and start new with a 
"mariadb-install-db --datadir=$HOME/.local/share/akonadi/db_data --basedir=
/usr".

The question remains (and here I see the real problem) why akonadi or one of
its components removes the "ib_logfile0" file on the first logon after the
update.

-- 
You are receiving this mail because:
You are the assignee for the bug.