(Just partially fixed) Who killed Akonadi?

[Bald Brick]

After a routine update a couple of days ago the Akonadi server won't start. At first the self-test dialogue reported very many errors; after following this advice from the KDE site the number is down to five:

Copy it from /usr/share/config/akonadi/mysql-global.conf into ~/.config/akonadi/mysql-local.conf. (For debian and openSuSE users the file is located in /etc/akonadi/mysql-global.conf). Then open it and uncomment the line sql_mode=strict_trans_tables.

The most serious one seems to be that Akonadi can't find any resource agents. It's looking for them in /usr/share/akonadi/agents, where the XDG_DATA_DIRS environment variable tells it to.

I'm also informed that neither the Akonadi control process nor the Akonadi server process are registered at D-Bus, which is probably a result of the above: not finding the resource agents Akonadi is simply not running. On top of that the error dialogue complains about some error logs.

I have reinstalled Akonadi and mysql-core, and after some googling I tried renaming the ~/.config/akonadi and ~/.local/share/akonadi/db_data directories. Smaller versions lacking most of the contents of the old ones were created, but apart from that no change.

Strangely enough Strigi runs happily without Akonadi.

I would have attached the latest self-test log but the option seems to have gone missing. I will probably add selected parts of it to a follow-up post instead. (In its entirety it's too long for a post.)

[menotu]

Yup - I had an Akonadi issue a couple of days ago but it seems to of been resolved. (well, no more error messages) and it didn't cause any problems whilst running Kontact

[Bald Brick]

Yup - I had an Akonadi issue a couple of days ago but it seems to of been resolved. (well, no more error messages) and it didn't cause any problems whilst running Kontact

Most of those errors I got rid of by copying/creating/editing ~/.config/akonadi/mysql-local.conf. My remaining errors:



(My KDE speaks Swedish, but you get the idea.)

Kontact appears to work well here too. I haven't had time to test all modules and functions though.

[BrandNewDay]

That was me. Sorry. Don't know how I did it, or even what Akonadi is, but it was me what done it.

[Bald Brick]

That was me. Sorry. Don't know how I did it, or even what Akonadi is, but it was me what done it.

You are forgiven. You do of course realize you will have to go to prison anyway? But it might be a mitigating circumstance that the problem immediately resolved itself when you confessed.

Actually, everything is all right again and I have no idea what fixed it.

I first restored the directories I had renamed. Then I recreated ~/.config/akonadi/mysql-local.conf. Then I rebooted. And Akonadi started.

It oughtn't to because the configuration files were in precisely the same state as two days ago when it didn't start. But it did.

The self-test still complained about some log files though. I thought about removing them manually, but as a test I logged in at a tty and ran "akonadictl stop". I couldn't restart it from the terminal so I rebooted. Problem fixed. And I don't really know what fixed it.

[Texstar]

Very odd. I haven't had any issues with the akonadi update. 

[Bald Brick]

I was overly optimistic. On reboot I still get the error messages about the log files. But at least Akonadi starts and runs well enough. I'll try removing the log files later tonight.

[menotu]

I was overly optimistic. On reboot I still get the error messages about the log files. But at least Akonadi starts and runs well enough. I'll try removing the log files later tonight.

Ditto: came back to me as well but it doesn't appear to cause any problems for running Kontact. 

Will keep my eye on it for a few days. If it persists I'll possibly rename the .config/akonadi &  .local/share/akonadi/db_data folders

[Crow]

Akonadi failed here too and Sefi's remaster broke when I tried to update a new install. That computer was working and completely updated one hour before (don't ask)

I know is not officially supported and I'd put a message to Sefi but I think it was interesting to let you know

[Bald Brick]

I think this is the most important error message:

Test 4:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/erik/.local/share/akonadi/db_data/mysql.err'>/home/erik/.local/share/akonadi/db_data/mysql.err[/url]&apos; contains errors.

File content of '/home/erik/.local/share/akonadi/db_data/mysql.err':
100807 21:59:07 [ERROR] Can't open shared library '/LIBDIR/mysql/plugin/ha_innodb.so' (errno: 0 cannot open shared object file: No such file or directory)
100807 21:59:14  InnoDB: Started; log sequence number 0 327290
100807 21:59:14 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
100807 21:59:14 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
100807 21:59:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.42'  socket: '/home/erik/.local/share/akonadi/db_misc/mysql.socket'  port: 0  PCLinuxOS 2010 - MySQL Standard Edition (GPL)

And to start somewhere: ha_innodb.so really doesn't exist on my system.


Added:

I wish the same fate on the KDE people who forced Akonadi on us before it's ready as I wish on the spammers who forced Tex to shut down the forums for two days: string'em up!

[mikkl]

I too am having Akonadi error messages.  In my case, it is complaining about the mysql logs and that Nepomuk is not registered with dbus.

mikkl

[mikkl]

Regarding ha_innodb.so --  I think this is a mysql build problem.  According to the Akonadi error log, the mysql configuration files contains the following lines:

# plugins
plugin_dir=LIBDIR/mysql/plugin
plugin-load=ha_innodb.so

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

The problem is, however, that ha_innodb.so is not located on my system.  So, either the mysql build is missing a required plugin or the configuration files are incorrect.  In either case, this looks like a build problem.

The second error I receive is that Nepomuk is not registered with DBus.  Checking the Services tab of PCC, Nepomuk does not show up as a service and "top" does not list an application by that name as running.  Searching Synaptic for Nepomuk shows that the kdebase4-runtime-nepomuk package is not installed.  Could this be part of the problem?

The last two errors are that there were Akonadi error logs, both of which indicated " D-Bus session bus went down - quitting"

Not at all certain what could cause this error.

mikkl

[Bald Brick]

The second error I receive is that Nepomuk is not registered with DBus.  Checking the Services tab of PCC, Nepomuk does not show up as a service and "top" does not list an application by that name as running.  Searching Synaptic for Nepomuk shows that the kdebase4-runtime-nepomuk package is not installed.  Could this be part of the problem?

Well, here kdebase4-runtime-nepomuk is installed and nepomuk is running. (nepomukserver and seven instances of nepomukservices). It does not show up in PCC though, but that is hardly surprising as it's started locally from within KDE. And it does show up in systemsettings.

[Bald Brick]

Regarding ha_innodb.so --  I think this is a mysql build problem.  According to the Akonadi error log, the mysql configuration files contains the following lines:

# plugins
plugin_dir=LIBDIR/mysql/plugin
plugin-load=ha_innodb.so

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

The problem is, however, that ha_innodb.so is not located on my system.  So, either the mysql build is missing a required plugin or the configuration files are incorrect.  In either case, this looks like a build problem.

ha_innodb.so seems to be part of the mysqld-max package -- which I wasn't brave enough to install as Synaptic wants to remove too many other packages (including akonadi) if one does install it.

[mikkl]

The second error I receive is that Nepomuk is not registered with DBus.  Checking the Services tab of PCC, Nepomuk does not show up as a service and "top" does not list an application by that name as running.  Searching Synaptic for Nepomuk shows that the kdebase4-runtime-nepomuk package is not installed.  Could this be part of the problem?

Well, here kdebase4-runtime-nepomuk is installed and nepomuk is running. (nepomukserver and seven instances of nepomukservices). It does not show up in PCC though, but that is hardly surprising as it's started locally from within KDE. And it does show up in systemsettings.

Do you get the Nepomuk error message when Adonadi starts?

mikkl