I'm new here, so thank you for the opportunity and please be gentle.

I've got a fresh installation of Mageia 6:
Linux 4.9.50-desktop-1.mga6 #1 SMP Wed Sep 13 23:14:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
plasma-desktop-5.8.4-1.mga6.x86_64

I can't get Akonadi to start. My access to mysql is fine, but there seems to be some trouble where Akonadi is concerned.

Any help with this is appreciated.

The self-test shows this:

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/madams/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-madams.JNM4vB/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


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: 2017-09-17 23:29:22 139846940252224 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
/usr/sbin/mysqld Ver 10.1.26-MariaDB for Linux on x86_64 (Mageia MariaDB Server)


Test 5: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file '<a href="/home/madams/.local/share/akonadi/db_data/mysql.err">/home/madams/.local/share/akonadi/db_data/mysql.err</a>' contains errors.

File content of '/home/madams/.local/share/akonadi/db_data/mysql.err':
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using Linux native AIO
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using SSE crc32 instructions
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Completed initialization of buffer pool
2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode
2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: The system tablespace must be writable!
2017-09-17 23:29:22 140100944709696 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-17 23:29:22 140100944709696 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-09-17 23:29:22 140100944709696 [ERROR] Unknown/unsupported storage engine: innodb
2017-09-17 23:29:22 140100944709696 [ERROR] Aborting



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:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)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/madams/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-madams.JNM4vB/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


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: 2017-09-17 23:29:22 139846940252224 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
/usr/sbin/mysqld Ver 10.1.26-MariaDB for Linux on x86_64 (Mageia MariaDB Server)


Test 5: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file '<a href="/home/madams/.local/share/akonadi/db_data/mysql.err">/home/madams/.local/share/akonadi/db_data/mysql.err</a>' contains errors.

File content of '/home/madams/.local/share/akonadi/db_data/mysql.err':
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using Linux native AIO
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Using SSE crc32 instructions
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2017-09-17 23:29:22 140100944709696 [Note] InnoDB: Completed initialization of buffer pool
2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode
2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: The system tablespace must be writable!
2017-09-17 23:29:22 140100944709696 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-17 23:29:22 140100944709696 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-09-17 23:29:22 140100944709696 [ERROR] Unknown/unsupported storage engine: innodb
2017-09-17 23:29:22 140100944709696 [ERROR] Aborting



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:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M

# 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/madams/.local/share/akonadi/mysql.conf">/home/madams/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/madams/.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:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M

# 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 '/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 5.3.3


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 '/var/lib/plasma5-profiles/common/share:/usr/local/share:/usr/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadiindexingagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kalarmdirresource.desktop
kalarmresource.desktop
knutresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
newmailnotifieragent.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
tomboynotesresource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/var/lib/plasma5-profiles/common/share:/usr/local/share:/usr/share'

Test 14: SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

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/madams/.local/share/akonadi/akonadiserver.error.old">/home/madams/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/madams/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!executable: "/usr/sbin/mysqld"arguments: ("--defaults-file=/home/madams/.local/share/akonadi/mysql.conf", "--datadir=/home/madams/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-madams.JNM4vB/mysql.socket")stdout: ""stderr: "2017-09-17 23:29:22 140100944709696 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB) starting as process 30346 ...\n"exit code: 1process error: "Unknown error"Failed to remove Unix socketFailed to remove runtime connection config file

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: ERROR
--------

Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href="/home/madams/.local/share/akonadi/akonadi_control.error.old">/home/madams/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/home/madams/.local/share/akonadi/akonadi_control.error.old':
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)Application 'akonadiserver' exited normally...


# innodb_additional_mem_pool_size=8M

# 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/madams/.local/share/akonadi/mysql.conf">/home/madams/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/madams/.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:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M

# 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 '/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 5.3.3


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 '/var/lib/plasma5-profiles/common/share:/usr/local/share:/usr/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadiindexingagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kalarmdirresource.desktop
kalarmresource.desktop
knutresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
newmailnotifieragent.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
tomboynotesresource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/var/lib/plasma5-profiles/common/share:/usr/local/share:/usr/share'

