Akonadi server issue

Discussions Regarding Software

Moderator: Moderators

Akonadi server issue

Postby Wiji » Sun May 11, 2014 15:14

Hello,

A friend has installed Sabayon(64b) on my computer, and it was working very well until as a result of an update Akonadi got broken because the "D-Bus session bus is not available !"

I've tried solutions found on KDE forums such as :
Solution 1
Code: Select all
cp ~/.local/share/akonadi ~/.backupAkonadi
 # find ~/.local/share/akonadi -iname *socket* -delete

Solution 2 :
Code: Select all
rm -r ~/.local/share/akonadi/
 rm -r ~/.config/akonadi/
 rm -r ~/.kde4/share/config/akonadi*

I have also looked at Sabayon known issues but the solutions didn't help solve the problem.

Here is the Akonadi Server Self-Test Report. With some information taken out for readability(much of the "success" taken out).

Code: Select all
===============================

Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi
server configuration and was found on your system.

File content of '/home/name/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-bazinbt.joWeIL/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS
--------

Test 3:  SUCCESS
--------

Test 4:  SUCCESS
--------

Test 5:  ERROR
--------

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

File content of '/home/name/.local/share/akonadi/db_data/mysql.err':
140501 12:07:04 [Note] Plugin 'FEDERATED' is disabled.
140501 12:07:04 InnoDB: The InnoDB memory heap is disabled
140501 12:07:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140501 12:07:04 InnoDB: Compressed tables use zlib 1.2.8
140501 12:07:04 InnoDB: Using Linux native AIO
140501 12:07:04 InnoDB: Initializing buffer pool, size = 80.0M
140501 12:07:04 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140501 12:07:04  InnoDB: Retrying to lock the first data file
[...]
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.


Test 6:  SUCCESS
--------

MySQL server default configuration found.


Test 7:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is
optional.

Test 8:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a
href='/home/name/.local/share/akonadi/mysql.conf'>/home/name/.local/share/akonadi/mysql.conf</a>
and is readable.


Test 9:  SUCCESS
--------
Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which
typically means it was not started or encountered a fatal error during
startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which
typically means it was not started or encountered a fatal error during
startup.

Test 12:  SUCCESS
--------
Test 13:  SUCCESS
--------
Test 14:  SKIP
--------
Test 15:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without
at least one. This usually means that no resource agents are installed or
that there is a setup problem. The following paths have been searched:
'/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set
to '/usr/share:/usr/local/share:/usr/share'; make sure this includes all
paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
[  ...   ]
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop


Environment variable XDG_DATA_DIRS is set to
'/usr/share:/usr/local/share:/usr/share'

Test 16:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The
log can be found in <a
href='/home/name/.local/share/akonadi/akonadiserver.error'>/home/name/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/name/.local/share/akonadi/akonadiserver.error':
DATABASE ERROR:
  Error code: 1048
  DB error:  "Column 'name' cannot be null"
  Error text: "Column 'name' cannot be null QMYSQL3: Unable to execute
statement"
  Query: "INSERT INTO PartTypeTable (ns, name) VALUES (:0, :1)"
"Column 'name' cannot be null QMYSQL3: Unable to execute statement"
Update failed
Failed to commit transaction for database update
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x34) [0x4719b4]
1: akonadiserver() [0x471dd1]
2: /lib64/libc.so.6(+0x38640) [0x7fb2d5ff4640]
3: /lib64/libc.so.6(gsignal+0x35) [0x7fb2d5ff45c5]
4: /lib64/libc.so.6(abort+0x148) [0x7fb2d5ff5a48]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74)
[0x7fb2d7aec7c4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x473d6b]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4)
[0x7fb2d7b85994]
8: /usr/lib64/qt4/libQtCore.so.4(+0x11b63f) [0x7fb2d7b9063f]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7fb2d7b98bcb]
10: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0x5ec) [0x477aec]
11: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x26e)
[0x7fb2d7c0b9ae]
12:
/usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)
[0x7fb2d7bf20be]
13:
/usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x361)
[0x7fb2d7bf56d1]
14: /usr/lib64/qt4/libQtCore.so.4(+0x1ab373) [0x7fb2d7c20373]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135)
[0x7fb2d5abeb75]
16: /usr/lib64/libglib-2.0.so.0(+0x4beb8) [0x7fb2d5abeeb8]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x34)
[0x7fb2d5abef74]
18:
/usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)
[0x7fb2d7c20506]
19:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)
[0x7fb2d7bf0d6f]
20:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)
[0x7fb2d7bf0ff8]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)
[0x7fb2d7bf6238]
22: akonadiserver(main+0x1b3) [0x46c5d3]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fb2d5fe0c45]
24: akonadiserver() [0x46cd71]
]
"


