Hi,

my experience with this kind of errors from MySQL/MariaDB is that adding

innodb_force_recovery = 3

option to mysql.conf usually helps. Then just start Akonadi, which should fix whatever MySQL is unhappy about, then stop Akonadi, remove the option from mysql.conf, start Akonadi again and everything should work.

Note that you can't run Akonadi with innodb_force_recovery normally, as it makes the database read-only, so the start-stop cycle is only needed to start MySQL. You can also just start MySQL manually, but I can't remember the arguments from top of my head.

Dan

On Sunday 03 of August 2014 10:19:51 José Matos wrote:

Hi, yesterday I decided to upgrade to Fedora 21, soon to be in Alpha. It all works smoothly and my only problem was with akonadi and thus with kmail.

Where I got [ERROR] mysqld got signal 11 ;

The full error log is available as attachment.

Since despair is not an option I searched for help and I got to this page about Arch and the same problem:

https://bbs.archlinux.org/viewtopic.php?id=184192

After reading I decided to remove the ~/.local/share/akonadi/mysql.conf

log out and log in and voilá I am again an happy camper. :-)

FWIW, as reported in the link above, there is not any difference between the file that I had removed (moved actually, not that it matters) and the new file placed there. I suspected that the absence of that file triggers the right procedure.

I hope this helps others.

Regards,