Akonadi server start crashes at session login

[Swâmi Petaramesh]

Hi,

Right after I boot and login into KDE, if I start Kmail this will fire up a popup stating that Akonadi server is starting.

Then I get a failure message with a list of checks stating that MySQL failed starting and inviting me to inspect its log. If I do I find messages like :

100410 18:33:34 InnoDB: Error: page 1 log sequence number 0 226470
InnoDB: is in the future! Current system log sequence number 0 193949.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.

From there, if I close the error box, Kmail will die as well, but if I restart KMail if will then open gracefully without any error (and "ps" shows me that mysql server is running).

I don't believe I have any system clock problem that would make it live in the future ;-)

I have tried to restart MySQL manually in table-fix mode just to make sure, but it didn't change the behaviour that the 1st start of Akonadi after bootup/login always have on my system :-/

So I'm used to start KMail twice, closing an error box in between :-/

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: akonadi-server 1.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 18:44:56 2010
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: akonadi

[Harald Sitter (apachelogger)]

Can you please tell us a bit more about your system? Is it a fresh install of 10.04? If so at about what time did you install it? If not, which upgrades did it see yet? 9.04->9.10->10.04? 9.10->9.04? Other? Do you happen to have data in Akonadi? (addressbook data, calendar data)

[Swâmi Petaramesh (swami-petaramesh)]

@Harald : Actually it's an upgrade Karmic => Lucid, and the whole Karmic install had been ripped from another machine when it had had a path like Jaunty => Karmic...

I don't have data in Akonadi AFAIK, at least not much if any.

I will attach tables status obtained with : $ mysql --socket=/home/myself/.local/share/akonadi/db_misc/mysql.socket akonadi -e "show table status;" > ~/tmp/akonadi_table_status.txt

If my Akonadi is emtpy as it looks, I wouldn't mind resetting the DB and restartting from scratch if it may help getting rid of errors...

[Harald Sitter (apachelogger)]

Oh that ripped from another machine would explain it. See, your error says that for some reason the timestamp in your log seems odd too innodb. I doubt we can do much about this particular portability flaw.

It would however be cool if you could check with wiped akonadi data, but only in 2 days, I am still working on some important fixes that prevent first start issues.

For the time being it would be cool if you could move the ib_logfile* files in .local/share/akonadi/ somewhere else while akonadi is not running (akonadictl stop) and then start akonadi. If I am not mistaken that should give a warning but recreate the logs so that further starts should work just fine (I might be wrong though).

[Swâmi Petaramesh (swami-petaramesh)]

Hi again Harald,

It seems that moving the ib_logfile* wasn't enough, neither was to put the binary logs out of the way.

So in the end I just rm -rf ~/.local/share/akonadi/db_data then let it recreate itself.

Therafter I don't have any MySQL errors anymore (for now...) but I get a couple other Akonadi errors (in french so I translate, see original attached image), basically one that says that "the Akonadi server process is not registered in D-bus" and the other that "No resource agent has been found"...

Go figure... ;-)

[Harald Sitter (apachelogger)]

Both should be fixed in the package uploads I did yesterday, so those error should resolve within the next couple of updates. I am marking this bug invalid since the original issue is now gone, though since we neither know why it happened nor how to prevent it, I would not dare talking about a fix :(

[ivan (ivan.tg)]

Hi everyone,
After a clean install of release Kubuntu 10.04 i can confirm the non-mysql errors as described in #5 still appear on first start of Kmail.
However, i have disabled Nepomuk. Could it be this what's causing the Akonadi error pop-up?

[Harald Sitter (apachelogger)]

No, because #5 clearly shows that the Nepomuk tests succeeds.