Bug 592870 - Akonadi fails to start
Summary: Akonadi fails to start
Alias: None
Product: Fedora
Classification: Fedora
Component: akonadi
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-17 09:13 UTC by Juha Tuomala
Modified: 2010-05-17 13:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-17 13:28:53 UTC
Type: ---

Attachments (Terms of Use)

Description Juha Tuomala 2010-05-17 09:13:31 UTC
Description of problem:
I restart desktop machine after updates, and Kmail fails to start complaining that Akonadi fails.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log in to KDE
2. Start Kmail
3. It fails and exists.
Actual results:
Error dialog, saying that 'MySQL server log contains errors'.

100517 12:08:19 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: Unable to lock ./ib_logfile0, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Error in opening ./ib_logfile0
100517 12:08:19 [ERROR] Plugin 'InnoDB' init function returned error.
100517 12:08:19 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
100517 12:08:19 [ERROR] Unknown/unsupported table type: innodb
100517 12:08:19 [ERROR] Aborting

100517 12:08:19 [Note] /usr/libexec/mysqld: Shutdown complete

Comment 1 Juha Tuomala 2010-05-17 12:48:46 UTC
You can leave the akonadi error dialog open and kmail seems to work fine with IMAP  connections (why it forces to use it in the first place?), but korganizer gives:

  Error while loading akonadi calendar.

any suggestions how to work around this one? I can't access my work calendar which hurts my business. :-/

Comment 2 Rex Dieter 2010-05-17 12:56:23 UTC
Those are mysql errors, have you updated mysql recently?  (see /var/log/yum.log )

Comment 3 Rex Dieter 2010-05-17 12:57:59 UTC
Otherwise, this is the most telling,
InnoDB: Unable to lock ./ib_logfile0, error: 11

you can try using the 'lsof' tool, to see if anything on the system has an open lock or filehandle on this file.

else, maybe try rebooting?

Comment 4 Juha Tuomala 2010-05-17 13:03:28 UTC
# grep mysql /var/log/yum.log 
Mar 09 17:24:36 Installed: mysql-libs-5.1.44-1.fc12.x86_64
Mar 09 17:25:15 Installed: mysql-5.1.44-1.fc12.x86_64
Mar 09 17:25:19 Installed: mysql-server-5.1.44-1.fc12.x86_64
Mar 09 17:25:19 Installed: 1:qt-mysql-4.6.2-3.fc12.x86_64
Mar 09 17:25:50 Installed: mysql-embedded-5.1.44-1.fc12.x86_64
Mar 25 13:08:11 Updated: 1:qt-mysql-4.6.2-8.fc12.x86_64
Apr 23 14:33:24 Updated: mysql-libs-5.1.45-2.fc12.x86_64
Apr 23 14:34:53 Updated: mysql-5.1.45-2.fc12.x86_64
Apr 23 14:34:56 Updated: mysql-server-5.1.45-2.fc12.x86_64
Apr 23 14:35:16 Updated: mysql-embedded-5.1.45-2.fc12.x86_64
May 10 12:38:19 Updated: 1:qt-mysql-4.6.2-16.fc12.x86_64

well, yes and no. I do reboot quite rarely so the end of last month's update could have done it.

# lsof|grep -c ib_log

this box boots so long time that i try to avoid it. :-/

Comment 5 Rex Dieter 2010-05-17 13:09:30 UTC
Also, I'm not a mysql guru, but you could try deleting anything that matches
to see if that helps.  (I think it should get re-created automatically on next launch),

$ akonadictl restart

Speaking of failed locks, are you using an nfs homedir?

Comment 6 Juha Tuomala 2010-05-17 13:13:32 UTC
~/.local/share/akonadi/db_data% rm -rf *
zsh: sure you want to delete all the files in /home/tuju/.local/share/akonadi/db_data [yn]? y

helped! (i use akonaditray-applet to restart)

Yes, I use NFS as $HOME.

Comment 7 Juha Tuomala 2010-05-17 13:17:10 UTC
Crap. now korganizer is empty.

Don't tell me that it stored its entries into that dir, not acting as cache only...?

Comment 8 Juha Tuomala 2010-05-17 13:28:25 UTC
nope...config still points to .pim/calendar/ Directory resource, it just doesn't show anything.

Comment 9 Rex Dieter 2010-05-17 13:28:53 UTC
I only suggested removing the ib_logfiles , nothing more.  there is a bit of extra information stored in the akonadi db, though I'm not entirely familiar with the implementation details.

For the purposes of this issue,
InnoDB: Unable to lock ./ib_logfile0, error: 11

working around the failed nfs locking seems resolved now (marking worksforme, unless we're uber interested in trying to followup on how/why the nfs file locking failed).

Note You need to log in before you can comment on or make changes to this bug.