Test 14: SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

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/madams/.local/share/akonadi/akonadiserver.error.old">/home/madams/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/madams/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!executable: "/usr/sbin/mysqld"arguments: ("--defaults-file=/home/madams/.local/share/akonadi/mysql.conf", "--datadir=/home/madams/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-madams.JNM4vB/mysql.socket")stdout: ""stderr: "2017-09-17 23:29:22 140100944709696 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB) starting as process 30346 ...\n"exit code: 1process error: "Unknown error"Failed to remove Unix socketFailed to remove runtime connection config file

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: ERROR
--------

Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href="/home/madams/.local/share/akonadi/akonadi_control.error.old">/home/madams/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/home/madams/.local/share/akonadi/akonadi_control.error.old':
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)Application 'akonadiserver' exited normally...

The problem seems to be this:

Code: Select all

2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode
2017-09-17 23:29:22 140100944709696 [ERROR] InnoDB: The system tablespace must be writable!


So check the file permissions and ownerships in the folder ~/.local/share/akonadi/db_data/, especially of the file ibdata1.

Code: Select all

ls -la ~/.local/share/akonadi/db_data/

Might also indicate file system corruption though.

I'm at work and doing this on my phone. It's awkward.

I spent a lot of time checking permissions last night. In desperation I set db_data to 777:

drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 db_data/

The contents are mostly 660 and owned by me.

total 209132
drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 ./
drwxrwxr-x 6 madams madams 4096 Sep 18 00:40 ../
drwx------ 2 madams madams 4096 Sep 18 00:15 akonadi/
-rw-rw---- 1 madams madams 16384 Sep 18 00:40 aria_log.000000
1
-rw-rw---- 1 madams madams 52 Sep 18 00:40 aria_log_contro
-rw-rw---- 1 madams madams 12582912 Sep 18 00:24 ibdata1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:33 ib_logfile0
-rw-rw---- 1 madams madams 67108864 Sep 18 00:15 ib_logfile1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:24 ib_logfile101
-rw-rw---- 1 madams madams 0 Sep 18 00:15 multi-master.in
o
drwx------ 2 mysql root 4096 Sep 17 20:00 mysql/
-rw-rw---- 1 madams madams 2146 Sep 18 00:40 mysql.err
-rw-r--r-- 1 madams madams 180126 Sep 18 00:40 mysql.err.old
-rw-rw---- 1 mysql mysql 1023 Sep 17 20:00 sql_errors.log
drwx------ 2 mysql root 4096 Sep 17 20:00 test/

