MySQL 5.1.14 SLOW !!!!
Dear All,
i am using CF7.0.1 with MySQL 5.0.14 and JDBC connector
5.0.4. However, it is slow !!
For example: CF need 20 ++ seconds to display a very simple
query result if i am using MySQL 5.0.14 with JDBC 5.0.4.But if i
changed the JDBC connector to ver 3.0.17, CF works as usual.....
Any one know what is the problem?
Now, it's sure, libmysqlclient need to be fixed and qt rebuiled:
#include <QApplication>
#include <QSqlDatabase>
#include <QSqlError>
#include <QDebug>
int main( int argc, char *argv[] )
QApplication app( argc, argv );
QSqlDatabase defaultDB = QSqlDatabase::addDatabase ( "QMYSQL3" );
defaultDB.setDatabaseName( "akonadi");
defaultDB.setUserName( "******" );
defaultDB.setPassword( "*******" );
defaultDB.setHostName( "localhost" );
if ( defaultDB.open() ) {
// Database successfully opened; we can now issue
qDebug () << "ok";
else {
qDebug() << defaultDB.lastError().databaseText().toLatin1();
return 0;
result:
"Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)"
Last edited by gnumdk (2009-11-19 01:22:39)
Similar Messages
-
Mail, Server Admin, MySQL running very, very slow
Hi all,
I have this Leopard Server on a Mac Mini and I experience some big bottlenecks on mail services (especially webmail), Server Admin connections (both local and remote), and also connections with mySQL clients (remote). Local MySQL is working fine. It is not the same for mail and Server Admin. They are very slow also for local connections. Any idea? Hint: I'm using a USB-ethernet adapter (from Apple) for my public IP's (I have 2 of them) and I use built-in ethernet for local network. I've switched them, I tried only with the built-in ethernet... no change. Please help... my enthusiasm about this server solution is getting lower and lower... Thank you very muchpterobyte wrote:
Have a look at system.log and mailaccess.log for clues to begin with.
Server Admin is usually slow (locally and remotely) when the DNS (forward and reverse) setup is not correct.
Since mySQL seems to have only problems when used remotely, I'd look at bandwidth, routers and switches involved.
Is mail only slow when used via webmail or via any IMAP client?
You're a genius as usually
It seems that I removed my reverse zone accidentally... I didn't even think to look at DNS setting before you told me... Thank you very much -
Performance over DG from mysql to oracle very slow for inserts
configured het services over gateway from oracle 11.2.0.4 to mysql 5.6
Have a table I want to pull over into oracle. 1000 rows.
On mysql : create view vw_mysql_t1 as select columns from my_mysql_table.
On Oracle: create view vw_ora as select columns from vw_mysql_t1@mysql_link
On oracle: select * from vw_ora data returns data in 3-4 seconds.
however, try an insert to get the data over
insert into a_table_on_oracle
(select * from vw_ora)
takes 11-12 minutes.
create table as or insert into same performance. Tried just inserting 1 row and same performance 11-12 minutes. any ideas?cant seem to get the trace file to generate. any ideas, I have the config as below, the gateway is working, I can select data no problem from table@dcv , just performance is terrible
logfile not in $ORACLE_HOME/hs/log
or
/tmp
this is my tns
dcv =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = tcp)(HOST = <IP of server>)(PORT = 1521))
(CONNECT_DATA =
(SID = dcv)
(HS = OK)
this is my init file
# HS init parameters
HS_FDS_CONNECT_INFO=dcv
HS_FDS_TRACE_LEVEL=255
HS_FDS_SHAREABLE_NAME = /usr/lib64/libmyodbc5a.so
HS_RPC_FETCH_SIZE=50000
HS_ROWID_CACHE_SIZE=10000
#HS_LONG_PIECE_TRANSFER_SIZE=1024
HS_LONG_PIECE_TRANSFER_SIZE=65536
HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P15 ## The Oracle RDBMS is using a Unicode characterset [ID 756186.1]
HS_FDS_FETCH_ROWS=1 ## This is select int datatype
HS_FDS_SQLLEN_INTERPRETATION=32 ## This is to select NULL values via DB Link [ID 554409.1]
# ODBC specific environment variables
set ODBCINI=/etc/odbc.ini
more /etc/odbc.ini
[dcv]
Driver = /usr/lib64/libmyodbc5a.so
SERVER = <IP of mysql server>
PORT = 3306
USER = un
Password = pw
Database = dcv
OPTION = 3
CHARSET = latin1
[ODBC]
TRACE = ON # also tried 0 and 1 and DEBUG and USER
TraceFile = /tmp/odbc.trace
10:11:19 SQL> select count(*) from "vw_t1"@dcv;
COUNT(*)
24794
Elapsed: 00:00:00.23
10:11:45 SQL>
10:11:57 SQL>
10:11:57 SQL>
10:11:57 SQL>
10:11:57 SQL>
10:11:58 SQL> create table backup_data.delete_me as
10:11:59 2 select * from
10:11:59 3 "vw_t1"@dcv;
Table created.
Elapsed: 00:09:47.07
10:21:49 SQL>
Theres around 130 columns, varchars, numerics and floats. Is there a conversion going on that would take that long? -
Akonadi database error code: 1062 Duplicate entry for key
Since my email provider migrated their webmail platform, I keep getting an error each time kmail attempts to get emails from their imap server: could not create collection INBOX resourceid: 17
I double checked the provided imap settings have not changed and are correct : imap.laposte.net port 993 using SSL/TLS
As you can see in the pasted akonadi self-test report below, I have a few errors related to innodb, the absence of mysql tables in local/share/akonadi/db_data/ and the table performance_schema having the wrong structure. Those have been there for several months but I've been unable to fix them and I didn't care because my email was working. I suppose they are unrelated to my current issues.
Any help I can get is much welcome.
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/the_user/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-the_user.kKTLSR/mysql.socket"
ServerPath=/usr/bin/mysqld
StartServer=true
User=
Password=
[Debug]
Tracer=null
[QPSQL]
StartServer=true
Name=akonadi
Host=
User=
Password=
Port=5432
[SQLITE]
Name=akonadi
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/bin/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/bin/mysqld Ver 10.0.14-MariaDB-log for Linux on x86_64 (MariaDB Server)
Test 5: ERROR
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/the_user/.local/share/akonadi/db_data/mysql.err'>/home/the_user/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/the_user/.local/share/akonadi/db_data/mysql.err':
141129 9:34:33 [Warning] You need to use --log-bin to make --binlog-format work.
2014-11-29 09:34:33 7f5b81d0b780 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.
141129 9:34:33 [Note] InnoDB: Using mutexes to ref count buffer pool pages
141129 9:34:33 [Note] InnoDB: The InnoDB memory heap is disabled
141129 9:34:33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
141129 9:34:33 [Note] InnoDB: Memory barrier is not used
141129 9:34:33 [Note] InnoDB: Compressed tables use zlib 1.2.8
141129 9:34:33 [Note] InnoDB: Using Linux native AIO
141129 9:34:33 [Note] InnoDB: Using CPU crc32 instructions
141129 9:34:33 [Note] InnoDB: Initializing buffer pool, size = 80.0M
141129 9:34:33 [Note] InnoDB: Completed initialization of buffer pool
141129 9:34:33 [Note] InnoDB: Highest supported file format is Barracuda.
141129 9:34:33 [Note] InnoDB: The log sequence numbers 66340678877 and 66340678877 in ibdata files do not match the log sequence number 66344113222 in the ib_logfiles!
141129 9:34:33 [Note] InnoDB: Database was not shutdown normally!
141129 9:34:33 [Note] InnoDB: Starting crash recovery.
141129 9:34:33 [Note] InnoDB: Reading tablespace information from the .ibd files...
141129 9:34:33 [Note] InnoDB: Restoring possible half-written data pages
141129 9:34:33 [Note] InnoDB: from the doublewrite buffer...
141129 9:34:34 [Note] InnoDB: 128 rollback segment(s) are active.
141129 9:34:34 [Note] InnoDB: Waiting for purge to start
141129 9:34:34 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 66344113222
141129 9:34:34 [Note] Plugin 'FEEDBACK' is disabled.
141129 9:34:34 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
141129 9:34:34 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
141129 9:34:34 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
141129 9:34:34 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
141129 9:34:34 [Note] Reading of all Master_info entries succeded
141129 9:34:34 [Note] Added new Master_info '' to hash table
141129 9:34:34 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.0.14-MariaDB' socket: '/tmp/akonadi-the_user.kKTLSR/mysql.socket' port: 0 MariaDB Server
2014-11-29 09:34:34 7f5b81c77700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
141129 15:14:56 [Warning] Aborted connection 58 to db: 'akonadi' user: 'the_user' host: '' (Unknown error)
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 <[email protected]>
[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: SUCCESS
MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is readable at <a href='/home/the_user/.config/akonadi/mysql-local.conf'>/home/the_user/.config/akonadi/mysql-local.conf</a>
File content of '/home/the_user/.config/akonadi/mysql-local.conf':
# workaround fix for akonadi db error after server upgrade
# http://forum.kde.org/viewtopic.php?f=215&t=101004
[mysqld]
binlog_format=row
Test 8: SUCCESS
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/the_user/.local/share/akonadi/mysql.conf'>/home/the_user/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/the_user/.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 <[email protected]>
[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
# workaround fix for akonadi db error after server upgrade
# http://forum.kde.org/viewtopic.php?f=215&t=101004
[mysqld]
binlog_format=row
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
facebookresource.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
kolabresource.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/share:/usr/local/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/the_user/.local/share/akonadi/akonadiserver.error'>/home/the_user/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/the_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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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/the_user/.local/share/akonadi/akonadiserver.error.old'>/home/the_user/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/the_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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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)"
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/the_user/.local/share/akonadi/akonadi_control.error'>/home/the_user/.local/share/akonadi/akonadi_control.error</a>.
File content of '/home/the_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/the_user/.local/share/akonadi/akonadi_control.error.old'>/home/the_user/.local/share/akonadi/akonadi_control.error.old</a>.
File content of '/home/the_user/.local/share/akonadi/akonadi_control.error.old':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!After Upload you can delete the Duplicates comparing the employee Id.
It Will be Possible only when you use OLE and read the file records line by Line. I am not sure of the error Handling with OLE control. It may lead to some performance issues.. -
[SOLVED] Can't make Akonadi server / Nepomuk service run
I'm currently running KDE SC 4.9 on Arch Linux x86_64, system fully up to date.
My laptop's HD went dead some days ago so I had to restore my system from a 2-weeks old backup; I usually use fsarchiver to backup root partition and 7z to compress ~/.kde4 and ~/.config so this way I'm covered up about these kind of things.
So after restoring my system and home folder I did a full upgrade (nearly a gigabyte of downloads) and while most things seems to work well I found that Nepomuk isn't running, when I try to start it manually I have this error message:
"Failed to start the desktop search service (Nepomuk). The settings have been saved and will be used the next time the server is started."
Going back to the wiki I did my homework re-configuring Akonadi but so far I can't make Nepomuk run.
This is what I have:
~/.config/akonadi/akonadiserverrc
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=localhost
ServerPath=/usr/bin/mysqld
StartServer=true
User=akonadiuser
Password=akonadiuser
Options="UNIX_SOCKET=/home/msx/.local/share/akonadi/socket-heybeavis/mysql.socket"
[Debug]
Tracer=null
The database is already created and configured:
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| akonadi
| mysql
| owncloud
| performance_schema |
+--------------------+
5 rows in set (0.00 sec)
and the ~/.config/akonadi/mysql-local.conf is in place:
~ $ cat ~/.config/akonadi/mysql-local.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 <[email protected]>
[mysqld]
# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
sql_mode=strict_trans_tables
# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
[client]
default-character-set=utf8
Now, when I do restart Akonadi server I got:
~ $ akonadictl restart
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/usr/local/bin", "/usr/bin", "/bin", "/usr/local/sbin", "/usr/sbin", "/sbin", "/usr/bin/vendor_perl", "/usr/bin/core_perl", "/usr/bin/msx", "/usr/lib/colorgcc/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
~ $ akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
Nepomuk Query Server not available
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/usr/local/bin", "/usr/bin", "/bin", "/usr/local/sbin", "/usr/sbin", "/sbin", "/usr/bin/vendor_perl", "/usr/bin/core_perl", "/usr/bin/msx", "/usr/lib/colorgcc/bin")
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
"/usr/bin/akonadi_nepomuk_feeder(13892)" Soprano: "Could not connect to server at /tmp/ksocket-msx/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(13892)" Soprano: "Could not connect to server at /tmp/ksocket-msx/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(13892)" Soprano: "Could not connect to server at /tmp/ksocket-msx/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(13892)" Soprano: "Could not connect to server at /tmp/ksocket-msx/nepomuk-socket (No such file or directory)"
search paths: ("/home/msx/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/home/msx/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/msx/.kde4/lib/kde4/", "/usr/lib/kde4/")
AkonadiAgentServer(13913)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
AkonadiAgentServer(13913)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Please correct me if I'm wrong but seems Akonadi can't/don't create the resource needed by Nepomuk, right?
"/usr/bin/akonadi_nepomuk_feeder(13892)" Soprano: "Could not connect to server at /tmp/ksocket-msx/nepomuk-socket (No such file or directory)"
Already raked the forums and the net but can't find anything of help :(
* UPDATE *
1.Further research shows akonadi database is empty so it seems Akonadi isn't connecting to MySQLd.
2. I created a new user to simplify research and found the very same problem when trying to activate Nepomuk: Failed to start the desktop search service (Nepomuk). The settings have been saved and will be used the next time the server is started.
From what I remember Akonadi/Nepomuk/Soprano were working well in previous KDE 4.8.4.
* UPDATE *
Solved after reinstalling all MySQL stack.
Regards,
Martin
Last edited by msx (2012-08-15 06:33:30)msx, please use [ code ]...[ /code ] tags (without the intervening spaces) around your listings. See: https://bbs.archlinux.org/help.php#bbcode
-
[SOLVED PAR/LY]kde 4.2 -- akonadi configuration + kmail crash problems
Hey guys,
Recently i decided to give kde 4.2 a try , (been using gnome for months) and after the update i have these two distinct (i think) problems with kmail.
When i run kmail , it tries to start akonadi server, which fails due to configuration issues (see below) . After that , when i try to send an email it *always* crashes. Here is the output either of the shell or the popup error dialog:
1) akonadi misconfiguration(?)
From the pop up
Akonadi Server Self-Test Report
===============================
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL, QODBC3, QODBC, QPSQL7, QPSQL.
Make sure the required driver is installed.
File '/akonadiserverrc' could not be opened
Test 2: ERROR
MySQL server not found.
Details: You currently have 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 locations varies depending on the distribution.
Test 3: ERROR
Executing the MySQL server failed.
Details: Executing the MySQL server '' failed with the following error message: ''
Test 4: SUCCESS
No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup into '/mysql.err'.
Test 5: 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 <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Test 6: SKIP
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
Test 7: ERROR
MySQL server configuration not found or not readable.
Details: The MySQL server configuration was not found or is not readable.
Test 8: SUCCESS
akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
Akonadi Control: running
Akonadi Server: stopped
Test 9: 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 10: 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 11: 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 12: 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:/usr/local/share:/opt/kde/share', make sure this includes all paths where Akonadi agents are installed to.
Directory listing of '/usr/share/akonadi/agents':
distlistresource.desktop
icalresource.desktop
imaplibresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
mailthreaderagent.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
strigifeeder.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/local/share:/opt/kde/share'
Test 13: SUCCESS
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 14: SUCCESS
No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.
Test 15: SUCCESS
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 16: SUCCESS
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
From the shell output:
kmail(14979) KWallet::Wallet::openWallet: Pass a valid windows to KWallet::Wallet::openWallet().
kres-migrator(14981)/libakonadi Akonadi::Control::Private::exec: Could not start/stop Akonadi!
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi/db_data" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.config/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
XdgBaseDirs::saveDir: failed to create directory ' "/root/.local/share/akonadi" '
kmail(14979)/kresources: Akonadi migration failed!
kmail(14979)/kresources: command was: ("kres-migrator", "--interactive-on-change", "--type", "contact", "--omit-client-bridge")
kmail(14979)/kresources: exit code: 0
kmail(14979)/kresources: stdout: ""
kmail(14979)/kresources: stderr: ""
QProcess: Destroyed while process is still running.
kmail(14979): No language dictionaries for the language: "en_US"
kmail(14979): No language dictionaries for the language: "en_US"
kmail(14979): No language dictionaries for the language: "en_US"
kmail(14979): No language dictionaries for the language: "en_US"
and
2) this is the output at the shell once i write a mail and i press send.
kmail: relocation error: /usr/lib/libgpgme++-pthread.so.2: symbol gpgme_cancel_async, version GPGME_1.1 not defined in file libgpgme-pthread.so.11 with link time reference
and a crash follows.
Well , i tried to manually create some of the directories, with no success. To be honest, i mostly care to fix this crashing issue since i cant send any email after the upgrade.Any pointers folks?
Cheers,
IMG
Last edited by IMG (2009-02-22 12:02:50)Hey toxygen,
thanks for the reply. No i am not using kdemod (actually never tried it, maybe i should try it some day) . The thing about turning akonadi off is that it is not that clear to me how to do it properly.
Looking around at System settings --> advanced --> Akonadi server configuration , it clearly states that akonadi server is not running (due to bad configuration). I dont see anything like "switch off Akonadi server" either.
Trying System settings--> advanced --> Kresources , it tries a couple of times to start the Akonadi server (fails ofcourse) , and then i get to the Kresources dialog. But i cant see anything there related to Akonadi, or something like "do not use Akonadi".
Also removing the package ignoring the dependencies with
pacman -Rd akonadi
has this result on shell
KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet().
kres-migrator: error while loading shared libraries: libakonadiprotocolinternals.so.1: cannot open shared object file: No such file or directory
kmail(23835)/kresources: Akonadi migration failed!
kmail(23835)/kresources: command was: ("kres-migrator", "--interactive-on-change", "--type", "contact", "--omit-client-bridge")
kmail(23835)/kresources: exit code: 127
kmail(23835)/kresources: stdout: ""
kmail(23835)/kresources: stderr: ""
So the kde still looks for it(expected). Btw it doesnt seem there to be a way to remove it without the -d option at pacman , since it is required by kdepimlibs , which in turn are required by many other kde packages.So how do you go about switching it off?
Another strange thing i noticed after googling about the issue is that usually if i get it right, the akonadi configuration files should be located at ~/.config/Akonadi , so why is it trying to do its stuff at /root/.config/akonadi in my machine ?? Am i somehow causing it to run as root?
IMG -
[SOLVED] KDE Akonadi nightmare
After a fresh KDE 4.4 install on top of freshly installed Arch, I discovered that Akonadi server fails to start, giving a number of errors, like mysql startup error and the subsequent failure of akonadi to register at dbus, error logs et cetera. Since the Arch installation is probably as vanilla as it gets, it seems to me that the Akonadi package is broken, which makes one wonder what the devs were thinking when they released it. I think I tried every proposed solution that Google has indexed on the web but none worked. Then I found the answer for my problem. I have written it out below in case it is of use to somebody else.
1. In my case, the problem vaguely gave signs of being a mysql problem. Pardus is the only distribution I know that makes Akonadi work (and if you don't want to follow the Arch way, it is the best KDE distribution IMHO), so I replaced the mysql-global.conf in two places - /usr/share/config/akonadi/mysql-global.conf and $HOME/.local/share/akonadi/mysql.conf. The conf file from Pardus is given below. But there is a small thing to remember: if you ran the akonadi server before, it is best to clean the $HOME/.local/share/akonadi directory. Copy the mysql-global.conf file into that directory after cleaning it and before trying to start the akonadi server again. There are only little differences between the stock arch conf and the one from Pardus and even though I forgot the output of the diff command, it seemed like the error had to do with some bad options passed.
2. The second problem seemed to be resources and it was solved by a suggestion I have found in this forum. In system settings, in the advanced tab, go to KDE resources. Create akonadi resources for contacts and calendar and set them as default. If you want to do something regarding the resources (set something else as default/export/import), you can do so after you successfully start the akonadi server from the akonaditray utility's configuration window. But first you need to be able to start it successfully.
After I did these, Akonadi server starts when I fire up Kontact with no errors. When trying to start it from akonaditray, it sometimes says the resource "outbox" cannot be found, but kmail handles the local outbox well and I have no special desire to start akonadi with akonaditray anyway.
Here is the mysql-global.conf from Pardus. If these suggestions don't work, you might want to check out a Pardus live cd to get other ideas because it is working well there unlike the kubuntu live cd.
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
# Based on advice by Kris Köhntopp <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=8M
# innodb_flush_log_at_trx_commit=2
Now, I can have a full mysql database to store my all 10-15 contacts. Hooray, I suppose.Yeah that was too short. I meant that if you go to systemsettings->Personal information->Kde resources then tab calendar and check that the configured akonadi resource for the google calendar is not read-only. But that seems to be irrelevant.
For me it works perfectly but I have installed it from git repository! -
Akonadi didn't start after login.
Error log:
Akonadi Server Self-Test Report
===============================
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL, QODBC3, QODBC, QPSQL7, QPSQL.
Make sure the required driver is installed.
File content of '/home/rpr/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false
[QMYSQL]
Name=akonadi
User=
Password=
Options="UNIX_SOCKET=/home/rpr/.local/share/akonadi/db_misc/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true
Host=
Test 2: SUCCESS
MySQL server found.
Details: You currently have 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 locations varies depending on the distribution.
Test 3: SUCCESS
MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.39 for pc-linux-gnu on i686 (Source distribution)
Test 4: ERROR
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/rpr/.local/share/akonadi/db_data/mysql.err'>/home/rpr/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/rpr/.local/share/akonadi/db_data/mysql.err':
091026 9:19:07 [Note] Plugin 'FEDERATED' is disabled.
091026 9:19:07 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb.html
091026 9:19:07 [ERROR] Plugin 'InnoDB' init function returned error.
091026 9:19:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
091026 9:19:07 [ERROR] Unknown/unsupported table type: innodb
091026 9:19:07 [ERROR] Aborting
091026 9:19:07 [Warning] Forcing shutdown of 2 plugins
091026 9:19:07 [Note] /usr/sbin/mysqld: Shutdown complete
Test 5: 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 <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Test 6: SUCCESS
MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is readable at <a href='/home/rpr/.config/akonadi/mysql-local.conf'>/home/rpr/.config/akonadi/mysql-local.conf</a>
File content of '/home/rpr/.config/akonadi/mysql-local.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 <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Test 7: SUCCESS
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/rpr/.local/share/akonadi/mysql.conf'>/home/rpr/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/rpr/.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 <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
# Based on advice by Kris Köhntopp <[email protected]>
[mysqld]
skip_grant_tables
skip_networking
# 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
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Test 8: 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.2.1
Test 9: 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 10: 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 11: 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 12: 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:/usr/local/share', make sure this includes all paths where Akonadi agents are installed to.
Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
distlistresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
microblog.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
strigifeeder.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/local/share'
Test 13: ERROR
Current Akonadi server error log found.
Details: The Akonadi server did report error during startup into <a href='/home/rpr/.local/share/akonadi/akonadiserver.error'>/home/rpr/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/rpr/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/rpr/.local/share/akonadi//mysql.conf", "--datadir=/home/rpr/.local/share/akonadi/db_data/", "--socket=/home/rpr/.local/share/akonadi/db_misc/mysql.socket")
stdout: ""
stderr: "091026 9:19:07 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.
091026 9:19:07 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.
exit code: 1
process error: "Unknown error"
0: akonadiserver(_Z11akBacktracev+0x35) [0x80526a5]
1: akonadiserver [0x8052b6e]
2: [0xb77e2400]
3: [0xb77e2424]
4: /lib/libc.so.6(gsignal+0x51) [0xb712f411]
5: /lib/libc.so.6(abort+0x182) [0xb7130c12]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0xb74686e4]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8053604]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x85) [0xb74f7fb5]
9: /usr/lib/libQtCore.so.4 [0xb7506c95]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb7508068]
11: akonadiserver(_ZN6QDebugD1Ev+0x43) [0x804d893]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x1a86) [0xb76b00b6]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x70) [0xb76b26e0]
14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x58) [0xb76b3a48]
15: akonadiserver(main+0x2c9) [0x804cf19]
16: /lib/libc.so.6(__libc_start_main+0xe6) [0xb711ba36]
17: akonadiserver [0x804cb81]
Test 14: ERROR
Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href='/home/rpr/.local/share/akonadi/akonadiserver.error.old'>/home/rpr/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/rpr/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/rpr/.local/share/akonadi//mysql.conf", "--datadir=/home/rpr/.local/share/akonadi/db_data/", "--socket=/home/rpr/.local/share/akonadi/db_misc/mysql.socket")
stdout: ""
stderr: "091026 9:19:06 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.
091026 9:19:06 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.
exit code: 1
process error: "Unknown error"
0: akonadiserver(_Z11akBacktracev+0x35) [0x80526a5]
1: akonadiserver [0x8052b6e]
2: [0xb76f4400]
3: [0xb76f4424]
4: /lib/libc.so.6(gsignal+0x51) [0xb7041411]
5: /lib/libc.so.6(abort+0x182) [0xb7042c12]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0xb737a6e4]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8053604]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x85) [0xb7409fb5]
9: /usr/lib/libQtCore.so.4 [0xb7418c95]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb741a068]
11: akonadiserver(_ZN6QDebugD1Ev+0x43) [0x804d893]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x1a86) [0xb75c20b6]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x70) [0xb75c46e0]
14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x58) [0xb75c5a48]
15: akonadiserver(main+0x2c9) [0x804cf19]
16: /lib/libc.so.6(__libc_start_main+0xe6) [0xb702da36]
17: akonadiserver [0x804cb81]
Test 15: SUCCESS
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 16: SUCCESS
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.Hi guys, I have the same problem.
How can I update the values??
Please help!!
Chinho -
MySQL very slow on Win 2000 Fast on Win XP Found a fix
Greetings,
I've recently rolled out an internal LabVIEW 8.5 application that works
with a MySQL database. Several of the PCs required an installer.
Although a few of them belonged to other LabVIEW developers in the
office and required only the .exe file to run.
After setting up the OBDC connector, the application works on all the
PCs. However, any calls to the database are brutally slow on the one
Windows 2000 machine.
I thought perhaps the problem might be due to the fact that the LabVIEW
program was compiled on a Windows XP machine. But even when I run the
connection test from the OBDC Data Source Configuration dialog, it
responds much slower on the Windows 2000 machine than any of the
Windows XP machines.
-------edit---------
While in the middle of drafting this post I happened upon some information on the MySQL forums.
Adding the following lines to the "my.ini" file in the MySQL Server 5.1 directory cleared the problem right up.
skip-host-cache
skip-name-resolve
All my clients are working fine now. Let the weekend begin!
Patrick AllenHave you checked your ethernet speed/duplex settings on the ethernet port and XP machine?
-
Please anyone with expirience in applets accessing MySQL Server!
I made a test with a loop code executing queries and got the following conclusion:
In media a query takes more than 2 seconds. I used PrepareStatement for better performance but it doesn�t make it better. I�ve heart about persistent connection. It�s realy faster? You know anything I could do for better performance? Obs.: When I ping my server the time answer is 200 ms. I�m from Brazil. But I think it sholdn�t make the mysql too slow as it is. Please help me.....
I�m very thank for ur help..
My java code:
public void ConectaBD()
try
Class.forName("com.mysql.jdbc.Driver").newInstance();
//Class.forName("org.gjt.mm.mysql.Driver").newInstance();
catch(Exception e)
System.out.println("Error: " + e);
try
con = DriverManager.getConnection("jdbc:mysql://labinfor.com.br/labinfor_codvirtual?user=labinfor_cliente&password=800091");
catch(SQLException e)
System.out.println("Error: " + e );
e.printStackTrace();
public void Logon()
java.util.Date start = new java.util.Date();
long startTime = start.getTime();
if (ValidaCPF(TFCPF.getText()))
queryLogon = "SELECT Nome FROM clientes WHERE CPF='" + TFCPF.getText().trim() + "' AND senha='" + TFSenha.getText() + "'";
int indCon=0;
Timer t = new Timer(1000, this);
t.start();
while(indCon<100)
Conecta();
try
stmt[indStmt] = con.createStatement();
rsLogon = stmt[indStmt].executeQuery(queryLogon);
Achou = "false";
while (rsLogon.next())
Achou = "true";
StrNome = rsLogon.getString(1);
LValidaCPF.setText("Bem-vindo " + StrNome);
TFCPF.disable();
TFSenha.disable();
BLogon.setLabel("Logoff");
System.out.println("delay["+indCon+"]= "+System.currentTimeMillis());
if (Achou == "false")
LValidaCPF.setText("CPF ou senha incorreto");
Desconecta();
catch(Exception e)
System.out.println("Error: " + e);
indCon+=1;
}Connection times of 1 to 5 seconds are normal. Pool your connections.
To understand why:
First, setting up a TCP/IP connection takes roughly 50% longer than a ping; a ping is one packet to the server and one packet back, a TCP/IP handshake to create a connection is one packet to the server, one back, and another to the server. Then you have a required brief wait before the connection is considered complete; we'll ignore the wait and call it .3 seconds for the TCP/IP handshake.
Second, the database has to go through the login process. Just sending the login request and response is yet another packet round trip; in your case, that's another .2 seconds in just network time alone. With MySQL, the login involves checking the security of the connection and the user; it often requires a reverse DNS lookup on the IP address of the client. Probably 4 or 5 tables have to be queried and a user environment is created within the server. The server work for the login might take .75 seconds, at a guess. Adding the network time makes this step .95 seconds or so.
Third, there's the time it takes to do the query itself; another network round trip; .2 second network round trip, plus maybe .1 second to run the query on the database, for a total of .3 seconds.
Fourth, there's the time it takes to tear down the TCP/IP connection on connection close. That involves 4 packets, 2 round-trips, so add another .4 seconds.
Adding it all up, you get .3 + .95 + .3 + .4 = 1.95 seconds, of which .3 is your SQL query (network and DB time), .9 is network time for TCP/IP connection and login request, and .75 is DB time for the login. -
I have an issue that is rather irritating. I'm playing
around with MYSQL 5.0 on my laptop with Coldfusion 7x
developer edition. I'm using the J-connector 5.0.3.
It's a duo core 1.8 processor with 1 gig of ram. Any
time I include a query of any size accessing tables
with less than 20 records it can take up to 3 seconds
on the debug info. The tables are all properly indexed
and keyed. I've hit several sites and forums to
determine if anyone else is having the issue I am.
They all say things are running fine.
Most queries say 0 msec which is right but after CF
processes the cfincluded query it adds about 3 seconds
on the execution. I'm thinking maybe the database and
the cf server might be fighting over the bus to the
CPU. I just don't know. Have you experienced anything
like this?David, I'm experiencing the same problem. And it's not a
problem with the table joins. I am running a CF/JSP environment and
I run the exact same queries using the exact same driver, and only
experience the problems with CF, the queries run fast in JSP. Mind
you, this is only occurring with MySQL 5 as previous versions of
MySQL ran fine with CF.
Has anyone experienced massive slow down when using MySQL 5
and CF7?
Here are the environments I've tested. I've gotten the same
slow response with each one (up to 5 seconds to return an empty
query)
CF7/Tomcat with MySQL 5 with Connecter/J 5.0
CF7/Tomcat with MySQL 5 with Connecter/J 3.1.10
CF7/IIS with MySQL 5 with Connecter/J 5.0
CF7/IIS with MySQL 5 with Connecter/J 3.1.10
CF7/IIS with MySQL 5 with ODBC/3.5.1
CF7/IIS with MySQL 5 with ODBC/5.0
In each case I've gotten the same results. I've installed on
multiple machines, all running Windows and CF 7, MySQL 5 and Tomcat
5.5 running on the same local server.
Any help would be much appreciated. -
MySQL problem: can't get log-slow-queries to work
I've edited added the requisite lines to /etc/my.cnf (which is being read on start up):
[slowqueries]
longquerytime = 5
log-slow-queries=/var/log/mysql-slow-queries.log
And I've tried different locations for the log file, and I've chown'd it to :wheel, then chmod'd it to 777 (which means any user/process can write to it, right?). And even though I run queries that are longer than five seconds, the file still is neither created, nor if existing, is written to. Any ideas? This seems so straightforward according to the MySQL and Apple docs. I can't figure out what it's not happening.
/// RDFThe CAPS LOCK key also seems to have gotten stuck on.*
Update 51 ratcheted up the security on Java applets, so that unsigned applets that used to generate a warning are now completely blocked. Please see the following documentation from Oracle on your options:
* [http://www.java.com/en/download/help/appsecuritydialogs.xml What should I do when I see a security prompt from Java?]
* [http://www.java.com/en/download/faq/exception_sitelist.xml How can I configure the Exception Site List?]
''* Just a joke-y way of noting that on the web, writing in all caps is considered shouting. Please don't shout at the volunteers.'' -
Slow mySQL select - mySQL/JDBC/CFMX issue?
Hello!
I have got two simple SQL statements in my CFMX app:
SELECT
companyname,
uidnumber,
description,
telephone
FROM
companies
WHERE
entrykey = ?
Query Parameter Value(s) -
Parameter #1(cf_sql_varchar) =
2405961E-FE08-E3BE-059C648DC01198A9
SELECT
LEFT(companyname, 250) AS companyname,
LEFT(uidnumber, 100) AS uidnumber,
LEFT(description, 250) AS description,
LEFT(telephone, 100) AS telephone
FROM
companies
WHERE
entrykey = ?
Query Parameter Value(s) -
Parameter #1(cf_sql_varchar) =
2405961E-FE08-E3BE-059C648DC01198A9
Both return the same result, but the second one only take 1
msec, the first one 30 msec. The number of chars to return (using
LEFT) is exactly the length of the field (no data is shortend).
What could be the reason for that difference? Any methods to make
query #1 as fast as query #2?
system: JDBC 5.0 / myISAM tables with UTF-8 encoding / CFMX7
app server
best regards,
HansjoergHello!
- Index exists, table is optimized (and currently has just 5
records).
- I tried to change the order, no change. The version with
the simple naming of the desired fields is always up to 10-100
times slower than the version with LEFT( ...).
- I now went back to mysql-connector-java-3.0.17-ga-bin.jar
from version mysql-connector-java-5.0.6 - now both queries have the
same speed (about 1-3 msec).
So it seems to be a JDBC driver issue but I cannot find any
information on the net why the newer version is sooo much slower.
Best regards,
Hansjoerg -
Same table, Oracle 5 times slower than MySQL
Hi
I have several sites with the same aplication using a database as a log device and to later retrieve reports from. Some tables are for setup and one are for all the log data. The log data table has the following columns: LINEID, TAG, DATE_, HOUR_, VALUE, TIME_ and CHANGED. Typical data is: 122345, PA01_FT1_ACC, 2008-08-01, 10, 985642, "", 0.
Index (TAG,DATE_)
When calling a report the software querys for typical 3-5 select querys like the following, only different TAG: SELECT * FROM table WHERE TAG='PA01_FT1_ACC' AND DATE_ BETWEEN '2008-08-01' AND '2008-08-31' AND HOUR_=24
Since our customers have different preferences some sites have Oracle and some have MySQL. And I have registered that the sites running Oracle uses 24-30 sec on the report, MySQL uses 3-6 sec on a similar report with the same tables and querying software.
How is this?
Is there anything I can do to make Oracle work faster?
Should HOUR_ also be in the index?
Since I guess this slowness is not something consistant in Oracle, there must be something to do.
Thanks for any help.Histograms on varchar2 columns are based on the
first 6 bytes of the column. If the database is using
a character set that uses 1 byte per character, every
entry in the DATE_ column since the beginning of the
year looks like '2008-0' to the optimizer when
determining cardinality to produce the "best"
execution plan. For character sets that require
multiple bytes per character, the situation is worse
- every entry in the column representing this century
appears to be the same value to the optimizer when
determining cardinality
That's a very good point and I didnt know about it
before, about first 6 bytes being used. Can you point
me in the docs where it is listed if its there or
some other document/s which has this detail?Aman,
I am having a bit of trouble finding the information in the documentation about the number of bytes used by a histogram on a VARCHAR2 column.
References:
http://www.freelists.org/archives/oracle-l/08-2006/msg00199.html
"Cost-Based Oracle Fundamentals" page 117 shows a demonstration, and describes the use of ENDPOINT_ACTUAL_VALUE starting on Oracle 9i.
"Cost-Based Oracle Fundamentals" page 118-120 describes selectivity problems when histograms are not used and a date is placed into a VARCHAR2 column.
"Troubleshooting Oracle Performance", likely around page 130-140 also indicates that histograms only use the first 6 bytes.
See section "Followup November 12, 2005 - 4pm US/Eastern"
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:707586567563
An interesting test setup that almost shows what I intended - but Oracle 10.2.0.2 was a little smarter than I expected, even though it selected to use an index to retrieve more than 50% of a table... Take a look at the TO_CHAR representation of the ENDPOINT_VALUE from DBA_TAB_HISTOGRAMS to understand what I was trying to decribe in my original post in this thread.
CREATE TABLE T1 (DATE_ VARCHAR2(10));
INSERT INTO T1
SELECT
TO_CHAR(TO_DATE('2008-01-01','YYYY-MM-DD')+ROWNUM-1,'YYYY-MM-DD')
FROM
DUAL
CONNECT BY
LEVEL<=250;
250 rows created.
COMMIT;
CREATE INDEX IND_T1 ON T1(DATE_);
SELECT
MIN(DATE_),
MAX(DATE_)
FROM
T1;
MIN(DATE_) MAX(DATE_)
2008-01-01 2008-09-06
SELECT
COLUMN_NAME,
NUM_DISTINCT,
NUM_BUCKETS,
HISTOGRAM
FROM
DBA_TAB_COL_STATISTICS
WHERE
OWNER=USER
AND TABLE_NAME='T1';
no rows selected
SELECT
SUBSTR(COLUMN_NAME,1,10) COLUMN_NAME,
ENDPOINT_NUMBER,
ENDPOINT_VALUE,
SUBSTR(ENDPOINT_ACTUAL_VALUE,1,10) ENDPOINT_ACTUAL_VALUE
FROM
DBA_TAB_HISTOGRAMS
WHERE
OWNER=USER
AND TABLE_NAME='T1';
no rows selected
EXEC DBMS_STATS.GATHER_TABLE_STATS(OWNNAME=>USER,TABNAME=>'T1',METHOD_OPT=>'FOR COLUMNS SIZE 254 DATE_',CASCADE=>TRUE);
PL/SQL procedure successfully completed.
SELECT
COLUMN_NAME,
NUM_DISTINCT,
NUM_BUCKETS,
HISTOGRAM
FROM
DBA_TAB_COL_STATISTICS
WHERE
OWNER=USER
AND TABLE_NAME='T1';
COLUMN_NAME NUM_DISTINCT NUM_BUCKETS HISTOGRAM
DATE_ 250 250 HEIGHT BALANCED
SELECT
SUBSTR(COLUMN_NAME,1,10) COLUMN_NAME,
ENDPOINT_NUMBER,
ENDPOINT_VALUE,
SUBSTR(ENDPOINT_ACTUAL_VALUE,1,10) ENDPOINT_ACTUAL_VALUE
FROM
DBA_TAB_HISTOGRAMS
WHERE
OWNER=USER
AND TABLE_NAME='T1'
ORDER BY
ENDPOINT_NUMBER;
COLUMN_NAM ENDPOINT_NUMBER ENDPOINT_VALUE ENDPOINT_A
DATE_ 1 2.6059E+35 2008-01-01
DATE_ 2 2.6059E+35 2008-01-02
DATE_ 3 2.6059E+35 2008-01-03
DATE_ 4 2.6059E+35 2008-01-04
DATE_ 5 2.6059E+35 2008-01-05
DATE_ 6 2.6059E+35 2008-01-06
DATE_ 7 2.6059E+35 2008-01-07
DATE_ 8 2.6059E+35 2008-01-08
DATE_ 9 2.6059E+35 2008-01-09
DATE_ 10 2.6059E+35 2008-01-10
DATE_ 243 2.6059E+35 2008-08-30
DATE_ 244 2.6059E+35 2008-08-31
DATE_ 245 2.6059E+35 2008-09-01
DATE_ 246 2.6059E+35 2008-09-02
DATE_ 247 2.6059E+35 2008-09-03
DATE_ 248 2.6059E+35 2008-09-04
DATE_ 249 2.6059E+35 2008-09-05
DATE_ 250 2.6059E+35 2008-09-06
ALTER SESSION SET EVENTS '10053 TRACE NAME CONTEXT FOREVER, LEVEL 1';
SELECT
DATE_
FROM
T1
WHERE
DATE_<='2008-01-15';
15 rows selected.
From the 10053 trace:
BASE STATISTICAL INFORMATION
Table Stats::
Table: T1 Alias: T1
#Rows: 250 #Blks: 5 AvgRowLen: 11.00
Index Stats::
Index: IND_T1 Col#: 1
LVLS: 0 #LB: 1 #DK: 250 LB/K: 1.00 DB/K: 1.00 CLUF: 1.00
SINGLE TABLE ACCESS PATH
Column (#1): DATE_(VARCHAR2)
AvgLen: 11.00 NDV: 250 Nulls: 0 Density: 0.002
Histogram: HtBal #Bkts: 250 UncompBkts: 250 EndPtVals: 250
Table: T1 Alias: T1
Card: Original: 250 Rounded: 15 Computed: 15.00 Non Adjusted: 15.00
Access Path: TableScan
Cost: 3.01 Resp: 3.01 Degree: 0
Cost_io: 3.00 Cost_cpu: 85607
Resp_io: 3.00 Resp_cpu: 85607
Access Path: index (index (FFS))
Index: IND_T1
resc_io: 2.00 resc_cpu: 49621
ix_sel: 0.0000e+000 ix_sel_with_filters: 1
Access Path: index (FFS)
Cost: 2.00 Resp: 2.00 Degree: 1
Cost_io: 2.00 Cost_cpu: 49621
Resp_io: 2.00 Resp_cpu: 49621
Access Path: index (IndexOnly)
Index: IND_T1
resc_io: 1.00 resc_cpu: 10121
ix_sel: 0.06 ix_sel_with_filters: 0.06
Cost: 1.00 Resp: 1.00 Degree: 1
Best:: AccessPath: IndexRange Index: IND_T1
Cost: 1.00 Degree: 1 Resp: 1.00 Card: 15.00 Bytes: 0
============
Plan Table
============
| Id | Operation | Name | Rows | Bytes | Cost | Time |
| 0 | SELECT STATEMENT | | | | 1 | |
| 1 | INDEX RANGE SCAN | IND_T1 | 15 | 165 | 1 | 00:00:01 |
Predicate Information:
1 - access("DATE_"<='2008-01-15')
INSERT INTO T1
SELECT
TO_CHAR(TO_DATE('2008-09-07','YYYY-MM-DD')+ROWNUM-1,'YYYY-MM-DD')
FROM
DUAL
CONNECT BY
LEVEL<=250;
COMMIT;
EXEC DBMS_STATS.GATHER_TABLE_STATS(OWNNAME=>USER,TABNAME=>'T1',METHOD_OPT=>'FOR COLUMNS SIZE 254 DATE_',CASCADE=>TRUE);
PL/SQL procedure successfully completed.
SELECT
COLUMN_NAME,
NUM_DISTINCT,
NUM_BUCKETS,
HISTOGRAM
FROM
DBA_TAB_COL_STATISTICS
WHERE
OWNER=USER
AND TABLE_NAME='T1';
COLUMN_NAME NUM_DISTINCT NUM_BUCKETS HISTOGRAM
DATE_ 500 254 HEIGHT BALANCED
SELECT
SUBSTR(COLUMN_NAME,1,10) COLUMN_NAME,
ENDPOINT_NUMBER,
TO_CHAR(ENDPOINT_VALUE) ENDPOINT_VALUE,
SUBSTR(ENDPOINT_ACTUAL_VALUE,1,10) ENDPOINT_ACTUAL_VALUE
FROM
DBA_TAB_HISTOGRAMS
WHERE
OWNER=USER
AND TABLE_NAME='T1'
ORDER BY
ENDPOINT_NUMBER;
COLUMN_NAM ENDPOINT_NUMBER ENDPOINT_VALUE ENDPOINT_A
DATE_ 0 260592218925307000000000000000000000 2008-01-01
DATE_ 1 260592218925307000000000000000000000 2008-01-02
DATE_ 2 260592218925307000000000000000000000 2008-01-04
DATE_ 3 260592218925307000000000000000000000 2008-01-06
DATE_ 4 260592218925307000000000000000000000 2008-01-08
DATE_ 5 260592218925307000000000000000000000 2008-01-10
DATE_ 6 260592218925307000000000000000000000 2008-01-12
DATE_ 7 260592218925307000000000000000000000 2008-01-14
DATE_ 8 260592218925307000000000000000000000 2008-01-16
DATE_ 9 260592218925307000000000000000000000 2008-01-18
DATE_ 10 260592218925307000000000000000000000 2008-01-20
DATE_ 242 260592219234792000000000000000000000 2009-04-26
DATE_ 243 260592219234792000000000000000000000 2009-04-28
DATE_ 244 260592219234792000000000000000000000 2009-04-29
DATE_ 245 260592219234792000000000000000000000 2009-05-01
DATE_ 246 260592219234792000000000000000000000 2009-05-02
DATE_ 247 260592219234792000000000000000000000 2009-05-04
DATE_ 248 260592219234792000000000000000000000 2009-05-05
DATE_ 249 260592219234792000000000000000000000 2009-05-07
DATE_ 250 260592219234792000000000000000000000 2009-05-08
DATE_ 251 260592219234792000000000000000000000 2009-05-10
DATE_ 252 260592219234792000000000000000000000 2009-05-11
DATE_ 253 260592219234792000000000000000000000 2009-05-13
DATE_ 254 260592219234792000000000000000000000 2009-05-14
SELECT
DATE_
FROM
T1
WHERE
DATE_ BETWEEN '2008-01-15' AND '2008-09-15';
245 rows selected.
From the 10053 trace:
BASE STATISTICAL INFORMATION
Table Stats::
Table: T1 Alias: T1
#Rows: 500 #Blks: 5 AvgRowLen: 11.00
Index Stats::
Index: IND_T1 Col#: 1
LVLS: 1 #LB: 2 #DK: 500 LB/K: 1.00 DB/K: 1.00 CLUF: 2.00
SINGLE TABLE ACCESS PATH
Column (#1): DATE_(VARCHAR2)
AvgLen: 11.00 NDV: 500 Nulls: 0 Density: 0.002
Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 255
Table: T1 Alias: T1
Card: Original: 500 Rounded: 240 Computed: 240.16 Non Adjusted: 240.16
Access Path: TableScan
Cost: 3.01 Resp: 3.01 Degree: 0
Cost_io: 3.00 Cost_cpu: 148353
Resp_io: 3.00 Resp_cpu: 148353
Access Path: index (index (FFS))
Index: IND_T1
resc_io: 2.00 resc_cpu: 111989
ix_sel: 0.0000e+000 ix_sel_with_filters: 1
Access Path: index (FFS)
Cost: 2.01 Resp: 2.01 Degree: 1
Cost_io: 2.00 Cost_cpu: 111989
Resp_io: 2.00 Resp_cpu: 111989
Access Path: index (IndexOnly)
Index: IND_T1
resc_io: 2.00 resc_cpu: 62443
ix_sel: 0.48031 ix_sel_with_filters: 0.48031
Cost: 2.00 Resp: 2.00 Degree: 1
Best:: AccessPath: IndexRange Index: IND_T1
Cost: 2.00 Degree: 1 Resp: 2.00 Card: 240.16 Bytes: 0
============
Plan Table
============
| Id | Operation | Name | Rows | Bytes | Cost | Time |
| 0 | SELECT STATEMENT | | | | 2 | |
| 1 | INDEX RANGE SCAN | IND_T1 | 240 | 2640 | 2 | 00:00:01 |
Predicate Information:
1 - access("DATE_">='2008-01-15' AND "DATE_"<='2008-09-15')I am sure that there are much better examples than the above, as the above generates a very small data set, and is still an incomplete test setup.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc. -
Slow to UPDATE records in MySQL
Hi all,
I've recently started using MySQL on my local machine for its reported speed. I've developed an application that executes at the end of each day, this creates a result set using a simple SELECT query. I then manipluate records from the result set and update the database using an UPDATE statement.
It works fine, the only problem is it takes a very long time to run - 4 hours on average. Im using the JDBC:MYSQL Type 4 driver - which should be very fast. Each day i need to create approx 10,000 separate result sets, perform the calculations and update the database. The calculations aren't the problem and take next to no time to perform, it's mainly updating the database that takes the most time.
Does anyone know a way of increasing the speed? Any suggestions would be appreciated!
Regards,
BBBHere's some sample code. As you can see, there's nothing too advanced with the statements. The database currently holds 152,000 records so would this account for the slow update speeds?
Class.forName(driver).newInstance();
Connection con = DriverManager.getConnection(url, "", "");
Statement stmt = con.createStatement(); // getting tickers
Statement stmt2 = con.createStatement(); // stock 50 day high
ResultSet rs = stmt.executeQuery(GetStockCalculations.query);
// get the price and value of the stock
String query = "SELECT EngDaily.fd_Date, EngDaily.Indi, EngDaily.Total " +
"FROM EngDaily WHERE ((EngDaily.Indi)='" + name + "') ORDER BY EngDaily.fd_Date DESC;";
int total = 0;
ResultSet rs2 = stmt2.executeQuery(query);
int counter = 0;
while ( rs2.next() && counter < 5 ) {
total += Double.parseDouble( rs2.getString( "Total" ) );
counter ++;
double avgTotal = total / 5;
stmt.executeUpdate( "UPDATE EngDaily SET AvgTotal = '" + avgTotal + "' WHERE fd_Date = '" + GetCalculations.date + "' AND EngDaily.Indi = '" + name + "';" );
Maybe you are looking for
-
View thumbnails by default on Open...
Using PS CS3 and Win XP Home Need a way to set the Open... dialogue box to display thumbnails by default rather than just a list of my image file names. Frustrated! Ta.
-
Magic Mouse multi-touch surface not working.
Three months ago, I purchased the Magic Mouse. Recently, the multi-touch surface has not been responding. The tracking and bluetooth connections are fine. I have checked the Mouse Preferences and these appear to checked correctly. Any suggestions?
-
How similar is x86 compared to Solaris 8 or 9 on SPARC?
How similar is x86 compared to Solaris 8 or 9 on SPARC? Thanks.
-
I have found out an error in valuation in COPA (due to the +/- Sign in Condition type assignment to Value fields - KE4I) What is the most optimum way of correction of this error. Should the billing document be reversed and reposted. Or the fi documen
-
I am running a Visual Basic 6 program that connects to an Oracle database and works OK until I try to store a clob via a package. When attemting to set .. cmd.Properties("SPPrmsLOB") = True .. I get the error "Item cannot be found in the collection c