LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (https://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   kontact + akonadi problems (https://www.linuxquestions.org/questions/linux-desktop-74/kontact-akonadi-problems-4175482788/)

michael.schmid 10-30-2013 10:57 AM
kontact + akonadi problems
 
I recently restored my entire home directory (everything under /home/user) from a backup from a few days ago. I then fired up kontact, let it check for new mails - everything worked. I even was able to send new mail. The only thing out of order that I noticed was that kontact complained about non existing "Sent" folders for my individual accounts, and that all sent mails would be stored in the default folder (which was fine with me). But: all mails were there, inbox intact and all.

Today, after a reboot, kontact does not start up anymore. It now displays the infamous "The Akonadi personal information management service is not operational" screen. I hope somebody is able to help me with this, what follows is the error report (I left all tests labeled as "SUCCESS" out):

Code:
Akonadi Server Self-Test Report
===============================

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

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

File content of '/home/user/.local/share/akonadi/db_data/mysql.err':
131030  9:36:14  InnoDB: Initializing buffer pool, size = 80.0M
131030  9:36:14  InnoDB: Completed initialization of buffer pool
131030  9:36:14  InnoDB: Error: page 7 log sequence number 0 226537929
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:14  InnoDB: Error: page 1 log sequence number 0 81874805
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:14  InnoDB: Error: page 3 log sequence number 0 81874805
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:14  InnoDB: Error: page 4 log sequence number 0 339848172
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:14  InnoDB: Error: page 11 log sequence number 0 226543252
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:14  InnoDB: Error: page 8 log sequence number 0 226543272
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 10 log sequence number 0 226543262
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 9 log sequence number 0 226543267
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 12 log sequence number 0 226543247
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 46 log sequence number 0 340947899
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 47 log sequence number 0 340922051
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 48 log sequence number 0 340774088
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131030  9:36:15  InnoDB: Error: page 49 log sequence number 0 340919556
InnoDB: is in the future! Current system log sequence number 0 3473975.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/storage/innobase/include/page0page.ic line 591
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:36:15 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=256
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 567890 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x24) [0x82db34]
/usr/sbin/mysqld(handle_fatal_signal+0x361) [0x686771]
/lib64/libpthread.so.0(+0x10bf0) [0x7f788f7c5bf0]
/lib64/libc.so.6(gsignal+0x35) [0x7f788e1edb65]
/lib64/libc.so.6(abort+0x17b) [0x7f788e1eefdb]
/usr/sbin/mysqld(page_cur_search_with_match+0x731) [0x779e01]
/usr/sbin/mysqld(btr_cur_search_to_nth_level+0x63f) [0x715d5f]
/usr/sbin/mysqld(btr_pcur_open_on_user_rec+0x60) [0x7cb5f0]
/usr/sbin/mysqld(dict_load_foreigns+0x1fe) [0x73804e]
/usr/sbin/mysqld(dict_load_table+0x102b) [0x73a9fb]
/usr/sbin/mysqld(dict_create_or_check_foreign_constraint_tables+0x3a4) [0x7cedd4]
/usr/sbin/mysqld(innobase_start_or_create_for_mysql+0x12d8) [0x7a80e8]
/usr/sbin/mysqld() [0x70b9c1]
/usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x681671]
/usr/sbin/mysqld() [0x6f26e1]
/usr/sbin/mysqld(plugin_init(int*, char**, int)+0x4d3) [0x6f5be3]
/usr/sbin/mysqld() [0x5bd51a]
/usr/sbin/mysqld(main+0x215) [0x50df25]
/lib64/libc.so.6(__libc_start_main+0xed) [0x7f788e1da60d]
/usr/sbin/mysqld() [0x51aa19]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


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

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


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

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

Test 13:  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 14:  ERROR
--------

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

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

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

Test 15:  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/user/.local/share/akonadi/akonadiserver.error'>/home/user/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/user/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/user/.local/share/akonadi/mysql.conf", "--datadir=/home/user/.local/share/akonadi/db_data/", "--socket=/home/user/.local/share/akonadi/socket-myhost/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x34) [0x4587d4]
1: akonadiserver() [0x458c01]
2: /lib64/libc.so.6(+0x37be0) [0x7f311ca9bbe0]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f311ca9bb65]
4: /lib64/libc.so.6(abort+0x17b) [0x7f311ca9cfdb]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f311e56d7b4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x45aabb]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7f311e6088df]
8: /usr/lib64/qt4/libQtCore.so.4(+0x11dde2) [0x7f311e613de2]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f311e61cc99]
10: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x179a) [0x4c70fa]
11: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xc7) [0x45b797]
12: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0xa5) [0x45d545]
13: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x47) [0x45eb67]
14: akonadiserver(main+0x10a) [0x4522ba]
15: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f311ca8860d]
16: akonadiserver() [0x452a91]
]
"


Test 16:  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/user/.local/share/akonadi/akonadiserver.error.old'>/home/user/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/user/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/user/.local/share/akonadi/mysql.conf", "--datadir=/home/user/.local/share/akonadi/db_data/", "--socket=/home/user/.local/share/akonadi/socket-myhost/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x34) [0x4587d4]
1: akonadiserver() [0x458c01]
2: /lib64/libc.so.6(+0x37be0) [0x7f3909137be0]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f3909137b65]
4: /lib64/libc.so.6(abort+0x17b) [0x7f3909138fdb]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f390ac097b4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x45aabb]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7f390aca48df]
8: /usr/lib64/qt4/libQtCore.so.4(+0x11dde2) [0x7f390acafde2]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f390acb8c99]
10: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x179a) [0x4c70fa]
11: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xc7) [0x45b797]
12: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0xa5) [0x45d545]
13: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x47) [0x45eb67]
14: akonadiserver(main+0x10a) [0x4522ba]
15: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f390912460d]
16: akonadiserver() [0x452a91]
]
"

ichrispa 04-10-2014 06:02 AM
Hello michael.schmid,

try letting akonadi rebuild its database. There is propably a database error due to the fact that the database was created by a much older version of akonadi.

To that end, first klose any instances of kmail/kontact. Then open a console and type

Code:
akonadictl stop
If you enter it repeatadly, at some point you are going to get the answer that "akonadiserver is not running". After that, delete the database folder.

Code:
rm -rf $HOME/.local/share/akonadi*
Note that your settings are not going to be affected, they are stored in $HOME/.config/apps/akonadi and $HOME/.kde4/share/akonadi, you are only deleting the database cache. After that, restart akonadi.

Code:
akonadictl start
Akonadi will detect the absence of its database and rebuild it.

You might also want to run akonadiconsole or akonaditray, both will allow you to configure your database backend.

Kind regards,

ichrispa


All times are GMT -5. The time now is 07:01 PM.