https://bugs.kde.org/show_bug.cgi?id=454948
--- Comment #15 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Kishore Gopalakrishnan from comment #14) > (In reply to Oleksandr Natalenko from comment #4) > > All, if you expect some help on this, post your > > `~/.local/share/akonadi/db_data/mysql.err`. It might be the case the DB > > needs upgrade, and to find out also post the output of this: > > > > ``` > > $ mariadb-upgrade --defaults-file=~/.local/share/akonadi/mysql.conf > > --socket=/run/user/$(id -u)/akonadi/mysql.socket > > --check-if-upgrade-is-needed > > ``` > > The command you gave indeed says that an upgrade is required: > > [kishore@kishorearchtestingVM ~]$ mariadb-upgrade > --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/run/user/$(id > -u)/akonadi/mysql.socket --check-if-upgrade-is-needed > Major version upgrade detected from 10.7.4-MariaDB to 10.8.3-MariaDB. Check > required! Just running `mariadb-upgrade --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/run/user/$(id -u)/akonadi/mysql.socket` and then rebooting fixed this, but it doesn't seem to be related to the reported issue (akonadi was able to start even with an outdated database as long as the ib_logfile0 file was present). -- You are receiving this mail because: You are watching all bug changes.
