[kdepim-users] Trouble starting konadi database.

Sat May 28 23:54:15 BST 2016

Ingo,
Thank you for the suggestion. I tried that but I still have a problem. 
When I run akonadiselftest it complains about mysql server. If I do the 
command  "service --status-all" it shows the mysql server is running. 
See below: I've also tried to reinstall mysql and when I run 
akonadiselftest still has the same results. Test #3 fails and says it 
can't find the mysql server so I searched for it (mysqld) and it lives 
in /usr/sbin/mysqld. I opened a terminal and echo $PATH. That returns:

/opt/android-sdk-linux/tools:/opt/android-sdk-linux/platform-tools:/home/beatty/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Thanks in advance for any help you may provide,
John B.

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 '/home/beatty/.config/akonadi/akonadiserverrc' could not be opened

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

MySQL server not found.
Details: You have currently configured Akonadi to use the MySQL server ''.
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:  ERROR
--------

Executing the MySQL server failed.
Details: Executing the MySQL server '' failed with the following error 
message: ''

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/beatty/.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/xdg/akonadi/mysql-global.conf">/etc/xdg/akonadi/mysql-global.conf</a>.

File content of '/etc/xdg/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 at 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

# KUBUNTU:
# Unset the export dir check as only the full mysql-server package 
creates it
secure_file_priv=

# KUBUNTU:
# workaround for 5.7 being more strict with column types
# (reverts to 5.6 behavior)
sql_mode=NO_ENGINE_SUBSTITUTION

[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 5.1.51

Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which 
typically means it was not started or encountered a fatal error during 
startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which 
typically means it was not started or encountered a fatal error during 
startup.

Test 12:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check 
if the protocol version meets the requirements.

Test 13:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable 
without at least one. This usually means that no resource agents are 
installed or that there is a setup problem. The following paths have 
been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS 
environment variable is set to 
'/usr/share/akonadi/agents:/usr/share/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'; 
make sure this includes all paths where Akonadi agents are installed.

Environment variable XDG_DATA_DIRS is set to 
'/usr/share/akonadi/agents:/usr/share/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'

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

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

Test 16:  SUCCESS
--------

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

Test 17:  SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during 
its previous startup.

On 05/26/2016 02:21 PM, Ingo Klöcker wrote:
> On Thursday 26 May 2016 16:03:27 Anders Lund wrote:
>> Hi John,
>>
>> Just remove all the akonadi data and configuration from your system
>> (don't forget to back up), after all akonadi is not where your actual
>> data is kept.
> That's not necessarily true. Some messages might only be stored in
> Akonadi's database, e.g. until recently moving multiple messages from an
> IMAP folder to a local maildir folder only wrote one of the moved
> messages to the physical location of the local maildir folder. (FWIW,
> copying multiple messages from IMAP to local works as expected.)
>
> I encountered similar problems with moving/copying messages between
> different IMAP accounts.
>
> Moreover, I think that some (probably dispensable) meta information
> about the messages (e.g. replied, forwarded) is only stored in Akonadi.
> At least, for some types of accounts, e.g. maildir.
>
> Consequently, blindly purging all Akonadi data can result in data loss
> and is definitely not a recommended procedure for fixing problems with
> Akonadi.
>
>
> Regards,
> Ingo
>
>
> _______________________________________________
> KDE PIM users mailing list
> Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20160528/c5b5b12d/attachment.html>