[Bug 578357] Re: MySql log file problem prevents Akonadi startup

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=238217.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-05-19T19:37:50+00:00 Cubranic-w wrote:

Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

I originally reported this bug in Ubuntu Launchpad:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357

I am opening it here as a wider issue: Akonadi is very fragile in the
face of mysql startup problems, and that has a knock-on effect of
preventing basic user applications (mail, PIM) from running.

The most visible symptom of the problem was that after starting up
KMail, I would get an error dialog stating that Akonadi is not running.
After closing the dialog, the app would close also.

I started investigating, and got voluminous, but not very helpful error
output when running 'akonadictl start' from the command line. (I'll
attach a copy.) Further poking and twiddling with apparmor and other
workarounds suggested in various bugs and forums was unsuccessful.
Eventually, I stumbled upon mysql.err in ~/.local/share/akonadi/db_data/
with the following contents:

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 9:49:38 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
 100519 9:49:38 [ERROR] Unknown/unsupported table type: innodb
 100519 9:49:38 [ERROR] Aborting
100519 9:49:38 [Note] /usr/sbin/mysqld-akonadi: Shutdown complete

File 'ib_logfile1' was indeed of size zero. Deleting it and
'ib_logfile0', and then restarting 'akonadictl' seemed to fix the
problem and I now have a working mail reader.

I don't know how the log file got corrupted, but the system should be
more robust than that. I mean, having a zero-size or corrupted log file
does not need to be an unrecoverable error!

It's completely reasonable in such a situation to delete it and proceed
with startup. The database should still be in a consistent state, and
the worst that could happen is that the last few transactions are
missing. Or at the very least notify the user what the real problem is.
As it is, akonadi server's output is utterly unhelpful, and it took me
forever to find Akonadi's mysql.err, where the problem was actually
clearly identified.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/7

------------------------------------------------------------------------
On 2010-05-19T19:40:53+00:00 Cubranic-w wrote:

Created attachment 43736
Output of 'akonadictl start' when MySql fails to start

This is the output of running 'akonadictl start' from the console before
I vixed the problem by deleting the corrupted logfiles. This output
actually repeats three times. (Why?)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/8

------------------------------------------------------------------------
On 2010-09-14T22:52:52+00:00 reagle wrote:

I have the same problem too. Moving to akonadi has been a disaster for
me as a user. Beside this breakage, how does one even backup one's email
files even?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/13

------------------------------------------------------------------------
On 2010-11-10T17:59:00+00:00 João Eiras wrote:

*** Bug 256527 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/15

------------------------------------------------------------------------
On 2011-03-13T16:31:37+00:00 Ricardo Graça wrote:

*** This bug has been confirmed by popular vote. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/17

------------------------------------------------------------------------
On 2016-09-24T20:38:55+00:00 Kdenis wrote:

This bug has only been reported for versions older than KDEPIM 4.14 (at
most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE
Applications 15.08 or later), it gets closed in about three months.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/578357/comments/24


** Changed in: akonadi
       Status: Unknown => Incomplete

** Changed in: akonadi
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/578357

Title:
  MySql log file problem prevents Akonadi startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/578357/+subscriptions