Results 1 to 3 of 3

Thread: KOrganizer not working/Akonadi not working correctly

  1. #1

    Default KOrganizer not working/Akonadi not working correctly

    Dear Community,

    I have difficulties getting KOrganizer to work. Can you help me with this? I deleted the tests that passed.


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


    --------

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

    File content of '/home/Benjamin/.local/share/akonadi/db_data/mysql.err':
    2014-09-26 19:49:26 7fb487bbe740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
    140926 19:49:26 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    140926 19:49:26 [Note] InnoDB: The InnoDB memory heap is disabled
    140926 19:49:26 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    140926 19:49:26 [Note] InnoDB: Compressed tables use zlib 1.2.8
    140926 19:49:26 [Note] InnoDB: Using Linux native AIO
    140926 19:49:26 [Note] InnoDB: Using CPU crc32 instructions
    140926 19:49:26 [Note] InnoDB: Initializing buffer pool, size = 80.0M
    140926 19:49:26 [Note] InnoDB: Completed initialization of buffer pool
    140926 19:49:26 [Note] InnoDB: Highest supported file format is Barracuda.
    140926 19:49:26 [Note] InnoDB: The log sequence numbers 1734075 and 1734075 in ibdata files do not match the log sequence number 1734105 in the ib_logfiles!
    140926 19:49:26 [Note] InnoDB: Database was not shutdown normally!
    140926 19:49:26 [Note] InnoDB: Starting crash recovery.
    140926 19:49:26 [Note] InnoDB: Reading tablespace information from the .ibd files...
    140926 19:49:26 [Note] InnoDB: Restoring possible half-written data pages
    140926 19:49:26 [Note] InnoDB: from the doublewrite buffer...
    140926 19:49:26 [ERROR] mysqld got signal 11 ;
    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: 10.0.13-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 = 697798 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
    /usr/sbin/mysqld(my_print_stacktrace+0x29)[0xb7af09]
    /usr/sbin/mysqld(handle_fatal_signal+0x515)[0x72b395]
    /lib64/libpthread.so.0(+0xf9f0)[0x7fb48716f9f0]
    /usr/sbin/mysqld[0x9dd980]
    /usr/sbin/mysqld[0x9dee5a]
    /usr/sbin/mysqld[0x94582b]
    /usr/sbin/mysqld[0x88714e]
    /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5d)[0x72d22d]
    /usr/sbin/mysqld[0x5f61d6]
    /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x541)[0x5f7681]
    /usr/sbin/mysqld[0x5614c0]
    /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x51e)[0x56543e]
    /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fb485f61be5]
    /usr/sbin/mysqld[0x55a429]
    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 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:/etc/opt/kde3/share:/opt/kde3/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
    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
    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:/etc/opt/kde3/share:/opt/kde3/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/Benjamin/.local/share/akonadi/akonadiserver.error'>/home/Benjamin/.local/share/akonadi/akonadiserver.error</a>.

    File content of '/home/Benjamin/.local/share/akonadi/akonadiserver.error':
    Database process exited unexpectedly during initial connection!
    executable: "/usr/sbin/mysqld"
    arguments: ("--defaults-file=/home/Benjamin/.local/share/akonadi/mysql.conf", "--datadir=/home/Benjamin/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-Benjamin.SDhaZY/mysql.socket")
    stdout: ""
    stderr: ""
    exit code: 1
    process error: "Unknown error"
    "[
    0: akonadiserver(_Z11akBacktracev+0x38) [0x4584d8]
    1: akonadiserver() [0x458762]
    2: /lib64/libc.so.6(+0x35550) [0x7fc1e57dd550]
    3: /lib64/libc.so.6(gsignal+0x39) [0x7fc1e57dd4c9]
    4: /lib64/libc.so.6(abort+0x148) [0x7fc1e57de958]
    5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7fc1e7317204]
    6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45a96d]
    7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fc1e73b1830]
    8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7fc1e73bec2d]
    9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7fc1e73c7813]
    10: akonadiserver(_ZN6QDebugD1Ev+0x30) [0x450fd0]
    11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1c29) [0x4d81c9]
    12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xc7) [0x45b507]
    13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45d3c2]
    14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7fc1e743911e]
    15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7fc1e74210ad]
    16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7fc1e74240ff]
    17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7fc1e744e493]
    18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7fc1e4eab316]
    19: /usr/lib64/libglib-2.0.so.0(+0x4b668) [0x7fc1e4eab668]
    20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fc1e4eab70c]
    21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7fc1e744dd55]
    22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7fc1e741fd0f]
    23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7fc1e7420005]
    24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7fc1e742513b]
    25: akonadiserver(main+0x1bf) [0x45074f]
    26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fc1e57c9be5]
    27: akonadiserver() [0x450df9]
    ]
    "


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

    File content of '/home/Benjamin/.local/share/akonadi/akonadiserver.error.old':
    Database process exited unexpectedly during initial connection!
    executable: "/usr/sbin/mysqld"
    arguments: ("--defaults-file=/home/Benjamin/.local/share/akonadi/mysql.conf", "--datadir=/home/Benjamin/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-Benjamin.SDhaZY/mysql.socket")
    stdout: ""
    stderr: ""
    exit code: 1
    process error: "Unknown error"
    "[
    0: akonadiserver(_Z11akBacktracev+0x38) [0x4584d8]
    1: akonadiserver() [0x458762]
    2: /lib64/libc.so.6(+0x35550) [0x7f14c415d550]
    3: /lib64/libc.so.6(gsignal+0x39) [0x7f14c415d4c9]
    4: /lib64/libc.so.6(abort+0x148) [0x7f14c415e958]
    5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f14c5c97204]
    6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45a96d]
    7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f14c5d31830]
    8: /usr/lib64/libQtCore.so.4(+0x11ec2d) [0x7f14c5d3ec2d]
    9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f14c5d47813]
    10: akonadiserver(_ZN6QDebugD1Ev+0x30) [0x450fd0]
    11: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1c29) [0x4d81c9]
    12: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xc7) [0x45b507]
    13: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x92) [0x45d3c2]
    14: /usr/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f14c5db911e]
    15: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f14c5da10ad]
    16: /usr/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f14c5da40ff]
    17: /usr/lib64/libQtCore.so.4(+0x1ae493) [0x7f14c5dce493]
    18: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f14c382b316]
    19: /usr/lib64/libglib-2.0.so.0(+0x4b668) [0x7f14c382b668]
    20: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f14c382b70c]
    21: /usr/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f14c5dcdd55]
    22: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f14c5d9fd0f]
    23: /usr/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f14c5da0005]
    24: /usr/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f14c5da513b]
    25: akonadiserver(main+0x1bf) [0x45074f]
    26: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f14c4149be5]
    27: akonadiserver() [0x450df9]
    ]
    "

  2. #2

    Default AW: KOrganizer not working/Akonadi not working correctly

    Quote Originally Posted by gargamel98 View Post
    MySQL server log contains errors.
    Details: The MySQL server error log file &apos;<a href='/home/Benjamin/.local/share/akonadi/db_data/mysql.err'>/home/Benjamin/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

    File content of '/home/Benjamin/.local/share/akonadi/db_data/mysql.err':
    2014-09-26 19:49:26 7fb487bbe740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
    140926 19:49:26 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    140926 19:49:26 [Note] InnoDB: The InnoDB memory heap is disabled
    140926 19:49:26 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    140926 19:49:26 [Note] InnoDB: Compressed tables use zlib 1.2.8
    140926 19:49:26 [Note] InnoDB: Using Linux native AIO
    140926 19:49:26 [Note] InnoDB: Using CPU crc32 instructions
    140926 19:49:26 [Note] InnoDB: Initializing buffer pool, size = 80.0M
    140926 19:49:26 [Note] InnoDB: Completed initialization of buffer pool
    140926 19:49:26 [Note] InnoDB: Highest supported file format is Barracuda.
    140926 19:49:26 [Note] InnoDB: The log sequence numbers 1734075 and 1734075 in ibdata files do not match the log sequence number 1734105 in the ib_logfiles!
    140926 19:49:26 [Note] InnoDB: Database was not shutdown normally!
    140926 19:49:26 [Note] InnoDB: Starting crash recovery.
    140926 19:49:26 [Note] InnoDB: Reading tablespace information from the .ibd files...
    140926 19:49:26 [Note] InnoDB: Restoring possible half-written data pages
    140926 19:49:26 [Note] InnoDB: from the doublewrite buffer...
    140926 19:49:26 [ERROR] mysqld got signal 11 ;
    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.
    MySQL does not start because there's a problem with the database files that cannot be recovered apparently.

    Server version: 10.0.13-MariaDB
    Why are you using 10.0.13?
    What openSUSE version is this about?
    13.1 ships with 5.5.
    If you upgraded MariaDB recently it might be the source of your problem.

    Anyway, try to remove the Akonadi database, it should start then and KOrganizer work again.
    It is located in ~/.local/share/akonadi/ so remove or (better) rename that folder and try to start it again.

    The database is only a cache, so you should not loose any data when doing this. But some things can get confused because the collection ids may change (e.g. KMail filters probably will move the mails into the wrong folders, the sent-mail and trash folders might be set wrong, and so on), so you might have to reconfigure some things..

  3. #3

    Default Re: KOrganizer not working/Akonadi not working correctly

    Your advice worked. Thx.

Posting Permissions

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