Results 1 to 4 of 4

Thread: akonadi crashed and no longer starting

  1. #1

    Default akonadi crashed and no longer starting

    My laptop froze yesterday and after that I'm unable to use kontact as akonadi server is not starting. Please check logs below. How can I recover from this situation?

    Opensuse 12.3 x86_64
    KDE 4.10.3 from KDE:Release repo

    MySQL Log

    Code:
    130513 15:49:50 InnoDB: The InnoDB memory heap is disabled130513 15:49:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    130513 15:49:50 InnoDB: Compressed tables use zlib 1.2.7
    130513 15:49:50 InnoDB: Initializing buffer pool, size = 80.0M
    130513 15:49:50 InnoDB: Completed initialization of buffer pool
    130513 15:49:50 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    130513 15:49:50  InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    130513 15:49:50  InnoDB: Assertion failure in thread 139698913793856 in file fsp0fsp.c line 2935
    InnoDB: Failing assertion: space != 0
    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.5/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    130513 15:49:50 [ERROR] 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.
    
    
    To report this bug, see http://kb.askmonty.org/en/reporting-bugs
    
    
    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.
    
    
    Server version: 5.5.29-MariaDB
    key_buffer_size=134217728
    read_buffer_size=131072
    max_used_connections=0
    max_threads=258
    thread_count=0
    It is possible that mysqld could use up to 
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 696096 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    
    
    Thread pointer: 0x0x0
    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 = 0x0 thread_stack 0x48000
    ??:0(??)[0xa55426]
    ??:0(??)[0x6d9f05]
    ??:0(??)[0x7f0e318751f0]
    ??:0(??)[0x7f0e3046c3d5]
    ??:0(??)[0x7f0e3046d858]
    ??:0(??)[0x8d84e4]
    ??:0(??)[0x8d8914]
    ??:0(??)[0x862e2f]
    ??:0(??)[0x8a103c]
    ??:0(??)[0x8a1da3]
    ??:0(??)[0x83ca70]
    ??:0(??)[0x7fd120]
    ??:0(??)[0x6dc291]
    ??:0(??)[0x5ca118]
    ??:0(??)[0x5ce3b5]
    ??:0(??)[0x54d4ec]
    ??:0(??)[0x54e137]
    ??:0(??)[0x7f0e30458a15]
    ??:0(??)[0x544569]
    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.
    Akonadi log
    Code:
    Database process exited unexpectedly during initial connection! 
    executable: "/usr/sbin/mysqld" 
    arguments: ("--defaults-file=/home/ruchir/.local/share/akonadi/mysql.conf", "--datadir=/home/ruchir/.local/share/akonadi/db_data/", "--socket=/home/ruchir/.local/share/akonadi/socket-linux-t2ce.site/mysql.socket") 
    stdout: "" 
    stderr: "" 
    exit code: 1 
    process error: "Unknown error" 
    "[
    0: akonadiserver(_Z11akBacktracev+0x34) [0x45a3c4]
    1: akonadiserver() [0x45a701]
    2: /lib64/libc.so.6(+0x35450) [0x7fe11b100450]
    3: /lib64/libc.so.6(gsignal+0x35) [0x7fe11b1003d5]
    4: /lib64/libc.so.6(abort+0x148) [0x7fe11b101858]
    5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7fe11cbd7c54]
    6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x45c46b]
    7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4) [0x7fe11cc712e4]
    8: /usr/lib64/libQtCore.so.4(+0x11bf8f) [0x7fe11cc7bf8f]
    9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7fe11cc8458b]
    10: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x173a) [0x4d46ea]
    11: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xc7) [0x45d127]
    12: akonadiserver(_ZN7Akonadi13AkonadiServerC1EP7QObject+0xac) [0x45e05c]
    13: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x47) [0x45f747]
    14: akonadiserver(main+0x10a) [0x4542ba]
    15: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fe11b0eca15]
    16: akonadiserver() [0x454a91]
    ]
    "

  2. #2
    Join Date
    Sep 2012
    Location
    Maryland, US
    Posts
    623

    Default Re: akonadi crashed and no longer starting

    Have you reported the bug?
    Kernel: 4.12.14-lp150.12.7-default x86_64 bits:
    64 Desktop: Gnome 3.26.2
    Distro: openSUSE Leap 15.0

  3. #3

    Default Re: akonadi crashed and no longer starting

    Quote Originally Posted by Ruchir View Post
    My laptop froze yesterday and after that I'm unable to use kontact as akonadi server is not starting. Please check logs below. How can I recover from this situation?
    Your akonadi database seems to be corrupted.
    Please delete the folder ~/.local/share/akonadi/db_data/ (well, better just rename it so you could restore it again if necessary).

  4. #4

    Default Re: akonadi crashed and no longer starting

    Quote Originally Posted by wolfi323 View Post
    Your akonadi database seems to be corrupted.
    Please delete the folder ~/.local/share/akonadi/db_data/ (well, better just rename it so you could restore it again if necessary).
    Thanks, that helped starting the akonadi server again. Kontact is usable again.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •