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/USER/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
 
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/USER/.local/share/akonadi/socket-jlaptop/mysql.socket"
ServerPath=/usr/sbin/mysqld
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'.
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.61-3 for debian-linux-gnu on i486 ((Debian))
 
 
Test 5:  ERROR
--------
 
MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/USER/.local/share/akonadi/db_data/mysql.err'>/home/USER/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.
 
File content of '/home/USER/.local/share/akonadi/db_data/mysql.err':
120529 20:56:25 [Note] Plugin 'FEDERATED' is disabled.
120529 20:56:25  InnoDB: Initializing buffer pool, size = 80.0M
120529 20:56:25  InnoDB: Completed initialization of buffer pool
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.
120529 20:56:25  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.
120529 20:58:15  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120529 20:58:15  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!
120529 20:58:15 [ERROR] Plugin 'InnoDB' init function returned error.
120529 20:58:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120529 20:58:15 [ERROR] Unknown/unsupported table type: innodb
120529 20:58:15 [ERROR] Aborting
 
120529 20:58:15 [Note] /usr/sbin/mysqld: Shutdown complete
 
 
 
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)
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_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
 
[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/USER/.local/share/akonadi/mysql.conf'>/home/USER/.local/share/akonadi/mysql.conf</a> and is readable.
 
File content of '/home/USER/.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)
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_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
 
[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.7.2
 
 
Test 10:  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 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:  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 13:  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 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'. 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.
 
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 15:  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/USER/.local/share/akonadi/akonadiserver.error'>/home/USER/.local/share/akonadi/akonadiserver.error</a>.
 
File content of '/home/USER/.local/share/akonadi/akonadiserver.error':
"[
0: akonadiserver() [0x805db65]
1: akonadiserver() [0x805de9f]
2: [0xb76e9400]
3: [0xb76e9424]
4: /lib/i386-linux-gnu/i686/cmov/libc.so.6(gsignal+0x51) [0xb6dd4941]
5: /lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x182) [0xb6dd7d72]
6: /lib/i386-linux-gnu/libglib-2.0.so.0(g_assertion_message+0x16e) [0xb6cdbe8e]
7: /lib/i386-linux-gnu/libglib-2.0.so.0(+0x4c400) [0xb6cbd400]
]
"  
 
 
Test 16:  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/USER/.local/share/akonadi/akonadiserver.error.old'>/home/USER/.local/share/akonadi/akonadiserver.error.old</a>.
 
File content of '/home/USER/.local/share/akonadi/akonadiserver.error.old':
"[
0: akonadiserver() [0x805db65]
1: akonadiserver() [0x805de9f]
2: [0xb7730400]
3: [0xb7730424]
4: /lib/i386-linux-gnu/i686/cmov/libc.so.6(gsignal+0x51) [0xb6e1b941]
5: /lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x182) [0xb6e1ed72]
6: /lib/i386-linux-gnu/libglib-2.0.so.0(g_assertion_message+0x16e) [0xb6d22e8e]
7: /lib/i386-linux-gnu/libglib-2.0.so.0(+0x4c400) [0xb6d04400]
]
"  
 
 
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:  SUCCESS
--------
 
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
 

USER@jlaptop:~/.local/share/akonadi$ ll
total 24
-rw-r--r-- 1 USER USER  384 mai   30 13:08 akonadiserver.error
-rw-r--r-- 1 USER USER  384 mai   30 13:08 akonadiserver.error.old
drwxr-xr-x 4 USER USER 4096 mai   30 13:10 db_data
drwxr-xr-x 2 USER USER 4096 mai   29 20:53 db_misc
drwxr-xr-x 2 USER USER 4096 mai   29 20:53 file_db_data
-rw-r--r-- 1 USER USER 3277 mai   29 20:53 mysql.conf
lrwxrwxrwx 1 USER USER   31 mai   30 13:08 socket-jlaptop -> /tmp/akonadi-USER.RV7l8T
USER@jlaptop:~/.local/share/akonadi$ cd ..
USER@jlaptop:~/.local/share$ rm -rf 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/USER/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
 
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/USER/.local/share/akonadi/socket-jlaptop/mysql.socket"
ServerPath=/usr/sbin/mysqld
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'.
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.61-3 for debian-linux-gnu on i486 ((Debian))
 
 
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/USER/.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]
 
# 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)
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_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
 
[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.7.2
 
 
Test 10:  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 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:  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 13:  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 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'. 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.
 
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 15:  SUCCESS
--------
 
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
 
Test 16:  SUCCESS
--------
 
No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.
 
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:  SUCCESS
--------
 
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
 

120530 18:11:52 [Note] Plugin 'FEDERATED' is disabled.
120530 18:11:52  InnoDB: Initializing buffer pool, size = 80.0M
120530 18:11:52  InnoDB: Completed initialization of buffer pool
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.
120530 18:11:52  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.
----------8<----------8<----------8<----------8<----------8<----------
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.
120530 18:13:43  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120530 18:13:43  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!
120530 18:13:43 [ERROR] Plugin 'InnoDB' init function returned error.
120530 18:13:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120530 18:13:43 [ERROR] Unknown/unsupported table type: innodb
120530 18:13:43 [ERROR] Aborting

120530 18:13:43 [Note] /usr/sbin/mysqld: Shutdown complete

1000      4566  0.1  1.0 191368 22244 ?        Sl   12:22   0:00 /usr/sbin/mysqld --defaults-file=/home/USER/.local/share/akonadi/mysql.conf --datadir=/home/USER/.local/share/akonadi/db_data/ --socket=/home/USER/.local/share/akonadi/socket-jlaptop/mysql.socket