| View previous topic :: View next topic |
| Author |
Message |
Heimscheisser
n00b
Joined: 11 Oct 2010
Posts: 2
|
 Posted: Sun Oct 17, 2010 10:45 am Post subject: [SOLVED]Akonadi Server Configuration: MYSQL Server not found |
 |
|
Hi!
I know, there are many problems with akonadi and I googled a long time, but I can't find any thread with the same problem. My main problem is, that the akonadi can't find my MySQL-Server. Of course there is an executable ("/usr/sbin/mysqld"). So I've set this path in the akonadi-server-GUI. But it obviously this path can't be saved, because when I reopened the GUI there is no path any more.
In my home directory, there isn't a directory ".config", where the "/akonadiserverrc" should be. There is only a file with this name. Maybe this the problem, but how I can fix it?
Currently, I'm using:
- KDE 4.5
- akonadi-server 1.4.0-r2
- akonadi 4.4.5
Here is my test protocol of the akonadi-server:
| Code: |
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 '/akonadiserverrc' could not be opened
Test 2: SUCCESS
--------
Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.
Test 3: ERROR
--------
MySQL server not found.
Details: You have currently configured Akonadi to use the MySQL server ''.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.
Test 4: ERROR
--------
Executing the MySQL server failed.
Details: Executing the MySQL server '' failed with the following error message: ''
Test 5: SUCCESS
--------
MySQL server log contains no errors.
Details: The MySQL server log file '<a href='/home/florian/.local/share/akonadi/db_data/mysql.err'>/home/florian/.local/share/akonadi/db_data/mysql.err</a>' does not contain any errors or warnings.
File content of '/home/florian/.local/share/akonadi/db_data/mysql.err':
101017 11:51:12 InnoDB: Started; log sequence number 0 134920
101017 11:51:13 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.50' socket: '/home/florian/.local/share/akonadi/db_misc/mysql.socket' port: 0 Gentoo Linux mysql-5.1.50-r1
Test 6: SUCCESS
--------
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.
File content of '/usr/share/config/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@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=utf8
collation_server=utf8_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
# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000
[client]
default-character-set=utf8
Test 7: SKIP
--------
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
Test 8: SUCCESS
--------
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/florian/.local/share/akonadi/mysql.conf'>/home/florian/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/florian/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@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=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
[/list]# 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
# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000
[client]
default-character-set=utf8
Test 9: SUCCESS
--------
akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.4.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: SUCCESS
--------
Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.
Test 13: SUCCESS
--------
Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.
Test 14: 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 15: SUCCESS
--------
Resource agents found.
Details: At least one resource agent has been found.
Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop
Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/local/share:/usr/share'
Test 16: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 17: 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/florian/.local/share/akonadi/akonadiserver.error.old'>/home/florian/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/florian/.local/share/akonadi/akonadiserver.error.old':
D-Bus session bus went down - quitting
Failed to remove runtime connection config file
Test 18: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 19: 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/florian/.local/share/akonadi/akonadi_control.error.old'>/home/florian/.local/share/akonadi/akonadi_control.error.old</a>.
File content of '/home/florian/.local/share/akonadi/akonadi_control.error.old':
D-Bus session bus went down - quitting
|
Thanks for your help!
Last edited by Heimscheisser on Mon Oct 18, 2010 5:23 pm; edited 2 times in total |
|
| Back to top |
|
 |
codestation
Tux's lil' helper
Joined: 09 Nov 2008
Posts: 126
Location: /dev/negi
|
| Posted: Sun Oct 17, 2010 5:05 pm Post subject: Re: Akonadi Server Configuration: MYSQL Server not found |
|
|
| Heimscheisser wrote: |
In my home directory, there isn't a directory ".config", where the "/akonadiserverrc" should be. There is only a file with this name. Maybe this the problem, but how I can fix it? |
Have you tried deleting that file? In fact it must be a directory, so while that file exists other apps who use the .config directory cant write their configs.
_________________
Just feel the code... |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3465
Location: Gainesville, Florida
|
| Posted: Mon Oct 18, 2010 3:18 pm Post subject: |
|
|
If I didn't have a .config directory in my /home/user/ directory I'd definitely do (as user) a: | Code: | | mkdir /home/myuser/.config |
where "myuser" is of course your user name, and then do a cold reboot (to make sure all ram is cleared). My /home/wrc/.config directory has 27 folders and 5 files for all sorts of major apps. I expect a reboot would populate your newly created .config with all sorts of interesting stuff. 
What I don't get is how you are getting along without one, and why you don't even have one?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.41-r2, gcc-15.1.0
kernel-6.15.6 USE=experimental python3.13.3 |
|
| Back to top |
|
|
Heimscheisser
n00b
Joined: 11 Oct 2010
Posts: 2
|
| Posted: Mon Oct 18, 2010 5:05 pm Post subject: |
|
|
Simple solution ^^ But it works! Sorry, I'm fairly new to gentoo and I thought there is a good reason, why there is this ".config"-file. I hope deleting hasn't destroyed it.
Thank you very much! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
