From bugzilla_noreply@novell.com Wed Dec 22 08:14:16 2010 From: bugzilla_noreply@novell.com To: bugs@lists.opensuse.org Subject: [Bug 660958] New: akonadi server not starting anymore after kmail crash Date: Wed, 22 Dec 2010 08:14:08 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2059352054338924976==" --===============2059352054338924976== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable https://bugzilla.novell.com/show_bug.cgi?id=3D660958 https://bugzilla.novell.com/show_bug.cgi?id=3D660958#c0 Summary: akonadi server not starting anymore after kmail crash Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: chuller(a)novell.com QAContact: qa(a)suse.de Found By: Customer Blocker: --- Description: Yesterday my kmail did not respond anymore, the window containing the mail i was about to send froze completely and trying to close kmail resulted in some popup telling me that kmail is not responding anymore and if i would like to terminate it. I choose "Yes" and kmail disappeared. After that I started kmail again, which came up and seems to work fine (not y= et used for a longer time), however - while starting up, also some window appear= ed telling me "Starting akonadi server" ... just to be immediately followed by another window that contained the following error messages: ---------------------------------snip----------------------------------------- Akonadi Server Self-Test Report =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D 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 '/suse/chuller/.config/akonadi/akonadiserverrc': [%General] Driver=3DQMYSQL SizeThreshold=3D4096 ExternalPayload=3Dfalse [QMYSQL] Name=3Dakonadi Host=3D User=3D Password=3D Options=3D"UNIX_SOCKET=3D/suse/chuller/.local/share/akonadi/db_misc/mysql.soc= ket" ServerPath=3D/usr/sbin/mysqld StartServer=3Dtrue [Debug] Tracer=3Dnull Test 2: SUCCESS -------- MySQL server found. Details: You currently have 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 locations varies depending on the distribution. Test 3: SUCCESS -------- MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.46 for suse-linux-gnu = on x86_64 (SUSE MySQL RPM) Test 4: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '/suse/chuller/.= local/share/akonadi/db_data/mysql.err' contains errors. File content of '/suse/chuller/.local/share/akonadi/db_data/mysql.err': 101221 16:00:45 [Note] Plugin 'ndbcluster' is disabled. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 101221 16:00:45 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 101221 16:02:25 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 101221 16:02:25 InnoDB: Operating system error number 11 in a file operation. InnoDB: Error number 11 means 'Resource temporarily unavailable'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html InnoDB: Could not open or create data files. InnoDB: If you tried to add new data files, and it failed here, InnoDB: you should now edit innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove the new ibdata files InnoDB created InnoDB: in this failed attempt. InnoDB only wrote those files full of InnoDB: zeros, but did not yet use them in any way. But be careful: do not InnoDB: remove old data files which contain your precious data! 101221 16:02:25 [ERROR] Plugin 'InnoDB' init function returned error. 101221 16:02:25 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 101221 16:02:25 [ERROR] Unknown/unsupported table type: innodb 101221 16:02:25 [ERROR] Aborting 101221 16:02:25 [Note] /usr/sbin/mysqld: Shutdown complete Test 5: SUCCESS -------- MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at /etc/akonadi/mysql-global.conf. 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=C3=83=C2=B6hntopp # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=3Dstrict_trans_tables,strict_all_tables,strict_error_for_division_b= y_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_ze= ro_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=3Dstrict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=3Dinnodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=3D1 character_set_server=3Dlatin1 collation_server=3Dlatin1_general_ci table_cache=3D200 thread_cache_size=3D3 log_bin=3Dmysql-bin expire_logs_days=3D3 #sync_bin_log=3D0 # error log file name, relative to datadir log_error=3Dmysql.err log_warnings=3D2 # log all queries, useful for debugging but generates an enormous amount of data #log=3Dmysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=3Dmysql.slow #long_query_time=3D1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=3D1 # maximum blob size max_allowed_packet=3D32M max_connections=3D256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=3D0 query_cache_size=3D0 innodb_file_per_table=3D1 innodb_log_buffer_size=3D1M innodb_additional_mem_pool_size=3D1M # 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=3D80M # 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=3D64M innodb_flush_log_at_trx_commit=3D2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=3D1296000 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 /suse/chuller/.local/s= hare/akonadi/mysql.conf and is readable. File content of '/suse/chuller/.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=C3=83=C2=B6hntopp # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=3Dstrict_trans_tables,strict_all_tables,strict_error_for_division_b= y_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_ze= ro_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=3Dstrict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=3Dinnodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=3D1 character_set_server=3Dlatin1 collation_server=3Dlatin1_general_ci table_cache=3D200 thread_cache_size=3D3 log_bin=3Dmysql-bin expire_logs_days=3D3 #sync_bin_log=3D0 # error log file name, relative to datadir log_error=3Dmysql.err log_warnings=3D2 # log all queries, useful for debugging but generates an enormous amount of data #log=3Dmysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=3Dmysql.slow #long_query_time=3D1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=3D1 # maximum blob size max_allowed_packet=3D32M max_connections=3D256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=3D0 query_cache_size=3D0 innodb_file_per_table=3D1 innodb_log_buffer_size=3D1M innodb_additional_mem_pool_size=3D1M # 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=3D80M # 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=3D64M innodb_flush_log_at_trx_commit=3D2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=3D1296000 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 typical= ly 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: 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: 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', 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 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' Test 14: ERROR -------- Current Akonadi server error log found. Details: The Akonadi server did report error during startup into /suse/chuller= /.local/share/akonadi/akonadiserver.error. File content of '/suse/chuller/.local/share/akonadi/akonadiserver.error': "[ 0: akonadiserver(_Z11akBacktracev+0x39) [0x40c5d9] 1: akonadiserver() [0x40cb42] 2: /lib64/libc.so.6(+0x32a60) [0x7f52c9560a60] 3: /lib64/libc.so.6(gsignal+0x35) [0x7f52c95609e5] 4: /lib64/libc.so.6(abort+0x186) [0x7f52c9561ee6] 5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f52ca73e984] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x40e45b] 7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7f52ca7c9c37] 8: /usr/lib64/libQtCore.so.4(+0x103026) [0x7f52ca7d2026] 9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f52ca7daefb] 10: /usr/lib64/libakonadiprivate.so.1(_ZN6QDebugD1Ev+0x4b) [0x7f52cab9147b] 11: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatab= aseProcessEv+0x33ea) [0x7f52cab9efca] 12: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabasePr= ocessEv+0x2e8) [0x7f52caba0288] 13: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x76) [0x7f52caba06b6] 14: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7f52caba1dba] 15: akonadiserver(main+0x217) [0x406767] 16: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f52c954cb7d] 17: akonadiserver() [0x406459] ] "=20 Test 15: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server did report error during its previous startup into /suse/chu= ller/.local/share/akonadi/akonadiserver.error.old. File content of '/suse/chuller/.local/share/akonadi/akonadiserver.error.old': "[ 0: akonadiserver(_Z11akBacktracev+0x39) [0x40c5d9] 1: akonadiserver() [0x40cb42] 2: /lib64/libc.so.6(+0x32a60) [0x7fed013c8a60] 3: /lib64/libc.so.6(gsignal+0x35) [0x7fed013c89e5] 4: /lib64/libc.so.6(abort+0x186) [0x7fed013c9ee6] 5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7fed025a6984] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x40e45b] 7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7fed02631c37] 8: /usr/lib64/libQtCore.so.4(+0x103026) [0x7fed0263a026] 9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7fed02642efb] 10: /usr/lib64/libakonadiprivate.so.1(_ZN6QDebugD1Ev+0x4b) [0x7fed029f947b] 11: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatab= aseProcessEv+0x33ea) [0x7fed02a06fca] 12: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabasePr= ocessEv+0x2e8) [0x7fed02a08288] 13: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x76) [0x7fed02a086b6] 14: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7fed02a09dba] 15: akonadiserver(main+0x217) [0x406767] 16: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7fed013b4b7d] 17: akonadiserver() [0x406459] ] "=20 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. ---------------------------------snip----------------------------------------- If further issues appear I'll add them to this bug report --=20 Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are on the CC list for the bug. --===============2059352054338924976==-- From bugzilla_noreply@novell.com Wed Dec 22 08:32:07 2010 From: bugzilla_noreply@novell.com To: bugs@lists.opensuse.org Subject: [Bug 660958] akonadi server not starting anymore after kmail crash Date: Wed, 22 Dec 2010 08:31:57 +0000 Message-ID: <20101222083157.A7ED124551D@molor.provo.novell.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1947245136109441062==" --===============1947245136109441062== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable https://bugzilla.novell.com/show_bug.cgi?id=3D660958 https://bugzilla.novell.com/show_bug.cgi?id=3D660958#c1 Christian Hueller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #1 from Christian Hueller 2010-12-22 08:31= :57 UTC --- I missed an akonadi update - not sure if that is related, however after updating my system I had to reboot (kernel update) and after coming up again, the problem was gone. Closing the bug - will reopen if i see the problem once more. --=20 Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are on the CC list for the bug. --===============1947245136109441062==--