I opened a related KDE bug (https://bugs.kde.org/show_bug.cgi?id=238217)
to bring up the issue of Akonadi's fragility to the attention of KMail
devs.
** Bug watch added: KDE Bug Tracking System #238217
http://bugs.kde.org/show_bug.cgi?id=238217
--
Akonadi startup error with no MySql
https://b
Mysql.err that identified the problem:
100519 9:49:38 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Error: log file ./ib_logfile1 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 67108864 bytes!
100519 9:49:38 [ERROR] Plugin 'InnoDB' init function returned error.
100519
Deleting both ib_logfile0 and ib_logfile1 in
~/.local/share/akonadi/db_data/, and then running 'akonadictl start'
fixed the problem for me. I don't know how the log file got corrupted,
but the system should be more robust than that. I mean, deleting a
(corrupted) log file does not need to be an unr
I found interesting error messages in
~/.local/share/akonadi/db_data/mysql.err. It looks like the problem
might have to do with the (zero) size of a MySQL log file in that
directory, which causes MySQL startup to abort. (see attachment)
** Attachment added: "Akonadi's MySQL error log"
http://la
Unfortunately, that didn't help. Even stopping AppArmor (by running
'/etc/init.d/apparmor stop') makes no difference whatsoever -- I still
get the same stack trace.
--
Akonadi startup error with no MySql
https://bugs.launchpad.net/bugs/578357
You received this bug notification because you are a m
I had the same problem, and it was fixed running:
sudo aa-complain mysqld
sudo aa-complain mysqld-akonadi
sudo /etc/init.d/apparmor reload
akonadictl start
--
Akonadi startup error with no MySql
https://bugs.launchpad.net/bugs/578357
You received this bug notification because you are a member of
