Akonadi: no agents found
Page 1 of 1 (12 posts)
Tags:
None
Registered Member 
|
Each time I try to start kontact, I have this error from akonadi: no agents are found. The following is a snip of the saved message:
My KDE compiled from trunk is located in /opt/kde. |
Manager
|
Do you have a standard addressbook that has been used in KAddressBook before? If so, this can be migrated, after which Akonadi will start. See if any of the notes at http://userbase.kde.org/Akonadi help
annew, proud to be a member of KDE forums since 2008-Oct and a KDE user since 2002.
Join us on http://userbase.kde.org |
|
Registered Member
|
No, I don't.
I checked that page, but I did not find any useful information about my problem. The only relevant section is the following:
I put in ~/.bashrc an export statement in order to add to that value the path /opt/kde/share/akonadi/agents, where the following desktop files are located:
Since I did not fully understand what is in fact an agent (is it a executable? a configuration file? a running process?), I only checked the executables whose name begins with "akonadi":
In facts I have lots of "resources". Must I install something else? |
KDE Developer
|
The most common cause for this is an error earlier on.
Does your test log have any error before Test 14? Cheers, _ P.S. agents are executables, helper processes that perform task on behalf of the Akonadi server. A special category of agents are called resources. Those are helpers which transport data between a storage system and the Akonadi server, e.g. between a local calendar file and Akonadi or between an IMAP server and Akonadi, etc.
anda_skoa, proud to be a member of KDE forums since 2008-Oct.
|
KDE Developer
|
Just to be sure, can you paste the relevant .bashrc line please? you should have :
or
Akonadi user FAQ: http://userbase.kde.org/Akonadi
|
|
Registered Member
|
Thanks for explication. No, the test show that all is ok or is skipped:
I wrote exactly:
Shall I try "/opt/kde/share" instead of "/opt/kde/share/akonadi/agents"? EDIT: I tried so and now akonadi is working! Thanks! 
|
|
Registered Member
|
I know this thread is quite old now, but in case anyone else is reading this and wants an easy fix, all I had to do before running e.g. Kontact, was to run Akonaditray. The error goes away while it's running. Strange, but it works.
I'm running Kubuntu 10.04 with KDE 4.4.3 (via backports). |
|
Registered Member
|
I`m using KDE 4.4.4 (Ubuntu 10.04 desktop x64) now,and I have the same problem.
When I login KDE,and start kontact first time,Akonadi will report same messages. dump the messages as following lines: 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/samon/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi Host= User= Password= Options="UNIX_SOCKET=/home/samon/.local/share/akonadi/db_misc/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true [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.41-3ubuntu11 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 4: SUCCESS -------- MySQL server log contains no errors. Details: The MySQL server log file '<a href='/home/samon/.local/share/akonadi/db_data/mysql.err'>/home/samon/.local/share/akonadi/db_data/mysql.err</a>' does not contain any errors or warnings. File content of '/home/samon/.local/share/akonadi/db_data/mysql.err': 100603 21:39:07 [Note] Plugin 'FEDERATED' is disabled. 100603 21:39:08 InnoDB: Started; log sequence number 0 122691 100603 21:39:09 [Note] /usr/sbin/mysqld-akonadi: ready for connections. Version: '5.1.41-3ubuntu11-log' socket: '/home/samon/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu) 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,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=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/samon/.local/share/akonadi/mysql.conf'>/home/samon/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/samon/.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,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=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: SUCCESS -------- Akonadi control process registered at D-Bus. Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational. Test 10: SUCCESS -------- Akonadi server process registered at D-Bus. Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational. Test 11: 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 12: SUCCESS -------- Nepomuk search service uses an appropriate backend. Details: The Nepomuk search service uses one of the recommended backends. Test 13: SUCCESS -------- Server protocol version is recent enough. Details: The server Protocol version is 23, which equal or newer than the required version 23. 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 /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 gcalresource.desktop googledataresource.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 gcalresource.desktop googledataresource.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 15: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 16: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server did report error during its previous startup into <a href='/home/samon/.local/share/akonadi/akonadiserver.error.old'>/home/samon/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/samon/.local/share/akonadi/akonadiserver.error.old': Control process died, committing suicide! Test 17: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 18: ERROR -------- Previous Akonadi control error log found. Details: The Akonadi control process did report error during its previous startup into <a href='/home/samon/.local/share/akonadi/akonadi_control.error.old'>/home/samon/.local/share/akonadi/akonadi_control.error.old</a>. File content of '/home/samon/.local/share/akonadi/akonadi_control.error.old': D-Bus session bus went down - quitting How to resolve? Thx. |
|
Registered Member
|
Had the same problem, happening from time to time. Seems to depend on the startup sequence of Akonadi, whether launched manually, bu Akonaditray or by kKmail/Kontact.
Nevertheless, setting XDG_DATA_DIRS to the right path seem to have solved the problem. Go to your error log, have a look at the agents section and add the path where they have been found (and not loaded for whatever reason) to XDG_DATA_DIRS. I am on ubuntu 9.10 with KDE 4.4.2 and that is what I have set it to using bash shell:
I cannot understand why akonadictl could not do that himself as it clearly finds the agents and lists them but still does complain and not load them. I would then expect it to add the path where it found the agent to the XDG_DATA_DIRS. No ordinary user should be required to edit any system environment variables or open a bash shell. Okay, most of us are cracks but when you want to become mainstream.... Regards, Ingo |
|
KDE Developer
|
That path list (well, without the duplicate) is actually the default if the variable is not set at all.
If you had to change it, it would be interesting to check what made it wrong in the first place. However, the "no agents found" in KDE 4.4.x is actually a fluke, Akonadi does find the agents, its just that the application running the self test dialog doesn't know that due to a bug. Which is fixed now, though https://bugs.kde.org/show_bug.cgi?id=236538#c18 As for setting an environment variable automatically: Environment variables are "copied" on process start, changes to the environment of one process are therefore totally invisible to any other process (they have their own copy of all values). Cheers, _
anda_skoa, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
I had the former, but I just changed it to the latter in hopes my package manager would quit telling me "'/usr/share' is not in the search path". PS It has been working. |
|
Registered Member
|
After adding Akonadi's search path in .bashrc it started working as intended
 Thanks again. Can any one mention a bit more on why it doesn't turn up there initially. |
Page 1 of 1 (12 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar
