This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Kmail, PIM Akonadi won't start

Tags: None
(comma "," separated)
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Kmail, PIM Akonadi won't start

Mon Apr 28, 2014 11:06 am
I had to reinstall opensuse but left my home directory hoping my mails would all remain. Now when I try to get into kmail or anything else related to that it fails.
Below, I've included the rollout when starting from a terminal

Code: Select all
linux-wnq6:~ # akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
linux-wnq6:~ # search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:44 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:44 [ERROR] Aborting

140428 18:59:44 [Note] /usr/sbin/mysqld: Shutdown complete

"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f3951b158d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f3951b15849]
4: /lib64/libc.so.6(abort+0x148) [0x7f3951b16cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f395362b204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f39536c5830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f39536d2c2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f39536db813]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x4542a9]
11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1dca) [0x4d22da]
12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd7) [0x45cba7]
13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45e8d2]
14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f395374d11e]
15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f39537350ad]
16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f39537380ff]
17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f3953762493]
18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f39511e8e24]
19: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f39511e9068]
20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f39511e910c]
21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f3953761d55]
22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f3953733d0f]
23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f3953734005]
24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f395373913b]
25: akonadiserver(main+0x1bf) [0x453a6f]
26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f3951b01be5]
27: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:44 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:44 [ERROR] Aborting

140428 18:59:44 [Note] /usr/sbin/mysqld: Shutdown complete

"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7fa7038a08d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7fa7038a0849]
4: /lib64/libc.so.6(abort+0x148) [0x7fa7038a1cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7fa7053b6204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fa705450830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7fa70545dc2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7fa705466813]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x4542a9]
11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1dca) [0x4d22da]
12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd7) [0x45cba7]
13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45e8d2]
14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7fa7054d811e]
15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7fa7054c00ad]
16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7fa7054c30ff]
17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7fa7054ed493]
18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7fa702f73e24]
19: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7fa702f74068]
20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fa702f7410c]
21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7fa7054ecd55]
22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7fa7054bed0f]
23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7fa7054bf005]
24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7fa7054c413b]
25: akonadiserver(main+0x1bf) [0x453a6f]
26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa70388cbe5]
27: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:45 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:45 [ERROR] Aborting

140428 18:59:45 [Note] /usr/sbin/mysqld: Shutdown complete

"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f057a9a68d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f057a9a6849]
4: /lib64/libc.so.6(abort+0x148) [0x7f057a9a7cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f057c4bc204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f057c556830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f057c563c2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f057c56c813]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x4542a9]
11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1dca) [0x4d22da]
12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd7) [0x45cba7]
13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45e8d2]
14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f057c5de11e]
15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f057c5c60ad]
16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f057c5c90ff]
17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f057c5f3493]
18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f057a079e24]
19: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f057a07a068]
20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f057a07a10c]
21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f057c5f2d55]
22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f057c5c4d0f]
23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f057c5c5005]
24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f057c5ca13b]
25: akonadiserver(main+0x1bf) [0x453a6f]
26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f057a992be5]
27: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:45 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:45 [ERROR] Aborting

140428 18:59:45 [Note] /usr/sbin/mysqld: Shutdown complete

"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f0bdf8198d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f0bdf819849]
4: /lib64/libc.so.6(abort+0x148) [0x7f0bdf81acd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f0be132f204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f0be13c9830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f0be13d6c2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f0be13df813]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x4542a9]
11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1dca) [0x4d22da]
12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xd7) [0x45cba7]
13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45e8d2]
14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f0be145111e]
15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f0be14390ad]
16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f0be143c0ff]
17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f0be1466493]
18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f0bdeeece24]
19: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f0bdeeed068]
20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f0bdeeed10c]
21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f0be1465d55]
22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f0be1437d0f]
23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f0be1438005]
24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f0be143d13b]
25: akonadiserver(main+0x1bf) [0x453a6f]
26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0bdf805be5]
27: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!
wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Mon Apr 28, 2014 6:12 pm
joshaughnessy wrote:I had to reinstall opensuse but left my home directory hoping my mails would all remain. Now when I try to get into kmail or anything else related to that it fails.
Below, I've included the rollout when starting from a terminal

Code: Select all
linux-wnq6:~ # akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
linux-wnq6:~ # search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:44 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:44 [ERROR] Aborting

You are trying to run Akonadi as root. That doesn't work.
Try to run it as normal user instead, i.e. not in a "Superuser-Mode" Konsole, don't run "su" before, and don't login as root.
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Wed Apr 30, 2014 2:45 am
wolfi323 wrote:
joshaughnessy wrote:I had to reinstall opensuse but left my home directory hoping my mails would all remain. Now when I try to get into kmail or anything else related to that it fails.
Below, I've included the rollout when starting from a terminal

