Announcement

Collapse
No announcement yet.

Akonadi disaster

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Akonadi disaster

    Kubuntu 9.10/64 kept current

    ==============================
    I am pre-pending this for ease of reading. I did have to do a complete re-install to solve the Akonadi problem. Now I just have to finish all the re-configuring and loading of all my software.
    =======================================

    I was notified of the KDE 4.4 updates and accepted them all. Now, as mentioned in an earlier post, I am without KMail. That is a disaster. It is all due to Akonadi. Here is the error report when I try to start Akonadi:

    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/dick/.config/akonadi/akonadiserverrc':
    [%General]
    Driver=QMYSQL
    SizeThreshold=4096
    ExternalPayload=false

    [QMYSQL]
    Name=akonadi
    User=
    Password=
    Options="UNIX_SOCKET=/home/dick/.local/share/akonadi/db_misc/mysql.socket"
    ServerPath=/usr/sbin/mysqld-akonadi
    StartServer=true
    Host=

    [Debug]
    Tracer=null


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

    MySQL server found.
    Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'.
    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 locations varies depending on the distribution.

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

    MySQL server is executable.
    Details: MySQL server found: /usr/sbin/mysqld-akonadi Ver 5.1.37-1ubuntu5 for debian-linux-gnu on x86_64 ((Ubuntu))


    Test 4: ERROR
    --------

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

    File content of '/home/dick/.local/share/akonadi/db_data/mysql.err':
    100228 10:55:07 [Note] Plugin 'FEDERATED' is disabled.
    InnoDB: No valid checkpoint found.
    InnoDB: If this error appears when you are creating an InnoDB database,
    InnoDB: the problem may be that during an earlier attempt you managed
    InnoDB: to create the InnoDB data files, but log file creation failed.
    InnoDB: If that is the case, please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.1/...ng-innodb.html
    100228 10:55:07 [ERROR] Plugin 'InnoDB' init function returned error.
    100228 10:55:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    100228 10:55:07 [ERROR] Unknown/unsupported table type: innodb
    100228 10:55:07 [ERROR] Aborting

    100228 10:55:07 [Warning] Forcing shutdown of 1 plugins
    100228 10:55:07 [Note] /usr/sbin/mysqld-akonadi: Shutdown complete



    Test 5: 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]
    skip_grant_tables
    skip_networking

    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    #sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,
    no_auto_value_on_zero,no_engine_substitution,no_ze ro_date,no_zero_in_date,only_full_group_by,pipes_a s_concat
    #sql_mode=strict_trans_tables

    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # case-insensitive table names, avoids trouble on windows
    lower_case_table_names=1
    character_set_server=latin1
    collation_server=latin1_general_ci
    table_cache=200
    thread_cache_size=3
    log_bin=mysql-bin
    expire_logs_days=3
    #sync_bin_log=0
    # error log file name, relative to datadir
    log_error=mysql.err
    log_warnings=2
    # 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
    # maximum blob size
    max_allowed_packet=32M
    max_connections=256
    # makes sense when having the same query multiple times
    # makes no sense with prepared statements and/or transactions
    query_cache_type=0
    query_cache_size=0

    innodb_file_per_table=1
    innodb_log_buffer_size=1M
    innodb_additional_mem_pool_size=1M
    # messure database size and adjust
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    innodb_buffer_pool_size=80M
    # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    innodb_log_file_size=64M
    innodb_flush_log_at_trx_commit=2



    Test 6: SKIP
    --------

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

    Test 7: SUCCESS
    --------

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

    File content of '/home/dick/.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]
    skip_grant_tables
    skip_networking

    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    #sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,
    no_auto_value_on_zero,no_engine_substitution,no_ze ro_date,no_zero_in_date,only_full_group_by,pipes_a s_concat
    sql_mode=strict_trans_tables

    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # case-insensitive table names, avoids trouble on windows
    lower_case_table_names=1
    character_set_server=latin1
    collation_server=latin1_general_ci
    table_cache=200
    thread_cache_size=3
    log_bin=mysql-bin
    expire_logs_days=3
    #sync_bin_log=0
    # error log file name, relative to datadir
    log_error=mysql.err
    log_warnings=2
    # 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
    # maximum blob size
    max_allowed_packet=32M
    max_connections=256
    # makes sense when having the same query multiple times
    # makes no sense with prepared statements and/or transactions
    query_cache_type=0
    query_cache_size=0

    innodb_file_per_table=1
    innodb_log_buffer_size=1M
    innodb_additional_mem_pool_size=1M
    # messure database size and adjust
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    innodb_buffer_pool_size=80M
    # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    innodb_log_file_size=64M
    innodb_flush_log_at_trx_commit=2



    Test 8: 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.3.1


    Test 9: 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 10: 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 11: 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 12: 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 13: 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 /usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share', make sure this includes all paths where Akonadi agents are installed to.

    Directory listing of '/usr/share/akonadi/agents':
    birthdaysresource.desktop
    contactsresource.desktop
    icalresource.desktop
    imapresource.desktop
    kabcresource.desktop
    kcalresource.desktop
    knutresource.desktop
    kolabproxyresource.desktop
    localbookmarksresource.desktop
    maildirresource.desktop
    maildispatcheragent.desktop
    mboxresource.desktop
    microblog.desktop
    mtdummyresource.desktop
    nepomukcalendarfeeder.desktop
    nepomukcontactfeeder.desktop
    nepomuktagresource.desktop
    nntpresource.desktop
    notesresource.desktop
    pop3resource.desktop
    vcarddirresource.desktop
    vcardresource.desktop
    Directory listing of '/usr/share/akonadi/agents':
    birthdaysresource.desktop
    contactsresource.desktop
    icalresource.desktop
    imapresource.desktop
    kabcresource.desktop
    kcalresource.desktop
    knutresource.desktop
    kolabproxyresource.desktop
    localbookmarksresource.desktop
    maildirresource.desktop
    maildispatcheragent.desktop
    mboxresource.desktop
    microblog.desktop
    mtdummyresource.desktop
    nepomukcalendarfeeder.desktop
    nepomukcontactfeeder.desktop
    nepomuktagresource.desktop
    nntpresource.desktop
    notesresource.desktop
    pop3resource.desktop
    vcarddirresource.desktop
    vcardresource.desktop

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

    Test 14: ERROR
    --------

    Current Akonadi server error log found.
    Details: The Akonadi server did report error during startup into <a href='/home/dick/.local/share/akonadi/akonadiserver.error'>/home/dick/.local/share/akonadi/akonadiserver.error</a>.

    File content of '/home/dick/.local/share/akonadi/akonadiserver.error':
    Database process exited unexpectedly during initial connection!
    executable: "/usr/sbin/mysqld-akonadi"
    arguments: ("--defaults-file=/home/dick/.local/share/akonadi//mysql.conf", "--datadir=/home/dick/.local/share/akonadi/db_data/", "--socket=/home/dick/.local/share/akonadi/db_misc/mysql.socket")
    stdout: ""
    stderr: ""
    exit code: 1
    process error: "Unknown error"
    "[
    0: akonadiserver(_Z11akBacktracev+0x39) [0x40b379]
    1: akonadiserver [0x40b8c2]
    2: /lib/libc.so.6 [0x7f4be049d530]
    3: /lib/libc.so.6(gsignal+0x35) [0x7f4be049d4b5]
    4: /lib/libc.so.6(abort+0x180) [0x7f4be04a0f50]
    5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x74) [0x7f4be1668804]
    6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+ 0xa8) [0x40c9e8]
    7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x78) [0x7f4be16f8408]
    8: /usr/lib/libQtCore.so.4 [0x7f4be1709789]
    9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f4be170a989]
    10: akonadiserver(_ZN6QDebugD1Ev+0x4e) [0x406fee]
    11: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer2 5startMysqlDatabaseProcessEv+0x183b) [0x7f4be1ad823b]
    12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer2 0startDatabaseProcessEv+0x2e0) [0x7f4be1adcd10]
    13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC 1EP7QObject+0x76) [0x7f4be1adcfd6]
    14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8 instanceEv+0x4a) [0x7f4be1ade2fa]
    15: akonadiserver(main+0x3b8) [0x406618]
    16: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f4be0488abd]
    17: akonadiserver [0x406169]
    ]
    "


    Test 15: ERROR
    --------

    Previous Akonadi server error log found.
    Details: The Akonadi server did report error during its previous startup into <a href='/home/dick/.local/share/akonadi/akonadiserver.error.old'>/home/dick/.local/share/akonadi/akonadiserver.error.old</a>.

    File content of '/home/dick/.local/share/akonadi/akonadiserver.error.old':
    Database process exited unexpectedly during initial connection!
    executable: "/usr/sbin/mysqld-akonadi"
    arguments: ("--defaults-file=/home/dick/.local/share/akonadi//mysql.conf", "--datadir=/home/dick/.local/share/akonadi/db_data/", "--socket=/home/dick/.local/share/akonadi/db_misc/mysql.socket")
    stdout: ""
    stderr: ""
    exit code: 1
    process error: "Unknown error"
    "[
    0: akonadiserver(_Z11akBacktracev+0x39) [0x40b379]
    1: akonadiserver [0x40b8c2]
    2: /lib/libc.so.6 [0x7f6167785530]
    3: /lib/libc.so.6(gsignal+0x35) [0x7f61677854b5]
    4: /lib/libc.so.6(abort+0x180) [0x7f6167788f50]
    5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x74) [0x7f6168950804]
    6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+ 0xa8) [0x40c9e8]
    7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x78) [0x7f61689e0408]
    8: /usr/lib/libQtCore.so.4 [0x7f61689f1789]
    9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f61689f2989]
    10: akonadiserver(_ZN6QDebugD1Ev+0x4e) [0x406fee]
    11: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer2 5startMysqlDatabaseProcessEv+0x183b) [0x7f6168dc023b]
    12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer2 0startDatabaseProcessEv+0x2e0) [0x7f6168dc4d10]
    13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC 1EP7QObject+0x76) [0x7f6168dc4fd6]
    14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8 instanceEv+0x4a) [0x7f6168dc62fa]
    15: akonadiserver(main+0x3b8) [0x406618]
    16: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f6167770abd]
    17: akonadiserver [0x406169]
    ]
    "


    Test 16: SUCCESS
    --------

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

    Test 17: SUCCESS
    --------

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

    I have read and tried all the posts here, tried the Akonadi recommendations, completed a re-install of MySQL and nothing helps. Do I really have to go back and rebuild Kubuntu from scratch and stop the 4.4 update? There must be a way to fix Akonadi without doing that. Is there an Akonadi developer listening who can shed some light on this issue?
    An old mainframer trying to get modern in his retirement.

    #2
    Re: SOLVED/Akonadi disaster

    Why is this marked as SOLVED? Did you fix the issue?
    KeyboardShortcuts.org | CouponCodeSwap.com

    Comment


      #3
      Re: Akonadi disaster

      Unclear. I've removed the SOLVED from the subject. My previous edit of the post was only to correct 'long lines.'
      Windows no longer obstructs my view.
      Using Kubuntu Linux since March 23, 2007.
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

      Comment


        #4
        Re: Akonadi disaster

        Not sure if this will solve your problem, but worth a try:

        http://kubuntuforums.net/forums/inde...6364#msg226364
        Last edited by undoIT; Jan 25, 2013, 01:57 PM.
        KeyboardShortcuts.org | CouponCodeSwap.com

        Comment

        Working...
        X