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/bobbyubuhaut/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/tmp/akonadi-bobbyubuhaut.vyIuKa/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true [Debug] Tracer=null 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-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 location varies depending on the distribution. Test 4: SUCCESS -------- MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.41-0ubuntu0.14.10.1 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 5: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '<a href='/home/bobbyubuhaut/.local/share/akonadi/db_data/mysql.err'>/home/bobbyubuhaut/.local/share/akonadi/db_data/mysql.err</a>' contains errors. File content of '/home/bobbyubuhaut/.local/share/akonadi/db_data/mysql.err': 150408 10:55:25 [Note] Plugin 'FEDERATED' is disabled. 150408 10:55:25 InnoDB: The InnoDB memory heap is disabled 150408 10:55:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150408 10:55:25 InnoDB: Compressed tables use zlib 1.2.8 150408 10:55:25 InnoDB: Using Linux native AIO 150408 10:55:25 InnoDB: Initializing buffer pool, size = 80.0M 150408 10:55:25 InnoDB: Completed initialization of buffer pool 150408 10:55:25 InnoDB: highest supported file format is Barracuda. 150408 10:55:25 InnoDB: Waiting for the background threads to start 150408 10:55:26 InnoDB: 5.5.41 started; log sequence number 2920023 150408 10:55:26 [ERROR] Aborting 150408 10:55:26 InnoDB: Starting shutdown... 150408 10:55:27 InnoDB: Shutdown completed; log sequence number 2920023 150408 10:55:27 [Note] 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] # 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 # DEBUGGING: # 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 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [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: SUCCESS -------- MySQL server configuration is usable. Details: The MySQL server configuration was found at <a href='/home/bobbyubuhaut/.local/share/akonadi/mysql.conf'>/home/bobbyubuhaut/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/bobbyubuhaut/.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] # 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 # DEBUGGING: # 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 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) # Deprecated in MySQL >= 5.6.3 innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [client] default-character-set=utf8 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.12.91 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: 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'. The XDG_DATA_DIRS environment variable is set to '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadinepomukfeederagent.desktop akonotesresource.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 kolabresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop migrationagent.desktop mixedmaildirresource.desktop mtdummyresource.desktop newmailnotifieragent.desktop nntpresource.desktop notesagent.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' Test 14: 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/bobbyubuhaut/.local/share/akonadi/akonadiserver.error'>/home/bobbyubuhaut/.local/share/akonadi/akonadiserver.error</a>. File content of '/home/bobbyubuhaut/.local/share/akonadi/akonadiserver.error': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/bobbyubuhaut/.local/share/akonadi/mysql.conf", "--datadir=/home/bobbyubuhaut/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-bobbyubuhaut.vyIuKa/mysql.socket") stdout: "" stderr: "150408 10:55:25 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys' " exit code: 1 process error: "Process operation timed out" "[ 0: akonadiserver() [0x418df7] 1: akonadiserver() [0x419052] 2: /lib/x86_64-linux-gnu/libc.so.6(+0x36eb0) [0x7f884bf24eb0] 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f884bf24e37] 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f884bf26528] 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f884d735c22] 6: akonadiserver() [0x41aefd] 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f884d7d001a] 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x119fbc) [0x7f884d7defbc] 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f884d7e71a1] 10: akonadiserver() [0x47ff29] 11: akonadiserver() [0x41bb47] 12: akonadiserver() [0x41e1d5] 13: akonadiserver() [0x4e28d4] 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1c1) [0x7f884d858f41] 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f884d84086d] 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x201) [0x7f884d843f41] 17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1a8ed3) [0x7f884d86ded3] 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7f884b5edc5d] 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f48) [0x7f884b5edf48] 20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f884b5edffc] 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x71) [0x7f884d86e031] 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x31) [0x7f884d83f4f1] 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x185) [0x7f884d83f805] 24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x87) [0x7f884d844f67] 25: akonadiserver() [0x413385] 26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f884bf0fec5] 27: akonadiserver() [0x413d4e] ] " Test 15: 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/bobbyubuhaut/.local/share/akonadi/akonadiserver.error.old'>/home/bobbyubuhaut/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/bobbyubuhaut/.local/share/akonadi/akonadiserver.error.old': Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/bobbyubuhaut/.local/share/akonadi/mysql.conf", "--datadir=/home/bobbyubuhaut/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-bobbyubuhaut.vyIuKa/mysql.socket") stdout: "" stderr: "150408 10:55:23 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys' " exit code: 1 process error: "Process operation timed out" "[ 0: akonadiserver() [0x418df7] 1: akonadiserver() [0x419052] 2: /lib/x86_64-linux-gnu/libc.so.6(+0x36eb0) [0x7f19a3422eb0] 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f19a3422e37] 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f19a3424528] 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f19a4c33c22] 6: akonadiserver() [0x41aefd] 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f19a4cce01a] 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x119fbc) [0x7f19a4cdcfbc] 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f19a4ce51a1] 10: akonadiserver() [0x47ff29] 11: akonadiserver() [0x41bb47] 12: akonadiserver() [0x41e1d5] 13: akonadiserver() [0x4e28d4] 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1c1) [0x7f19a4d56f41] 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f19a4d3e86d] 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x201) [0x7f19a4d41f41] 17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1a8ed3) [0x7f19a4d6bed3] 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7f19a2aebc5d] 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f48) [0x7f19a2aebf48] 20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f19a2aebffc] 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x71) [0x7f19a4d6c031] 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x31) [0x7f19a4d3d4f1] 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x185) [0x7f19a4d3d805] 24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x87) [0x7f19a4d42f67] 25: akonadiserver() [0x413385] 26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f19a340dec5] 27: akonadiserver() [0x413d4e] ] " 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. Reproducible: Always Steps to Reproduce: 1. Startup Korganizer 2. Bug message open telling information managing service not operational 3. Actual Results: I can't use Korganizer. Expected Results: Be able to use Korganizer
I tried to reinstall korganizer but the problem is still the same
Created attachment 92866 [details] Akonadi self test log
Hello, I face the exact same issue: since I updated to KUbuntu 15.04, KOrganizer crashes at start up, with error message telling that personal data couln't be operated. The Akonadi self test report (attached) mentions an error in test #5 telling: "MySQL server log contains errors" etc. Would appreciate any help to fixing this blocking issue. Thanks in advance.
Can you get a backtrace with symbols ?
Sorry, I could neither find any korganizer-dbg package nor manage to build one (re: wiki.debian.org/HowToGetABacktrace) Could you please guide me a bit on the way to get the backtrace with symbols that you need, in the present case ?
Hello, You can close it. I had to reinstall all my computer to make it work. There was certainly a conflict betwin akonadi and mysql workbench because it happened when i installed it. Thanks for your answer. De: "Sergio Martins" <iamsergio@gmail.com> À: "hardy xavier" <hardy.xavier@free.fr> Envoyé: Jeudi 28 Mai 2015 19:13:38 Objet: [korganizer] [Bug 345972] crash at the start of Korganizer. Impossible to use. Akonadi problem with D-Bus. https://bugs.kde.org/show_bug.cgi?id=345972 Sergio Martins <iamsergio@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iamsergio@gmail.com --- Comment #4 from Sergio Martins <iamsergio@gmail.com> --- Can you get a backtrace with symbols ?
Good news for bobbyxh. But I'm not prepared to reinstall the whole system just to fix a conflict between Akonadi and MySql. Apparently, a lot of applications became dependant on Akonadi within the new KUbuntu 15.04. Then it would certainly be worth to understand this drawback. So, please keep it open. Thanks.
ok -----Message d'origine----- De : bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] De la part de Francois M Envoyé : vendredi 29 mai 2015 23:44 À : hardy.xavier@free.fr Objet : [korganizer] [Bug 345972] crash at the start of Korganizer. Impossible to use. Akonadi problem with D-Bus. https://bugs.kde.org/show_bug.cgi?id=345972 --- Comment #7 from Francois M <francoismalias-fwd@yahoo.fr> --- Good news for bobbyxh. But I'm not prepared to reinstall the whole system just to fix a conflict between Akonadi and MySql. Apparently, a lot of applications became dependant on Akonadi within the new KUbuntu 15.04. Then it would certainly be worth to understand this drawback. So, please keep it open. Thanks. -- You are receiving this mail because: You reported the bug. --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. http://www.avast.com
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.