I recently updated my laptop from 11.3 to suse 12.2 and am trying to run kOrganizer which is part of KDE but I open the error message and the 2 main errors have to do with mySQL and akonadi … now I have all the same software and apps running fine on my Desktop computer …
- where do I find my error logs for akonadi and mysql
- can or should I delete them
3 what should I edit
4 how should I edit
5 should any of these be running in root (as one of the error messages state)
6 what else should I look for
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/eric/.config/akonadi/akonadiserverrc’:
%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options=“UNIX_SOCKET=/home/eric/.local/share/akonadi/socket-linux-36ko.site/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.5.28 for Linux on i686 (Source distribution)
Test 5: ERROR
MySQL server log contains errors.
Details: The MySQL server error log file ‘<a href=’/home/eric/.local/share/akonadi/db_data/mysql.err’>/home/eric/.local/share/akonadi/db_data/mysql.err</a>’ contains errors.
File content of ‘/home/eric/.local/share/akonadi/db_data/mysql.err’:
130417 9:30:54 InnoDB: The InnoDB memory heap is disabled
130417 9:30:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130417 9:30:54 InnoDB: Compressed tables use zlib 1.2.7
130417 9:30:54 InnoDB: Initializing buffer pool, size = 80.0M
130417 9:30:54 InnoDB: Completed initialization of buffer pool
130417 9:30:54 InnoDB: highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.3.3 Troubleshooting InnoDB I/O Problems
130417 9:30:54 [ERROR] Plugin ‘InnoDB’ init function returned error.
130417 9:30:54 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
130417 9:30:54 [ERROR] Unknown/unsupported storage engine: innodb
130417 9:30:54 [ERROR] Aborting
130417 9:30:54 [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/eric/.local/share/akonadi/mysql.conf’>/home/eric/.local/share/akonadi/mysql.conf</a> and is readable.
File content of ‘/home/eric/.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