This forum has been archived. All content is frozen. Please use KDE Discuss instead.

kmail error: Could not create collection INBOX resourceId:17

Page 1 of 1 (3 posts)

Tags: kmail, akonadi kmail, akonadi kmail, akonadi
(comma "," separated)
bagmeenot
Registered Member
Posts
9
Karma
0

kmail error: Could not create collection INBOX resourceId:17

Thu Dec 11, 2014 5:51 pm
For a couple of weeks kmail fails to retrieve emails for one of my accounts. I'm running an up to date archlinux with kmail version 4.14.3

The process fails with this error message:
error: Could not create collection INBOX resourceId:17


I launched akonaditray to get to akonadi server configuration to run the self-test report.
The full text report is on pastebin at http://pastebin.com/ZEVe3FNU

I believe the relevant error message is this one :
akonadi database error code: 1062 Duplicate entry for key


Below is the edited report showing only the tests giving errors.
Akonadi Server Self-Test Report
===============================

Test 1: SUCCESS
--------
Test 2: SUCCESS
--------
Test 3: SUCCESS
--------
Test 4: SUCCESS
--------
Test 5: ERROR
--------

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

File content of '/home/user/.local/share/akonadi/db_data/mysql.err':
141210 21:32:47 [Warning] You need to use --log-bin to make --binlog-format work.
2014-12-10 21:32:47 7f712b986780 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.
141210 21:32:47 [Note] InnoDB: Using mutexes to ref count buffer pool pages
141210 21:32:47 [Note] InnoDB: The InnoDB memory heap is disabled
141210 21:32:47 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
141210 21:32:47 [Note] InnoDB: Memory barrier is not used
141210 21:32:47 [Note] InnoDB: Compressed tables use zlib 1.2.8
141210 21:32:47 [Note] InnoDB: Using Linux native AIO
141210 21:32:47 [Note] InnoDB: Using CPU crc32 instructions
141210 21:32:47 [Note] InnoDB: Initializing buffer pool, size = 80.0M
141210 21:32:47 [Note] InnoDB: Completed initialization of buffer pool
141210 21:32:47 [Note] InnoDB: Highest supported file format is Barracuda.
141210 21:32:47 [Note] InnoDB: 128 rollback segment(s) are active.
141210 21:32:47 [Note] InnoDB: Waiting for purge to start
141210 21:32:47 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 66596227123
141210 21:32:47 [Note] Plugin 'FEEDBACK' is disabled.
141210 21:32:47 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
141210 21:32:47 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
141210 21:32:47 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
141210 21:32:47 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
141210 21:32:47 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
141210 21:32:47 [Note] Reading of all Master_info entries succeded
141210 21:32:47 [Note] Added new Master_info '' to hash table
141210 21:32:47 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.0.15-MariaDB' socket: '/tmp/akonadi-user.aO5CDH/mysql.socket' port: 0 MariaDB Server
2014-12-10 21:32:48 7f712b8f2700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.

Test 6: SUCCESS
--------
Test 7: SUCCESS
--------
Test 8: SUCCESS
--------
Test 9: SUCCESS
--------
Test 10: SUCCESS
--------
Test 11: SUCCESS
--------
Test 12: SKIP
--------
Test 13: SUCCESS
--------
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/user/.local/share/akonadi/akonadiserver.error'>/home/user/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/user/.local/share/akonadi/akonadiserver.error':
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"

*SNIP* Same error repeated again and again *SNIP*


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

File content of '/home/user/.local/share/akonadi/akonadiserver.error.old':
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"

*SNIP* Same error repeated again and again *SNIP*


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/user/.local/share/akonadi/akonadi_control.error'>/home/user/.local/share/akonadi/akonadi_control.error</a>.

File content of '/home/user/.local/share/akonadi/akonadi_control.error':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" 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/user/.local/share/akonadi/akonadi_control.error.old'>/home/user/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/home/user/.local/share/akonadi/akonadi_control.error.old':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!
bagmeenot
Registered Member
Posts
9
Karma
0

Re: kmail error: Could not create collection INBOX resourceI

Tue Dec 16, 2014 10:43 am
Would deleting the whole database work around this duplicate entry error ?
Am I right to believe that I will not lose my mail by deleting this akonadi database ?
Will the database be recreated automatically ?
What is the recommended way to delete an akonadi database ?
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: kmail error: Could not create collection INBOX resourceI

Tue Dec 16, 2014 7:52 pm
I'm guessing the right query will fix it, but I'm not sure which one. I'll ask someone knowledgeable about it.

"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python

Page 1 of 1 (3 posts)

Bookmarks


Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]