Code: Select all
linux-wnq6:~ # akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
linux-wnq6:~ # search paths:  ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/root/.local/share/akonadi/mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-root.NVGLEK/mysql.socket")
stdout: ""
stderr: "140428 18:59:44 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

140428 18:59:44 [ERROR] Aborting

You are trying to run Akonadi as root. That doesn't work.
Try to run it as normal user instead, i.e. not in a "Superuser-Mode" Konsole, don't run "su" before, and don't login as root.

it does exactly the same with the same output at the end when I run it as USER (me), so that;s not the problem.... Also any program that uses akonadi (such as kmail) givves the error that akonadi won;t start..... I need to do something soon or change to another email program
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Wed Apr 30, 2014 2:48 am
john@linux-wnq6:~> akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
john@linux-wnq6:~> search paths: ("/home/john/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7fc63fdee8d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7fc63fdee849]
4: /lib64/libc.so.6(abort+0x148) [0x7fc63fdefcd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7fc641904204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fc64199e830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7fc6419abc2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7fc6419b4813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7fc641a2611e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7fc641a0e0ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7fc641a110ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7fc641a3b493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7fc63f4c1e24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7fc63f4c2068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fc63f4c210c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7fc641a3ad55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7fc641a0cd0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7fc641a0d005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7fc641a1213b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fc63fddabe5]
24: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths: ("/home/john/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f47269f28d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f47269f2849]
4: /lib64/libc.so.6(abort+0x148) [0x7f47269f3cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f4728508204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f47285a2830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f47285afc2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f47285b8813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f472862a11e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f47286120ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f47286150ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f472863f493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f47260c5e24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f47260c6068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f47260c610c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f472863ed55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f4728610d0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f4728611005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f472861613b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f47269debe5]
24: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths: ("/home/john/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f50daaf88d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f50daaf8849]
4: /lib64/libc.so.6(abort+0x148) [0x7f50daaf9cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f50dc60e204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f50dc6a8830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f50dc6b5c2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f50dc6be813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f50dc73011e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f50dc7180ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f50dc71b0ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f50dc745493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f50da1cbe24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f50da1cc068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f50da1cc10c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f50dc744d55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f50dc716d0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f50dc717005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f50dc71c13b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f50daae4be5]
24: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
search paths: ("/home/john/bin", "/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/X11R6/bin", "/usr/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f78c3ed18d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f78c3ed1849]
4: /lib64/libc.so.6(abort+0x148) [0x7f78c3ed2cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f78c59e7204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f78c5a81830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f78c5a8ec2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f78c5a97813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f78c5b0911e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f78c5af10ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f78c5af40ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f78c5b1e493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f78c35a4e24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f78c35a5068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f78c35a510c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f78c5b1dd55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f78c5aefd0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f78c5af0005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f78c5af513b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f78c3ebdbe5]
24: akonadiserver() [0x4540c9]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Wed Apr 30, 2014 3:05 am
below is the selftest report:

Akonadi Server Self-Test Report
===============================

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/john/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

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


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

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

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

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

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

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.33-MariaDB for Linux on x86_64 (openSUSE package)


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

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

File content of '/home/john/.local/share/akonadi/db_data/mysql.err':
140430 10:57:04 InnoDB: The InnoDB memory heap is disabled
140430 10:57:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140430 10:57:04 InnoDB: Compressed tables use zlib 1.2.8
140430 10:57:04 InnoDB: Using Linux native AIO
140430 10:57:04 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
140430 10:57:06 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
InnoDB: Warning: Linux Native AIO disabled because os_aio_linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf
140430 10:57:06 InnoDB: Initializing buffer pool, size = 80.0M
140430 10:57:06 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.
140430 10:57:06 InnoDB: Retrying to lock the first data file
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
140430 10:58:47 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140430 10:58:47 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
140430 10:58:47 InnoDB: Could not open or create data files.
140430 10:58:47 InnoDB: If you tried to add new data files, and it failed here,
140430 10:58:47 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140430 10:58:47 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140430 10:58:47 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140430 10:58:47 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140430 10:58:47 InnoDB: remove old data files which contain your precious data!
140430 10:58:47 [ERROR] Plugin 'InnoDB' init function returned error.
140430 10:58:47 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140430 10:58:47 [ERROR] mysqld: Can't lock aria control file '/home/john/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
140430 10:59:18 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/john/.local/share/akonadi/db_data/aria_log_control'
140430 10:59:18 [ERROR] Plugin 'Aria' init function returned error.
140430 10:59:18 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
140430 10:59:18 [ERROR] Unknown/unsupported storage engine: innodb
140430 10:59:18 [ERROR] Aborting

140430 10:59:18 [Note] /usr/sbin/mysqld: Shutdown complete



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

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

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

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[client]
default-character-set=utf8


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/john/.local/share/akonadi/mysql.conf'>/home/john/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/john/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

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

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[client]
default-character-set=utf8


Test 9: SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.11.0


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
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13: SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14: SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

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/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
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/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/john/.local/share/akonadi/akonadiserver.error'>/home/john/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/john/.local/share/akonadi/akonadiserver.error':
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7f0940c528d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f0940c52849]
4: /lib64/libc.so.6(abort+0x148) [0x7f0940c53cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f0942768204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f0942802830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f094280fc2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f0942818813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f094288a11e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f09428720ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f09428750ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f094289f493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7f0940325e24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7f0940326068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f094032610c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f094289ed55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f0942870d0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f0942871005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f094287613b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0940c3ebe5]
24: akonadiserver() [0x4540c9]
]
"


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/john/.local/share/akonadi/akonadiserver.error.old'>/home/john/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/john/.local/share/akonadi/akonadiserver.error.old':
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x459f57]
1: akonadiserver() [0x45a1b2]
2: /lib64/libc.so.6(+0x358d0) [0x7ff39d3088d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7ff39d308849]
4: /lib64/libc.so.6(abort+0x148) [0x7ff39d309cd8]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7ff39ee1e204]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45c0ad]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7ff39eeb8830]
8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7ff39eec5c2d]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7ff39eece813]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x5da) [0x45ee1a]
11: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7ff39ef4011e]
12: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7ff39ef280ad]
13: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7ff39ef2b0ff]
14: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7ff39ef55493]
15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x264) [0x7ff39c9dbe24]
16: /usr/lib64/libglib-2.0.so.0(+0x4c068) [0x7ff39c9dc068]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7ff39c9dc10c]
18: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7ff39ef54d55]
19: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7ff39ef26d0f]
20: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7ff39ef27005]
21: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7ff39ef2c13b]
22: akonadiserver(main+0x1bf) [0x453a6f]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff39d2f4be5]
24: akonadiserver() [0x4540c9]
]
"


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

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

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

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.


wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Wed Apr 30, 2014 10:25 am
But that's _not_ exactly the same... ;)

joshaughnessy wrote:below is the selftest report:

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

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

File content of '/home/john/.local/share/akonadi/db_data/mysql.err':
140430 10:57:04 InnoDB: The InnoDB memory heap is disabled
140430 10:57:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140430 10:57:04 InnoDB: Compressed tables use zlib 1.2.8
140430 10:57:04 InnoDB: Using Linux native AIO
140430 10:57:04 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
140430 10:57:06 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
InnoDB: Warning: Linux Native AIO disabled because os_aio_linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf
140430 10:57:06 InnoDB: Initializing buffer pool, size = 80.0M
140430 10:57:06 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.
140430 10:57:06 InnoDB: Retrying to lock the first data file
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
140430 10:58:47 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140430 10:58:47 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
140430 10:58:47 InnoDB: Could not open or create data files.
140430 10:58:47 InnoDB: If you tried to add new data files, and it failed here,
140430 10:58:47 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140430 10:58:47 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140430 10:58:47 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140430 10:58:47 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140430 10:58:47 InnoDB: remove old data files which contain your precious data!
140430 10:58:47 [ERROR] Plugin 'InnoDB' init function returned error.
140430 10:58:47 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140430 10:58:47 [ERROR] mysqld: Can't lock aria control file '/home/john/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
140430 10:59:18 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/john/.local/share/akonadi/db_data/aria_log_control'
140430 10:59:18 [ERROR] Plugin 'Aria' init function returned error.
140430 10:59:18 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
140430 10:59:18 [ERROR] Unknown/unsupported storage engine: innodb
140430 10:59:18 [ERROR] Aborting

140430 10:59:18 [Note] /usr/sbin/mysqld: Shutdown complete
...
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/john/.local/share/akonadi/akonadiserver.error'>/home/john/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/john/.local/share/akonadi/akonadiserver.error':
"
Sql error: Duplicate entry '47231-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.

You seem to have a problem with mysql or the akonadi database.

Can you try to create a new user and test if it works there?

Try to kill all mysql and akonadi processes and rename the folder '/home/john/.local/share/akonadi' so it isn't found.
Can you start Akonadi then (as user, not root) ?
wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Wed Apr 30, 2014 10:30 am
PS:
joshaughnessy wrote:I had to reinstall opensuse but left my home directory hoping my mails would all remain.

So I suppose you used mysql on your old installation, right?
A fresh openSUSE install would install mariadb by default.

I guess mariadb 5.5 cannot read mysql 5.6's database, causing the problem.
Removing the akonadi database as suggested should fix that (the database is only a cache anyway), or you could also try to install "mysql-community-server" instead of "mariadb".
Probably Akonadi works again then _without_ wiping out the akonadi database.
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Tue May 13, 2014 2:11 am
wolfi323 wrote:PS:
joshaughnessy wrote:I had to reinstall opensuse but left my home directory hoping my mails would all remain.

