[Kde-pim] How to Archive Folder in kmail when when database is corrupted?
Vylaern Vylaern
vylaern at gmail.com
Wed Jan 14 10:41:24 GMT 2015
>In case of inconsistencies
>akonadictl fsck
Hi,
I did akonadictl fsck - nothing happened - and I cannot still Archive many
folders.
What to do next?
I use kmail 4.14.3 now and bellow is Akonadi Report - maybe this will be
useful?
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/ryszard/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-ryszard.mpn79b/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.6.22 for Linux on
x86_64 (Source distribution)
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a
href='/home/ryszard/.local/share/akonadi/db_data/mysql.err'>/home/ryszard/.local/share/akonadi/db_data/mysql.err</a>'
contains errors.
File content of '/home/ryszard/.local/share/akonadi/db_data/mysql.err':
2015-01-14 11:24:55 14176 [Warning] Buffered warning: Changed limits:
max_open_files: 1024 (requested 5000)
2015-01-14 11:24:55 14176 [Warning] Buffered warning: Changed limits:
max_connections: 214 (requested 256)
2015-01-14 11:24:55 7f7a01e58740 InnoDB: Warning: Using
innodb_additional_mem_pool_size is DEPRECATED. This option may be removed
in future releases, together with the option innodb_use_sys_malloc and with
the InnoDB's internal memory allocator.
2015-01-14 11:24:55 14176 [Note] InnoDB: Using atomics to ref count buffer
pool pages
2015-01-14 11:24:55 14176 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-14 11:24:55 14176 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2015-01-14 11:24:55 14176 [Note] InnoDB: Memory barrier is not used
2015-01-14 11:24:55 14176 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-01-14 11:24:55 14176 [Note] InnoDB: Using Linux native AIO
2015-01-14 11:24:55 14176 [Note] InnoDB: Using CPU crc32 instructions
2015-01-14 11:24:55 14176 [Note] InnoDB: Initializing buffer pool, size =
80.0M
2015-01-14 11:24:55 14176 [Note] InnoDB: Completed initialization of buffer
pool
2015-01-14 11:24:55 14176 [Note] InnoDB: Highest supported file format is
Barracuda.
2015-01-14 11:24:56 14176 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-14 11:24:56 14176 [Note] InnoDB: Waiting for purge to start
2015-01-14 11:24:56 14176 [Note] InnoDB: 5.6.22 started; log sequence
number 4112777812
2015-01-14 11:24:56 14176 [Note] RSA private key file not found:
/home/ryszard/.local/share/akonadi/db_data//private_key.pem. Some
authentication plugins will not work.
2015-01-14 11:24:56 14176 [Note] RSA public key file not found:
/home/ryszard/.local/share/akonadi/db_data//public_key.pem. Some
authentication plugins will not work.
2015-01-14 11:24:56 14176 [Warning] Can't open and lock time zone table:
Table 'mysql.time_zone_leap_second' doesn't exist trying to live without
them
2015-01-14 11:24:56 14176 [ERROR] Can't open and lock privilege tables:
Table 'mysql.servers' doesn't exist
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'cond_instances' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_current' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_history' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_history_long' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_host_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_instance' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_user_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_by_account_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_waits_summary_global_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'file_instances' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'file_summary_by_event_name' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'file_summary_by_instance' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'host_cache' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'mutex_instances' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'objects_summary_global_by_type' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'performance_timers' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'rwlock_instances' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'setup_actors' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'setup_consumers' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'setup_instruments' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'setup_objects' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'setup_timers' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'table_io_waits_summary_by_table' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'table_lock_waits_summary_by_table' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'threads' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_current' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_history' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_history_long' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_summary_by_thread_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_summary_by_account_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_summary_by_user_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_summary_by_host_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_stages_summary_global_by_event_name' has the
wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_current' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_history' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_history_long' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_by_thread_by_event_name'
has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_by_account_by_event_name'
has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_by_user_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_by_host_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_global_by_event_name' has
the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'events_statements_summary_by_digest' has the wrong
structure
2015-01-14 11:24:56 14176 [ERROR] Native table 'performance_schema'.'users'
has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'accounts' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table 'performance_schema'.'hosts'
has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'socket_instances' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'socket_summary_by_instance' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'socket_summary_by_event_name' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'session_connect_attrs' has the wrong structure
2015-01-14 11:24:56 14176 [ERROR] Native table
'performance_schema'.'session_account_connect_attrs' has the wrong structure
2015-01-14 11:24:56 14176 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.22' socket: '/tmp/akonadi-ryszard.mpn79b/mysql.socket'
port: 0 Source distribution
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."collectionattributetable" but the
required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."collectionmimetyperelation" but
the required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."collectionpimitemrelation" but
the required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."collectiontable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."flagtable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."mimetypetable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:57 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."parttable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."parttypetable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."pimitemflagrelation" but the
required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:58 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."pimitemtable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."pimitemtagrelation" but the
required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."resourcetable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."schemaversiontable" but the
required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."tagattributetable" but the
required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."tagremoteidresourcerelationtable"
but the required system tables mysql.innodb_table_stats and
mysql.innodb_index_stats are not present or have unexpected structure.
Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."tagtable" but the required system
tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Table
"mysql"."innodb_table_stats" not found.
2015-01-14 11:24:59 7f79f12dd700 InnoDB: Error: Fetch of persistent
statistics requested for table "akonadi"."tagtypetable" but the required
system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not
present or have unexpected structure. Using transient stats instead.
Test 6: SUCCESS
--------
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at <a
href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.
File content of '/usr/share/config/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:1M)
# Deprecated in MySQL >= 5.6.3
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_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/ryszard/.local/share/akonadi/mysql.conf'>/home/ryszard/.local/share/akonadi/mysql.conf</a>
and is readable.
File content of '/home/ryszard/.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 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:1M)
# Deprecated in MySQL >= 5.6.3
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_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 '/usr/bin/akonadictl' to control the Akonadi server
was found and could be executed successfully.
Result:
Akonadi 1.13.0
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: SUCCESS
--------
Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically
indicates it is operational.
Test 12: SKIP
--------
Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if
the protocol version meets the requirements.
Test 13: SUCCESS
--------
Resource agents found.
Details: At least one resource agent has been found.
Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
folderarchiveagent.desktop
followupreminder.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to
'/usr/share:/usr/local/share:/usr/share'
Test 14: 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/ryszard/.local/share/akonadi/akonadiserver.error'>/home/ryszard/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/ryszard/.local/share/akonadi/akonadiserver.error':
ItemRetrieverException : Unable to retrieve item from resource:
<html>Invalid item retrieved</html>
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/ryszard/.local/share/akonadi/akonadiserver.error.old'>/home/ryszard/.local/share/akonadi/akonadiserver.error.old</a>.
File content of
'/home/ryszard/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!
Test 16: ERROR
--------
Current Akonadi control error log found.
Details: The Akonadi control process reported errors during its current
startup. The log can be found in <a
href='/home/ryszard/.local/share/akonadi/akonadi_control.error'>/home/ryszard/.local/share/akonadi/akonadi_control.error</a>.
File content of '/home/ryszard/.local/share/akonadi/akonadi_control.error':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder"
could not be found!
Executable "akonadi_folderarchive_agent" for agent
"akonadi_folderarchive_agent" could not be found!
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/ryszard/.local/share/akonadi/akonadi_control.error.old'>/home/ryszard/.local/share/akonadi/akonadi_control.error.old</a>.
File content of
'/home/ryszard/.local/share/akonadi/akonadi_control.error.old':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder"
could not be found!
Executable "akonadi_folderarchive_agent" for agent
"akonadi_folderarchive_agent" could not be found!
D-Bus session bus went down - quitting
On Sat, Jan 10, 2015 at 7:07 PM, Vylaern Vylaern <vylaern at gmail.com> wrote:
> First: The database should not get corrupted due to a migration.
>> Whether the database has any issue could be determined by looking at logs.
>> Look for anything special in
>> - ~/.xsession-errors
>> - ~/.local/share/akonadi/db_data/mysql.err
>> - ~/.local/share/akonadi/akonadi*.log
>>
> I do not have anything from above, but I have:
> .local/share/akonadi/akonadiserver.error
> ItemRetrieverException : Unable to retrieve item from resource:
> <html>Invalid item retrieved</html>
> ItemRetrieverException : Unable to retrieve item from resource:
> <html>Invalid item retrieved</html>
>
>
>> In case of inconsistencies
>> akonadictl fsck
>> may help
>> (but make a backup of your setup first!)
>
> How to make a backup?
>
>
>> You didn´t write what type of account you use. If its POP3, mails should
>> all
>> be in a local maildir. Where is likely visible within:
>> martin at merkaba:~/.kde/share/config> cat akonadi_maildir_resource_0rc
>> [General]
>> Path[$e]=$HOME/.local/share/local-mail
>> TopLevelIsContainer=true
>>
> I use POP3 and know its I am trying to solve it from a year ago:
> https://forum.kde.org/viewtopic.php?f=215&t=117689
> and admin form kde forum advised me to contact KDE PIM developer
>
> But have a look on this:
>
> You have some listings bellow. And you can see, there are some strange
> things here - it means folders and files in file-system in some places are
> different than in kmail.
>
> First example bellow - listing of (.local-mail). As you can see (listing
> 1), there is .sent-mail.directory. I keep there (in kmail, in sent-mail
> folder) my all old emails form last years, every year in one folder - 2006,
> 2007, 2008... (listing 2). In listing 3 you can see whats inside 2006
> folder, but all of subfolder of 2006 (cur, new, temp) are empty. Even du
> command says they are empty (see listing 4), but in compare du command for
> 2007 folder (see listing 5) says there is 53M of messages (instead of 4.3k
> for 2006). In reality, in kmail in sent-mail/2006 folder there are 504
> emails! Even akonadi console says so (should be 8.5M of messages):
> http://img837.imageshack.us/img837/3773/livu.jpg
> So where are those emails in real file system if 2006 folder is empty?
>
> I have some other examples like that - eg. I have a folder (in kmail)
> with 5 subfolder, and 100's other sub-sub-folder and over 1000's emails -
> but in file system (.inbox.directory) the same folder is empty, there is
> nothing appart empty (cur, new, temp) folders. Rest of system looks fine
> this just happed for few folder and few thousands emails. So this is reason
> I thinks there something wrong with data base.
>
> Listing 1
> ~/.local/share/local-mail $ ls -la
> total 48
> drwxr-xr-x 12 me me 4096 Apr 7 09:07 .
> drwxr-xr-x 18 me me 4096 Sep 30 22:03 ..
> drwxr-xr-x 5 me me 4096 Apr 7 09:07 drafts
> drwxr-xr-x 5 me me 4096 Feb 11 2013 import
> drwxr-xr-x 4 me me 4096 Feb 12 2013 .import.directory
> drwxr-xr-x 5 me me 4096 Feb 10 2013 inbox
> drwxr-xr-x 25 me me 4096 Sep 27 23:04 .inbox.directory
> drwxr-xr-x 5 me me 4096 Feb 10 2013 outbox
> drwxr-xr-x 5 me me 4096 Feb 10 2013 sent-mail
> drwxr-xr-x 10 me me 4096 Feb 12 2013 .sent-mail.directory
> drwxr-xr-x 5 me me 4096 Apr 7 09:07 templates
> drwxr-xr-x 5 me me 4096 Apr 7 09:07 wastebin
>
> Listing 2
> $ ls -la
> total 40
> drwxr-xr-x 10 me me 4096 Feb 12 2013 .
> drwxr-xr-x 12 me me 4096 Apr 7 09:07 ..
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2006
>
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2007
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2008
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2009
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2010
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2011
> drwxr-xr-x 5 me me 4096 Feb 12 2013 2012
> drwxr-xr-x 5 me me 4096 Feb 11 2013 2013
>
> Listing 3
> ~/.local/share/local-mail/.sent-mail.directory/2006 $ ls -la
> total 20
> drwxr-xr-x 5 me me 4096 Feb 12 2013 .
> drwxr-xr-x 10 me me 4096 Feb 12 2013 ..
> drwxr-xr-x 2 me me 4096 Feb 12 2013 cur
> drwxr-xr-x 2 me me 4096 Feb 12 2013 new
> drwxr-xr-x 2 me me 4096 Feb 12 2013 tmp
>
> Listing 4
> ~/.local/share/local-mail/.sent-mail.directory/2006 $ du --si
> 4.1k ./cur
> 4.1k ./tmp
> 4.1k ./new
> 17k .
>
> Listing 5
> ~/.local/share/local-mail/.sent-mail.directory/2007 $ du --si
> 4.1k ./cur
> 4.1k ./tmp
> 53M ./new
> 53M .
>
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list