Akonadi personal information management system is non operational

Hi all,

Wondering if anybody is experiencing issues with Akonadi not continuing to run, maybe in association with database issues?

I’m running Mageia 9 with Akonadi 23-04-3 and MariaDB 11.4.10. The mariadb stuff upgraded not long ago and I’m not sure if the issues I’m experiencing coincided with this, or not.

When Kmail failed to open a day ago, it gave the following message:

“The akonadi personal information management service is not operational.”

So I tried to start akonadi at the console: akonadictl start

This gave the following:

org.kde.pim.akonadictl: Starting Akonadi Server…
org.kde.pim.akonadictl: done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[andrew@localhost akonadi]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server…
/usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use ‘/usr/bin/mariadb-check’ instead
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
etc
akonadi.tagtypetable OK
/usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use ‘/usr/bin/mariadb-upgrade’ instead
This installation of MariaDB is already upgraded to 11.4.10-MariaDB.
There is no need to run mariadb-upgrade again.
You can use --force if you still want to run mariadb-upgrade
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: “2013”
org.kde.pim.akonadiserver: DB error: “Lost connection to server during query”
org.kde.pim.akonadiserver: Error text: “Lost connection to server during query QMYSQL3: Unable to execute statement”
org.kde.pim.akonadiserver: Values: QMap((“:0”, QVariant(QString, “akonadi”))(“:1”, QVariant(QString, “SchemaVersionTable”)))
org.kde.pim.akonadiserver: Query: “SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schem
a.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_
schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENT
IAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_sche
ma.KEY_COLUMN_USAGE.TABLE_NAME = :1 )”
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: “2006”
org.kde.pim.akonadiserver: DB error: “Server has gone away”
org.kde.pim.akonadiserver: Error text: “Server has gone away QMYSQL3: Unable to execute statement”
org.kde.pim.akonadiserver: Values: QMap((“:0”, QVariant(QString, “akonadi”))(“:1”, QVariant(QString, “ResourceTable”)))
org.kde.pim.akonadiserver: Query: “SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schem
a.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_
schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENT
IAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_sche
ma.KEY_COLUMN_USAGE.TABLE_NAME = :1 )”
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: “2006”
org.kde.pim.akonadiserver: DB error: “Server has gone away”

I’m running the default akonadiserverrc (see below):

[%General]

Driver=QMYSQL

[QMYSQL]

Host=

Name=akonadi

Options=“UNIX_SOCKET=/run/user/1000/akonadi/mysql.socket”

ServerPath=/usr/sbin/mysqld

StartServer=true

So to summarise, akonadi starts, then appears to try to access a database/table, several times, before giving up when it has failed to do so.

This inability for akonadi to run, is system-wide. So if I exit my desktop and login to another user desktop, and again to try to open kmail, I get the same warning message. “The akonadi personal information management service is not operational.” So the issues don’t appear to be caused by anything that I have done within my own user environment

So is this failure to start akonadi caused by a fundamental incompatibility between the Akonadi version and the Mariadb version that I have?

One further thing: I understand that Akonadi doesn’t normally use the system-wide mysql/Mariadb, but rather is using some mysql version/installation of its own. Is it possible that those databases/tables (such as information schema) might need some repair before akonadi can start up? If so, in what directories will I find these databases?

Any insights will be greatly appreciated, as life without access to my emails is becoming very challenging!! Cheers!

I also encounter some problem with akonadi in kmail. Maybe is it due to work done to move it as new frameworks library.

If you have a problem with mariadb you could switch to Sqlite3 backend. Akonadi-db-migrator is now included in kde.

akonadi-db-migrator --newengine sqlite

Your version of mariabd is broken, ask your distribution to backport the fix