So I suppose you used mysql on your old installation, right?
A fresh openSUSE install would install mariadb by default.

I guess mariadb 5.5 cannot read mysql 5.6's database, causing the problem.
Removing the akonadi database as suggested should fix that (the database is only a cache anyway), or you could also try to install "mysql-community-server" instead of "mariadb".
Probably Akonadi works again then _without_ wiping out the akonadi database.

In the end I deinstalled everything and cleaned up totally, then started from scratch..... I guess it is the change to mariadb that messed things up. I was trying to avoid a total reinstall as I run 7 different imap accounts with different rules on each.. :|
wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Tue May 13, 2014 10:59 am
joshaughnessy wrote:In the end I deinstalled everything and cleaned up totally, then started from scratch..... I guess it is the change to mariadb that messed things up. I was trying to avoid a total reinstall as I run 7 different imap accounts with different rules on each.. :|

Well, have you tried to install mysql-community-server or remove the akonadi database as I suggested?
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Tue May 13, 2014 5:51 pm
wolfi323 wrote:
joshaughnessy wrote:In the end I deinstalled everything and cleaned up totally, then started from scratch..... I guess it is the change to mariadb that messed things up. I was trying to avoid a total reinstall as I run 7 different imap accounts with different rules on each.. :|

Well, have you tried to install mysql-community-server or remove the akonadi database as I suggested?

Nope, I had already reinstalled everything fresh again before I saw your mail. It all works well now so I don't want to delve any further into it, not having the time either. Thanks for the advice though. If I had seen it on time, it might have saved me a couple of hours of writing in IMAP accounts, identities, filter rules etc.
Any time I try to run akonadiconsole it still throws up stuff and errors about mySQL. but if I use kmail, kontact or anything else it all does what it's supposed to: sending/receiving mail, syncing folders, accounts etc and running my organiser
wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Tue May 13, 2014 6:18 pm
joshaughnessy wrote:Any time I try to run akonadiconsole it still throws up stuff and errors about mySQL. but if I use kmail, kontact or anything else it all does what it's supposed to: sending/receiving mail, syncing folders, accounts etc and running my organiser

Hm, apparently Akonadi works, so I don't understand why akonadiconsole would give an error about mySQL. It just connects to Akonadi AFAIK.

What is the exact wording of the error(s)?

And again, you cannot run akonadiconsole as root. You did run it as user, right?
joshaughnessy
Registered Member
Posts
33
Karma
0
OS

Re: Kmail, PIM Akonadi won't start

Wed May 14, 2014 8:32 am
wolfi323 wrote:
joshaughnessy wrote:Any time I try to run akonadiconsole it still throws up stuff and errors about mySQL. but if I use kmail, kontact or anything else it all does what it's supposed to: sending/receiving mail, syncing folders, accounts etc and running my organiser

Hm, apparently Akonadi works, so I don't understand why akonadiconsole would give an error about mySQL. It just connects to Akonadi AFAIK.

What is the exact wording of the error(s)?

And again, you cannot run akonadiconsole as root. You did run it as user, right?


I don't know anymore, but I may have run it as root. I just tried it now and it's fine :)
wolfi323
Registered Member
Posts
1129
Karma
11
OS

Re: Kmail, PIM Akonadi won't start

Wed May 14, 2014 6:30 pm
joshaughnessy wrote:I don't know anymore, but I may have run it as root. I just tried it now and it's fine :)

Good. :)

You might want to mark this thread as solved then, I suppose. ;)
joshaughnessy
Registered Member
Posts
33
Karma
0
OS
wolfi323 wrote:
joshaughnessy wrote:I don't know anymore, but I may have run it as root. I just tried it now and it's fine :)

Good. :)

You might want to mark this thread as solved then, I suppose. ;)

just one thing I would like to say:
I'm a sixty year old dinosaur who recently discovered KDE.... I love it and I hate it at the same time, but lately...... it has gotten MUCH better! Kmail and related PIM apps are now functioning stable with great SPEED
KDE beats MAC OS and MSWindows hands down with some features..
the only problem is, that up until now, it seemed like Linux desktops were only for developers and IT people. I see this slowly moving towards real GUI bliss where the ignorant user can actually benefit from all the effort of past volunteers and developers put together. QT and KDE are definitely forces that will continue into and be part of our future...
I remember, BASIC, MINIX and MSDOS.... we've come a long way....
thanks for your help Wolf323
petrosalcibiades
Registered Member
Posts
1
Karma
0

Re: Kmail, PIM Akonadi won't start

Fri Nov 07, 2014 8:18 am
Same problem 'server protocol is too old'. But I am running the latest testing version of Debian. It was an upgrade that has caused this problem. Difficulty is that now everything is inaccessible, calendar, email, kjots....

Any ideas?

P


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]