I'm home and I've juggled permissions on these files. I also just logged out of kde, deleted /home/madams/.local/share/akonadi/db_data/akonadi/*, as well as ibdata1 and the log files and logged back in. Things improved, but there are still issues.

The akonadiselftest gets down to step 5 and throws this:

Code: Select all

MySQL server log contains errors.
Details: The MySQL server error log file '<a href="/home/madams/.local/share/akonadi/db_data/mysql.err">/home/madams/.local/share/akonadi/db_data/mysql.err</a>' contains errors.

File content of '/home/madams/.local/share/akonadi/db_data/mysql.err':
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Using Linux native AIO
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Using SSE crc32 instructions
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Completed initialization of buffer pool
2017-09-18 23:09:00 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Retrying to lock the first data file
2017-09-18 23:09:01 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:01 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:02 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:02 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:03 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:03 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:04 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:04 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:05 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:05 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:06 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:06 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:07 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:07 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:08 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:08 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:09 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:09 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:10 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:10 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:11 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:11 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:12 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:12 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-18 23:09:13 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:13 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.


A quick survey of google lead to the idea that I've got more than one mysql instance. Here's what I get from "ps aux|grep mysql":

Code: Select all

# ps aux|grep mysqld
mysql    13752  0.0  0.7 604564 64008 ?        Ssl  22:41   0:01 /usr/sbin/mysqld
madams   17785  0.0  0.7 580492 61088 ?        Sl   23:00   0:01 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.JNM4vB/mysql.socket
madams   29171  0.5  0.7 574348 61012 ?        Sl   23:29   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   29251  0.2  0.3 273788 26852 ?        Sl   23:29   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   29290  0.2  0.3 273788 26760 ?        Sl   23:29   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   29325  0.2  0.3 273788 26896 ?        Sl   23:29   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
root     29676  0.0  0.0 106216   888 pts/1    S+   23:31   0:00 grep --color mysqld


There are some good things about this information. The socket is being created. Unfortunately, it's being created in duplicate. When I kill some of these process they come back in greater numbers!

What should I be doing here?

Thanks.

I've wrestled with it some more and it comes down to locking the ibdata1 file. The errors seem to indicate that I've got more than one mysqld instance running. Here's what processes show:

Code: Select all

# ps aux|grep mysqld
mysql    23544  0.2  0.7 593660 59352 ?        Ssl  23:49   0:00 /usr/sbin/mysqld
madams   24621  1.6  0.7 572300 58644 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24698  0.7  0.3 273788 27012 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24736  0.7  0.3 273788 26976 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24769  0.7  0.3 273788 26828 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
root     25373  0.0  0.0 106216   860 pts/1    S+   23:51   0:00 grep --color mysqld

I don't seem to have any control over this. I kill them and they just come back with a different pid. I haven't found any clues as to how I can stop these processes from spawning.

Help?

adamsmark wrote:I'm at work and doing this on my phone. It's awkward.

I spent a lot of time checking permissions last night. In desperation I set db_data to 777:

drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 db_data/

It should be owned by your user, not the user "mysql".
777 shouldn't be necessary then.

The contents are mostly 660 and owned by me.

total 209132
drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 ./
drwxrwxr-x 6 madams madams 4096 Sep 18 00:40 ../
drwx------ 2 madams madams 4096 Sep 18 00:15 akonadi/
-rw-rw---- 1 madams madams 16384 Sep 18 00:40 aria_log.000000
1
-rw-rw---- 1 madams madams 52 Sep 18 00:40 aria_log_contro
-rw-rw---- 1 madams madams 12582912 Sep 18 00:24 ibdata1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:33 ib_logfile0
-rw-rw---- 1 madams madams 67108864 Sep 18 00:15 ib_logfile1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:24 ib_logfile101
-rw-rw---- 1 madams madams 0 Sep 18 00:15 multi-master.in
o
drwx------ 2 mysql root 4096 Sep 17 20:00 mysql/
-rw-rw---- 1 madams madams 2146 Sep 18 00:40 mysql.err
-rw-r--r-- 1 madams madams 180126 Sep 18 00:40 mysql.err.old
-rw-rw---- 1 mysql mysql 1023 Sep 17 20:00 sql_errors.log
drwx------ 2 mysql root 4096 Sep 17 20:00 test/

The mysql folder is owned my user "mysql", it (and its content) should be owned by you.
Same for test, but I suppose that won't matter much.

adamsmark wrote:I've wrestled with it some more and it comes down to locking the ibdata1 file. The errors seem to indicate that I've got more than one mysqld instance running.

And what is the current error exactly?

Here's what processes show:

Code: Select all

# ps aux|grep mysqld
mysql    23544  0.2  0.7 593660 59352 ?        Ssl  23:49   0:00 /usr/sbin/mysqld
madams   24621  1.6  0.7 572300 58644 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24698  0.7  0.3 273788 27012 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24736  0.7  0.3 273788 26976 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24769  0.7  0.3 273788 26828 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
root     25373  0.0  0.0 106216   860 pts/1    S+   23:51   0:00 grep --color mysqld

I don't seem to have any control over this. I kill them and they just come back with a different pid. I haven't found any clues as to how I can stop these processes from spawning.

Well, akonadi will restart mysql if necessary I think.
I'm not sure whether its normal that there a several though, I only use an external (system-wide) instance myself. (I can check on a different system tomorrow though).

One thing: the first one seems to be a system-wide instance. Shouldn't play any role here, unless you configured it to use /home/xxx/.local/share/akonadi/db_data/ for its tables.
You shouldn't do that and I hope you didn't, but it would explain the wrong ownership of some files/folders.

What version of akonadi are you using btw?
There have been some fixes in the handling of the internal mysql server processes a few months ago...

wolfi323 wrote:

adamsmark wrote:I'm at work and doing this on my phone. It's awkward.

I spent a lot of time checking permissions last night. In desperation I set db_data to 777:

drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 db_data/

It should be owned by your user, not the user "mysql".
777 shouldn't be necessary then.

The contents are mostly 660 and owned by me.

total 209132
drwxrwxrwx 5 mysql madams 4096 Sep 18 00:40 ./
drwxrwxr-x 6 madams madams 4096 Sep 18 00:40 ../
drwx------ 2 madams madams 4096 Sep 18 00:15 akonadi/
-rw-rw---- 1 madams madams 16384 Sep 18 00:40 aria_log.000000
1
-rw-rw---- 1 madams madams 52 Sep 18 00:40 aria_log_contro
-rw-rw---- 1 madams madams 12582912 Sep 18 00:24 ibdata1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:33 ib_logfile0
-rw-rw---- 1 madams madams 67108864 Sep 18 00:15 ib_logfile1
-rw-rw---- 1 madams madams 67108864 Sep 18 00:24 ib_logfile101
-rw-rw---- 1 madams madams 0 Sep 18 00:15 multi-master.in
o
drwx------ 2 mysql root 4096 Sep 17 20:00 mysql/
-rw-rw---- 1 madams madams 2146 Sep 18 00:40 mysql.err
-rw-r--r-- 1 madams madams 180126 Sep 18 00:40 mysql.err.old
-rw-rw---- 1 mysql mysql 1023 Sep 17 20:00 sql_errors.log
drwx------ 2 mysql root 4096 Sep 17 20:00 test/

The mysql folder is owned my user "mysql", it (and its content) should be owned by you.
Same for test, but I suppose that won't matter much.

Okay, that was actually productive. I changed ownership of /home/madams/.local/share/akonadi/db_data/mysql and test to "mysql".

Now, the only error akonadiselftest churns out in test 5 is:

Code: Select all

2017-09-21 13:47:38 139874658756672 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-21 13:47:38 139874658756672 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-21 13:47:38 139874658756672 [Note] InnoDB: Retrying to lock the first data file


But for some reason, it still is unable to get a lock on the file.

I also notice that I'm only getting one instance of mysqld from my user:

Code: Select all

# ps aux|grep mysqld
mysql    23544  0.0  0.8 608364 65984 ?        Ssl  Sep19   0:38 /usr/sbin/mysqld
madams   24621  0.0  0.8 576396 64668 ?        Sl   Sep19   0:41 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket


Looks promising. Work continues.

wolfi323 wrote:

adamsmark wrote:I've wrestled with it some more and it comes down to locking the ibdata1 file. The errors seem to indicate that I've got more than one mysqld instance running.

And what is the current error exactly?

I was talking about the multiplicity of these:

Code: Select all

2017-09-18 23:09:00 140115276617792 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-18 23:09:00 140115276617792 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

I'm no longer getting those.

Here's what processes show:

Code: Select all

# ps aux|grep mysqld
mysql    23544  0.2  0.7 593660 59352 ?        Ssl  23:49   0:00 /usr/sbin/mysqld
madams   24621  1.6  0.7 572300 58644 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24698  0.7  0.3 273788 27012 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24736  0.7  0.3 273788 26976 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
madams   24769  0.7  0.3 273788 26828 ?        Sl   23:51   0:00 /usr/sbin/mysqld --defaults-file=/home/madams/.local/share/akonadi/mysql.conf --datadir=/home/madams/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-madams.mFVdcM/mysql.socket
root     25373  0.0  0.0 106216   860 pts/1    S+   23:51   0:00 grep --color mysqld

I don't seem to have any control over this. I kill them and they just come back with a different pid. I haven't found any clues as to how I can stop these processes from spawning.

Well, akonadi will restart mysql if necessary I think.
I'm not sure whether its normal that there a several though, I only use an external (system-wide) instance myself. (I can check on a different system tomorrow though).

One thing: the first one seems to be a system-wide instance. Shouldn't play any role here, unless you configured it to use /home/xxx/.local/share/akonadi/db_data/ for its tables.
You shouldn't do that and I hope you didn't, but it would explain the wrong ownership of some files/folders.

I haven't messed with that and it seems fine.

What version of akonadi are you using btw?
There have been some fixes in the handling of the internal mysql server processes a few months ago...

Looks like 16.08.3. Installed from Mageia repositories.

Code: Select all

akonadi-16.08.3-1.mga6


Rebooted in hopes that whatever it takes to get the akonadi server running would happen. It didn't but the only error I'm getting is still:

Code: Select all

017-09-21 14:12:26 140670848456768 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-21 14:12:26 140670848456768 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-21 14:12:26 140670848456768 [Note] InnoDB: Retrying to lock the first data file

Still digging on this.

I checked the akonadiserverrc file. Does this look correct?

Code: Select all

[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-madams.mFVdcM/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

Should there be an entry for "Host"?

I'm groping around with all the akonadi stuff I can find. Tried akonadi_control and got some output. Here's the whole thing at Pastebin.

The upshot seems to be this:

Code: Select all

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
akonadiserver: symbol lookup error: akonadiserver: undefined symbol: _ZN7Akonadi8Protocol13HelloResponseC1ERK7QStringS4_i
org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-madams.mFVdcM/akonadiserver.socket"
log_akonadicontrol: ProcessControl: Application 'akonadiserver' returned with exit code 127 (Unknown error)
org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Connection refused" "/tmp/akonadi-madams.mFVdcM/akonadiserver.socket"

The socket is there:

Code: Select all

srwxr-xr-x 1 madams madams 0 Sep 21 23:01 /tmp/akonadi-madams.mFVdcM/akonadiserver.socket=

I assume ownership and permissions are correct.

Then a little later I'm seeing this:

Code: Select all

QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.341'
org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed"
org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Connection refused"
"No file specified."

"...had owner '' but we thought it was ':1.341'"? I'm not sure what that could even mean.


Then there are some of these:

Code: Select all

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/madams/.local/share/akonadi/akonadiserver-ntf.socket"

Of course that socket isn't there.

And finally it just gives up:

Code: Select all

Log_akonadicontrol: ProcessControl: Application 'akonadiserver' returned with exit code 127 (Unknown error)
log_akonadicontrol: "akonadiserver" crashed too often and will not be restarted!
"No file specified."
"No file specified."
"No file specified."
"No file specified."
"No file specified."
log_akonadicontrol: ProcessControl: Application "/bin/akonadi_kalarm_resource" stopped unexpectedly ( "Process crashed" )

Still looking.

adamsmark wrote:

wolfi323 wrote:What version of akonadi are you using btw?
There have been some fixes in the handling of the internal mysql server processes a few months ago...

Looks like 16.08.3. Installed from Mageia repositories.

Ok, that's quite old unfortunately.
As I indicated there were some fixes later on (17.04 in particular), although that's probably not the problem now.

Rebooted in hopes that whatever it takes to get the akonadi server running would happen. It didn't but the only error I'm getting is still:

Code: Select all

017-09-21 14:12:26 140670848456768 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-09-21 14:12:26 140670848456768 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-09-21 14:12:26 140670848456768 [Note] InnoDB: Retrying to lock the first data file

Well, I googled a bit, and besides mysql running more than once, one suggestion was to just delete (or rename) the ib* file(s) and let mysql recreate them.
Maybe try that, i.e. stop Akonadi ("akonadictl stop" as user), move the file, and start Akonadi again ("akonadictl start").

Another suggested possible cause might be that AppArmor is blocking access. AFAICR, this was quite a common problem wih Akonadi on some distributions years ago.
Probably not the case here either, but you might try to disable AppArmor temporarily to rule that out.
I don't know Mageia, but if they use systemd (likely), this should do: "sudo systemctl stop apparmor.service".

adamsmark wrote:I checked the akonadiserverrc file. Does this look correct?

Yes.

Should there be an entry for "Host"?

No, unless you want to connect to a running mysql instance, and not have Akonadi start its own.

In that case, you'd also have to set "StartServer=false" though (and maybe remove the Options, I'm not sure about this).

That may actually be worth a try too, might workaround your problem. (.local/share/akonadi/db_data/ is not used at all then)
And that's what I'm using here (on this system) since years. (also for Amarok, which would normally run its own mysql server as well, so I would have 3 running...)

FTR, that's my akonadiserverrc:

Code: Select all

[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=localhost
Name=akonadi
Options=
Password=xxx
ServerPath=
StartServer=false
User=akonadi


You need to se "User" and "Password" accordingly of course. "Name" specifies the name of the database (inside mysql) to use.
You probably need to create the database first and the specified user must have the necessary permissions of course.

For more details see here, though that config module has been removed meanwhile:
https://exote.ch/blogs/aseigo/2015/08/1 ... -database/

Regarding your last post, I don't think that you can run akonadi_control manually.
You should use "akonadictl start" to start akonadi.
I'm not sure whether your error messages have any relevance or maybe are just caused by this.

"akonadiserver: symbol lookup error: akonadiserver: undefined symbol: _ZN7Akonadi8Protocol13HelloResponseC1ERK7QStringS4_i" might point to some incompatible packages though.
Check that all kdepim/akonadi related packages have the same version.

wolfi323 wrote:

Well, I googled a bit, and besides mysql running more than once, one suggestion was to just delete (or rename) the ib* file(s) and let mysql recreate them.
Maybe try that, i.e. stop Akonadi ("akonadictl stop" as user), move the file, and start Akonadi again ("akonadictl start").

Thanks for the details. I've seen those Google results and tried that as well. The process generated a fresh set of ib* files okay, but akonadi is still not starting:

Code: Select all

[madams@spike db_data]$ akonadictl start
[madams@spike db_data]$ akonadi.collectionattributetable                   OK
akonadi.collectionmimetyperelation                 OK
akonadi.collectionpimitemrelation                  OK
akonadi.collectiontable                            OK
akonadi.flagtable                                  OK
akonadi.mimetypetable                              OK
akonadi.parttable                                  OK
akonadi.parttypetable                              OK
akonadi.pimitemflagrelation                        OK
akonadi.pimitemtable                               OK
akonadi.pimitemtagrelation                         OK
akonadi.relationtable                              OK
akonadi.relationtypetable                          OK
akonadi.resourcetable                              OK
akonadi.schemaversiontable                         OK
akonadi.tagattributetable                          OK
akonadi.tagremoteidresourcerelationtable           OK
akonadi.tagtable                                   OK
akonadi.tagtypetable                               OK
akonadiserverakonadiserverakonadiserver: symbol lookup error: akonadiserver: : symbol lookup errorundefined symbol: _ZN7Akonadi8Protocol13HelloResponseC1ERK7QStringS4_i:


That repeats 4 times and then just dies.

Another suggested possible cause might be that AppArmor is blocking access. AFAICR, this was quite a common problem wih Akonadi on some distributions years ago.
Probably not the case here either, but you might try to disable AppArmor temporarily to rule that out.
I don't know Mageia, but if they use systemd (likely), this should do: "sudo systemctl stop apparmor.service".

Again, I appreciate the detail. Mageia 6 uses systemd but it does not use AppArmor, that's not a factor.

wolfi323 wrote:

adamsmark wrote:I checked the akonadiserverrc file. Does this look correct?

Yes.

Should there be an entry for "Host"?

No, unless you want to connect to a running mysql instance, and not have Akonadi start its own.

In that case, you'd also have to set "StartServer=false" though (and maybe remove the Options, I'm not sure about this).

That may actually be worth a try too, might workaround your problem. (.local/share/akonadi/db_data/ is not used at all then)
And that's what I'm using here (on this system) since years. (also for Amarok, which would normally run its own mysql server as well, so I would have 3 running...)

FTR, that's my akonadiserverrc:

Code: Select all

[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=localhost
Name=akonadi
Options=
Password=xxx
ServerPath=
StartServer=false
User=akonadi


Regarding your last post, I don't think that you can run akonadi_control manually.
You should use "akonadictl start" to start akonadi.

Again, much thanks for the details

I implemented the akonadi mysql configuration you described above. It improved things in terms of akonadiselftest returning errors. It allowed akonadi to register at Dbus, but it still doesn't allow the pim to start. This may be due to a package mismatch. I queried the rpm system for the packages installed and I have no idea what packages might be show stoppers here.

I can say that the control process is now running. That wasn't happening before.

Code: Select all

$ akonadictl status
Akonadi Control: running
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_googlecalendar_resource, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_invitations_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_tomboynotes_resource, akonadi_vcard_resource, akonadi_vcarddir_resource

At this point, akonadiselftest is showing two errors:

Code: Select all

Test 8:  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.

Code: Select all

Test 12:  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/madams/.local/share/akonadi/akonadiserver.error.old">/home/madams/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/madams/.local/share/akonadi/akonadiserver.error.old':
QSqlDatabasePrivate::removeDatabase: connection 'initConnection' is still in use, all queries will cease to work.Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

I would note that this error showed up after I moved the ib* files.

I'm not sure whether your error messages have any relevance or maybe are just caused by this.

"akonadiserver: symbol lookup error: akonadiserver: undefined symbol: _ZN7Akonadi8Protocol13HelloResponseC1ERK7QStringS4_i" might point to some incompatible packages though.
Check that all kdepim/akonadi related packages have the same version.

So, I'm not sure about this. versions are kind of all over the place.

Code: Select all

# rpm -qa |grep akonadi
lib64akonadi-calendar4-4.14.10-9.mga6
lib64akonadi-singlefileresource5-16.12.3-1.mga6
lib64akonadi-contact4-4.14.10-9.mga6
lib64kf5akonadixml5-16.12.3-1.mga6
lib64kf5akonadimime5-16.12.3-1.mga6
akonadi-16.08.3-1.mga6
lib64kf5akonadisearchdebug5-16.12.3-1.mga6
akonadiconsole-16.08.3-1.mga6
akonadi-import-wizard-16.12.3-1.mga6
akonadi-kde-16.08.3-1.mga6
lib64kf5akonadinotes5-16.12.3-1.mga6
lib64kf5akonadisearchcore5-16.08.3-1.mga6
lib64kf5akonadiwidgets5-16.12.3-1.mga6
lib64kf5akonadisearchxapian5-16.08.3-1.mga6
lib64kf5akonadisearchpim5-16.12.3-1.mga6
lib64akonadiprotocolinternals1-1.13.0-10.mga6
lib64kf5akonadiagentbase5-16.12.3-1.mga6
lib64akonadi-filestore5-16.12.3-1.mga6
lib64kf5akonadicore5-16.12.3-1.mga6
lib64kf5akonadicalendar5-16.12.3-1.mga6
lib64akonadi-kde4-4.14.10-14.mga6
akonadi-contacts-16.12.3-1.mga6
akonadi-mime-16.08.3-1.mga6
lib64kf5akonadicontact5-16.12.3-1.mga6
lib64akonadiprivate5-16.12.3-1.mga6
lib64akonadi-kmime4-4.14.10-9.mga6
akonadi-search-16.08.3-1.mga6

Code: Select all

# rpm -qa |grep kdepim
kdepim-runtime-handbook-16.12.3-1.mga6
kdepim-apps-libs-16.12.3-1.mga6
lib64kf5libkdepim5-16.12.3-1.mga6
lib64kf5kdepimdbusinterfaces5-16.12.3-1.mga6
libkdepim-16.12.3-1.mga6
kdepim-core-16.08.3-1.mga6
kdepim-addons-16.12.3-1.mga6

Still working on it.

And I do appreciate the information.