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

Kontact doesn't start

Tags: None
(comma "," separated)
Carsten93
Registered Member
Posts
3
Karma
0

Re: Kontact doesn't start

Sat Feb 20, 2010 10:53 am
I had the same problem, you initially described, but managed to get rid of this mysql error by following 4.5 in http://userbase.kde.org/Akonadi closely.

I know you uncommented the line sql_mode=strict_trans_tables. Like in your case that didn't work for me, but did you definitely try the second step with commenting that out again and then searched for the line that starts the same, but has a lot more options and to uncomment that one? That did the trick for me.

I still have this D-Bus issue at a later (test 9 and 10) stage though :(
User avatar
Achilleus
Registered Member
Posts
19
Karma
0
OS

Re: Kontact doesn't start

Sat Feb 20, 2010 3:18 pm
Well, uncommenting the other line kinda helped with the [ERROR] Can't open and lock privilege tables, but Akonadi was no longer able to start, so it's not a solution at all.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Kontact doesn't start

Sat Feb 20, 2010 10:08 pm
You need to comment the line "skip_grant_tables" then move db_data somewhere else again.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Achilleus
Registered Member
Posts
19
Karma
0
OS

Re: Kontact doesn't start

Sun Feb 21, 2010 11:20 am
Still the same error

Code: Select all
100221 12:17:26 [Note] Plugin 'FEDERATED' is disabled.
100221 12:17:26 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100221 12:17:27  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100221 12:17:27  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait...
100221 12:17:29  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100221 12:17:31  InnoDB: Started; log sequence number 0 0
100221 12:17:31 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
100221 12:17:31 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
100221 12:17:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.42-log'  socket: '/home/zbyszek/.local/share/akonadi/db_misc/mysql.socket'  port: 0  Source distribution
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Kontact doesn't start

Mon Feb 22, 2010 4:12 am
Could you please post your /home/zbyszek/.local/share/akonadi/mysql.conf file?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Achilleus
Registered Member
Posts
19
Karma
0
OS

Re: Kontact doesn't start

Mon Feb 22, 2010 7:17 am
Here you are :)

Code: Select all
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
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=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 <kris@mysql.com>
#
[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=64M
innodb_flush_log_at_trx_commit=2
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Kontact doesn't start

Mon Feb 22, 2010 7:51 am
Please replace the contents of the file completely with the following and move db_data somewhere else again.

Code: Select all
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
#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=64M
innodb_flush_log_at_trx_commit=2


Make sure nothing else is left in the file other than those exact contents


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Achilleus
Registered Member
Posts
19
Karma
0
OS

Re: Kontact doesn't start

Mon Feb 22, 2010 8:38 am
I know what you mean, but previously I was making changes to another config file located in /home/zbyszek/.config/akonadi/mysql-local.conf as described here. Does Akonadi have two separate config files? :o
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Kontact doesn't start

Tue Feb 23, 2010 4:26 am
My Akonadi state is quite old, so it may be out of date. If you have an mysql.conf file, please make changes there, and delete mysql-local.conf. Failing everything, delete the entire ~/.local/share/akonadi folder, which will cause Akonadi to start afresh.

Your Akonadi configurations are stored in ~/.config/akonadi and are thus not affected by this.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], blue_bullet, Google [Bot], Sogou [Bot]