Author Topic: (Just partially fixed) Who killed Akonadi?  (Read 1252 times)

Offline Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6379
  • I'm going South
Re: (Just partially fixed) Who killed Akonadi?
« Reply #15 on: August 08, 2010, 02:45:31 PM »
Do you get the Nepomuk error message when Adonadi starts?

No. At this moment the only error messages I get are:

1) MySQL server log contains errors,
2) Previous Akonadi server error log found,
3) Current Akonadi control error log found.

(Translated back into English from Swedish -- but I don't think I missed anything.)

These errors don't seem to impede the running of Akonadi but cosmetically they are a nuisance.
« Last Edit: August 08, 2010, 02:53:13 PM by blackbird »
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
Re: (Just partially fixed) Who killed Akonadi?
« Reply #16 on: August 14, 2010, 05:50:06 AM »
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



Doing some digging, I see that the sql config file I mention above was created by Akonadi and therefore needs to be modified in order to prevent these mysql errors.  Working out how to do that now.

mikkl

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
Re: (Just partially fixed) Who killed Akonadi?
« Reply #17 on: August 14, 2010, 06:31:20 AM »
Making a little bit of progress.  Went into the config file and commented out the plugin-load lines and the default=innodb line.

Now the mysql error log reports that innodb started and that there are new errors to be debugged.

Yes, I realize that 4.5 is about to go stable and this problem may go away but I'm going to hold off until all the other packages are compiled and I'm curious to solve this.

mikkl

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
Re: (Just partially fixed) Who killed Akonadi?
« Reply #18 on: August 14, 2010, 07:40:08 AM »
Following a couple of pages from the Arch forums, I believe that I have solved this problem (or at least hidden it)

I corrected the initial mysql errors by editing the configuration file found in  ~/.local/share/akonadi  and commenting out 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

I then received new errors about being unable to lock specific tables.

From:  https://bbs.archlinux.org/viewtopic.php?pid=695037, I tried the following and it solved all of the remaining mysql errors:

<quote>
stop akonadi

akonadictl stop

remove the db_data dir:

rm  -r ~/.local/share/akonadi/db_data

recreate mysqldb with

mysql_install_db --datadir=$HOME/.local/share/akonadi/db_data/

restart akonadi

akonadictl start

worked for me.

</quote>

After installing Nepomuk and setting it for desktop search and deleting the Akonadi error logs, I was left with one error:  protocol version could not be verified.

I corrected/avoided this error by following the recommendations on this Arch page:  https://bbs.archlinux.org/viewtopic.php?pid=772278

<quote>
alternatively, go to system settings -> advanced -> kde resources, add an akonadi resource for contacts and one for the calendar and make them standard.
This will ensure that the agent starts and will also get rid of the "akonadi-is-starting" bar that appears the first time you open kmail per every session.

Afterward, you may want to remove any other pre-existing non-akonadi resource, but remember to export your data to the new akonadi resource if you don't want to lose it.
</quote>

On my next reboot and opening of Kontact/Kmail, the Akonadi server bar did not show, nor did the error message.  My last test ws to disable nepomuk, reboot, and load Kontact.  This too successfully avoided the error screen, even though checking the logs I find that the Nepomuk DBus error is logged.

Kontact and all of the features (calendars, contacts, etc) seem to be working fine.

mikkl

Offline Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6379
  • I'm going South
Re: (Just partially fixed) Who killed Akonadi?
« Reply #19 on: August 14, 2010, 09:00:20 AM »
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

Not anymore. I don't really know when I stopped getting it. (And kdebase4-runtime-nepomuk has been installed all the time.)

Running
Code: [Select]
mysql_install_db --datadir=$HOME/.local/share/akonadi/db_data/got rid of most of the errors.

The KDE page recommended it for openSUSE and as I found that mysql_install_db existed on my system I tried it and it helped, if only partially.

Today the most important error still concerns the MySQL server log containing errors (Test 4), but its entry in the self-test log has shrunk substantially to:

Quote
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':
100811 19:51:35 [ERROR] Function 'InnoDB' already exists
100811 19:51:35 [ERROR] Couldn't load plugin named 'InnoDB' with soname 'ha_innodb.so'.
100811 19:51:39  InnoDB: Started; log sequence number 0 330784
100811 19:51:40 [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)

The line:
Quote
100811 19:51:35 [ERROR] Couldn't load plugin named 'InnoDB' with soname 'ha_innodb.so'.
is the result of my using an ha_innodb.so extracted from mysqld-max as I still dare not install that package.

Before that the error log looked like this:
Quote
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':
100811 14:55:55 [ERROR] Can't open shared library '/LIBDIR/mysql/plugin/ha_innodb.so' (errno: 0 cannot open shared object file: No such file or directory)
100811 14:56:01  InnoDB: Started; log sequence number 0 329458
100811 14:56:03 [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)

Actually I haven't tried to fix this error for a couple of days. It seems to be entirely cosmetic: I have to close an error dialogue at boot but after that everything works.
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D