Results 1 to 2 of 2

Thread: Akonadi problems

  1. #1
    Join Date
    Nov 2009
    Location
    West Midlands
    Posts
    71

    Default Akonadi problems

    I'm in a bit of a mess right now with Kmail and Akonadi.

    I was trying to investigate why Kmail can't seem to handle a simple thing like send an email to a distribution/group list and came across several answers regarding Akonadi and AppArmour. I got nowhere fast with AppArmour so I started to dable with Akonadi.

    Trying a few things, I have managed to make things worse now. When ever I try to start Kmail, I get the Akonadi server waitbar poop up, then eventually the Akonadi self test gives errors and I have to quit it. This also quits Kmail. So now I have no access to my emails.

    I do not recall seeing the Akonadi server waitbar up previously when I start up Kmail.

    Desperately seeking help

    openSuse 11.3, KDE 4.5.5

    Below is the error report from the Akonadi self-test.

    Code:
    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/vas/.config/akonadi/akonadiserverrc':
    [%General]
    Driver=QMYSQL
    SizeThreshold=4096
    ExternalPayload=false
    
    [QMYSQL]
    Name=akonadi
    Host=
    User=
    Password=
    Options="UNIX_SOCKET=/home/vas/.local/share/akonadi/db_misc/mysql.socket"
    ServerPath=/usr/sbin/mysqld
    StartServer=true
    
    [Debug]
    Tracer=null
    
    [QPSQL]
    Name=akonadi
    Host=
    User=
    Password=
    Port=5432
    
    
    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.1.44b-MariaDB for suse-linux-gnu on i686 (SUSE MariaDB RPM)
    
    
    Test 5:  SUCCESS
    --------
    
    No current MySQL error log found.
    Details: The MySQL server did not report any errors during this startup. The log can be found in '/home/vas/.local/share/akonadi/db_data/mysql.err'.
    
    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]
    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,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
    
    # 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=utf8
    collation_server=utf8_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
    
    # Do not drop the connection to the DB after 8 hours of inactivity
    wait_timeout=1296000
    
    [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:  ERROR
    --------
    
    MySQL server configuration not found or not readable.
    Details: The MySQL server configuration was not found or is not readable.
    
    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.4.1
    
    
    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:/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':
    birthdaysresource.desktop
    contactsresource.desktop
    icalresource.desktop
    imapresource.desktop
    kabcresource.desktop
    kcalresource.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:/etc/opt/kde3/share:/opt/kde3/share'
    
    Test 16:  SUCCESS
    --------
    
    No current Akonadi server error log found.
    Details: The Akonadi server did not report any errors during its current startup.
    
    Test 17:  SUCCESS
    --------
    
    No previous Akonadi server error log found.
    Details: The Akonadi server did not report any errors during its previous startup.
    
    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.
    Vas
    openSuse 42.2

  2. #2
    Join Date
    Nov 2009
    Location
    West Midlands
    Posts
    71

    Default Re: Akonadi problems

    An update:
    Incidentally, there is no GUI for the Akonadi server control in System settings, but if I issue the following command in Konsole is shows up.

    Code:
    kcmshell4 kcm_akonadi
    But I also get this error when I quit it.

    Code:
    kcmshell(11751)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name"
    Vas
    openSuse 42.2

Tags for this Thread

Posting Permissions

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