Test 17:  ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup.
The log can be found in <a
href='/home/name/.local/share/akonadi/akonadiserver.error.old'>/home/name/.local/share/akonadi/akonadiserver.error.old</a>.

File content of
'/home/name/.local/share/akonadi/akonadiserver.error.old':
DATABASE ERROR:
  Error code: 1048
  DB error:  "Column 'name' cannot be null"
  Error text: "Column 'name' cannot be null QMYSQL3: Unable to execute
statement"
  Query: "INSERT INTO PartTypeTable (ns, name) VALUES (:0, :1)"
"Column 'name' cannot be null QMYSQL3: Unable to execute statement"
Update failed
Failed to commit transaction for database update
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x34) [0x4719b4]
1: akonadiserver() [0x471dd1]
2: /lib64/libc.so.6(+0x38640) [0x7ff789021640]
3: /lib64/libc.so.6(gsignal+0x35) [0x7ff7890215c5]
4: /lib64/libc.so.6(abort+0x148) [0x7ff789022a48]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74)
[0x7ff78ab197c4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x473d6b]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4)
[0x7ff78abb2994]
8: /usr/lib64/qt4/libQtCore.so.4(+0x11b63f) [0x7ff78abbd63f]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7ff78abc5bcb]
10: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0x5ec) [0x477aec]
11: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x26e)
[0x7ff78ac389ae]
12:
/usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)
[0x7ff78ac1f0be]
13:
/usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x361)
[0x7ff78ac226d1]
14: /usr/lib64/qt4/libQtCore.so.4(+0x1ab373) [0x7ff78ac4d373]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135)
[0x7ff788aebb75]
16: /usr/lib64/libglib-2.0.so.0(+0x4beb8) [0x7ff788aebeb8]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x34)
[0x7ff788aebf74]
18:
/usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)
[0x7ff78ac4d506]
19:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)
[0x7ff78ac1dd6f]
20:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)
[0x7ff78ac1dff8]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)
[0x7ff78ac23238]
22: akonadiserver(main+0x1b3) [0x46c5d3]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff78900dc45]
24: akonadiserver() [0x46cd71]
]
"


Test 18:  SUCCESS
--------
Test 19:  SUCCESS
--------


Thanks a lot for your time.
Last edited by Wiji on Tue May 13, 2014 13:18, edited 1 time in total.
Wiji
Baby Hen
 
Posts: 2
Joined: Sun May 11, 2014 14:47

Re: Akonadi server issue

Postby Stupot » Mon May 12, 2014 19:32

I think this a fairly recent issue introduced in kde:

http://comments.gmane.org/gmane.comp.kd ... gs/1509747

I found a few other threads about it, although the files you attempted to delete should have handled a number of things. I'll try and take a look at this later, but it could be a number of things. Hopefully they get sorted out in the near future.
Stupot
Sagely Hen
 
Posts: 1538
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Akonadi server issue

Postby Wiji » Tue May 13, 2014 13:20

Thanks,
I'll be paying close attention to the thread.
How could I downgrade akonadi in the mean time?

EDIT:
In the KDE Bug thread I found;
Daniel Vrátil 2014-03-14 18:36:05 UTC
Ha! We found the culprit. GID is not supposed to be there, it's not a part. It looks like after an update you started KMail, but did not restart Akonadi, so KMail was sending the "GID" data, but Akonadi did not know it so it though it's a part type.

Ivan Adzhubey 2014-04-19 02:12:12 UTC
$ aux | grep mysqld
$ mysql --socket=/tmp/akonadi-${USER}.XXXXX/mysql.socket
mysql> use akonadi
mysql> DELETE FROM PartTable WHERE name = 'GID'; //
mysql> quit
Bye
$ akonadictl start

But I can't tell yet if it's going to work for me. I'll be back on it !
Last edited by Wiji on Tue May 13, 2014 14:49, edited 1 time in total.
Wiji
Baby Hen
 
Posts: 2
Joined: Sun May 11, 2014 14:47

Re: Akonadi server issue

Postby Lemuriano » Tue May 13, 2014 14:33

Portage has the version app-office/akonadi-server-1.11.0, but you should read the wiki about Portage before anything else.

Specially:

https://wiki.sabayon.org/index.php?title=HOWTO:_Safely_mix_Entropy_and_Portage
Sabayon x64 Xfce main
Intel core i5 M-520
linux-sabayon 3.15.0
User avatar
Lemuriano
Young Hen
 
Posts: 35
Joined: Tue Feb 26, 2013 5:22
Location: Florida, USA


Return to Software in General

Who is online

Users browsing this forum: No registered users and 3 guests

cron