PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Akonadi - Steuerprogramm nicht am D-BUS registriert



Triple666Blood
24.09.09, 00:11
Hi,

will den Akonadi-Server zum laufen kriegen umd meine Kontactdaten damit zu speichern.
Leider bekomme ich folgende Fehlermelungen beim Start von Akonadi:

Steuerprogramm nicht am D-BUS registriert......

Habe auch schon gegoogelt, kann aber eine passende und funktionierende Lösung nicht finden.

Anbei das Fehlerprotokoll

Vielleicht könnt ihr mir ja helfen.

Vielen Dank

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/rincewind/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
User=
Password=
Options="UNIX_SOCKET=/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


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.38 for unknown-linux-gnu on x86_64 (Source distribution)


Test 4: ERROR
--------

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

File content of '/home/rincewind/.local/share/akonadi/db_data/mysql.err':
090923 21:16:56 [Note] Plugin 'FEDERATED' is disabled.
090923 21:16:56 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
090923 21:16:56 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
090923 21:17:55 InnoDB: Started; log sequence number 0 44233
090923 21:17:55 [Note] /usr/sbin/mysqld: Normal shutdown

090923 21:17:55 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
090923 21:17:55 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
090923 21:17:55 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.38-log' socket: '/home/rincewind/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source distribution
090923 21:17:55 InnoDB: Starting shutdown...
090923 21:17:56 InnoDB: Shutdown completed; log sequence number 0 44233
090923 21:17:56 [Warning] Forcing shutdown of 2 plugins
090923 21:17:56 [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 <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,st rict_error_for_division_by_zero,no_auto_create_use r,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: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/rincewind/.local/share/akonadi/mysql.conf'>/home/rincewind/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/rincewind/.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,st rict_error_for_division_by_zero,no_auto_create_use r,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: SUCCESS
--------

No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.

Test 14: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href='/home/rincewind/.local/share/akonadi/akonadiserver.error.old'>/home/rincewind/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/rincewind/.local/share/akonadi/akonadiserver.error.old':
Unable to open database "Can't connect to local MySQL server through socket '/mysql.socket' (2) QMYSQL: Unable to connect"
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x40b539]
1: akonadiserver [0x40ba82]
2: /lib/libc.so.6 [0x7f4112a9bf90]
3: /lib/libc.so.6(gsignal+0x35) [0x7f4112a9bf15]
4: /lib/libc.so.6(abort+0x180) [0x7f4112a9d340]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x6f) [0x7f4113a0504f]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+ 0xa8) [0x40c5b8]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x6e) [0x7f4113a8f80e]
8: /usr/lib/libQtCore.so.4 [0x7f4113a9d599]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0x7f4113a9e5c8]
10: akonadiserver(_ZN6QDebugD1Ev+0x45) [0x406a95]
11: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC 1EP7QObject+0x553) [0x7f4114056593]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8 instanceEv+0x4a) [0x7f41140572ca]
13: akonadiserver(main+0x3a4) [0x406154]
14: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f4112a889ed]
15: akonadiserver [0x405cb9]
]
"


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.

cookie170
26.09.09, 10:17
Geht mir genauso. Tut offensichtlich noch nicht richtig. Nach jahrelanger Erfahrung mit Linux als Nutzer: Abwarten, irgendwann läufts.

Niniveh
02.04.10, 20:17
Hi

Bei mir ist es mit KDE-4.3.5 genau so.
Allerdings war Nepomuk ursprünglich installiert und im zuge eines upgrades anscheinend wieder entfernt.
Kmail funktioniert bei mir, anders als bei anderen (http://www.linuxforen.de/forums/showthread.php?t=266542&highlight=Akonadi) auch mit diesem Akonadi-Fehler und ohne Nepomuk.
Meinen Fehlerbericht lasse ich mal, ist etwas umfangreich wie oben.
Aber anscheinend sind es die gleichen Fehlermeldungen.
Aber falls ihr ihn braucht hole ich es nach.

naraesk
02.04.10, 21:08
Nepomuk und Co wurden erst bei KDE 4.4 wirklich notwendig, bei KDE 4.3.x funktioniert daher auch alles ohne Nepomuk.

Bei der im ersten Beitrag geposteten Fehlermeldung laufen mehrere mysqld- Prozesse, wodurch ein Zugriffsfehler entsteht. Kille die einmal und probiere es erneut.

Und andernfalls dieses Tutorial einmal ausprobieren, hat bei mir mit Fedora ebenfalls funktioniert:
http://www.gentoofreunde.org/node/114

Niniveh
03.04.10, 09:08
Danke naraesk

Hmm?
Also Akonadi funktioniert noch nicht. Ich lege einen Screenshot Kurzbericht in
die Anlage.
Es kann aber gut sein, dass ich mich bei der englischsprachige Anleitung zu
MYSQL verhauen habe. ( # /usr/bin/mysql_secure_installation)
Jedenfalls legte ich dabei ein Passwort an, das gleiche wie für Root.

Ich versuche hier den Verlauf übersichtlich darzustellen, er ist hoffentlich nicht zu umfangreich. Kannst du oder jemand anderer einen Fehler von mir erkennen?

MYSQL scheint jedenfalls zu laufen:

# /etc/init.d/mysql start
mysql | * WARNING: mysql has already been started

Akonadi nicht:

~ $ akonadictl start
akonadictl: symbol lookup error: akonadictl: undefined symbol:
_ZN5boost15program_options6detail7cmdline21set_add itional_parserENS_9function1IS
t4pairISsSsERKSsSaINS_13function_baseEEEE


Mein Vorgehen
Zusammenfassung:

# mkdir /var/lib/mysql
# /etc/init.d/mysql start
# rc-update add mysql default
# /usr/bin/mysql_secure_installation

Hier liegt im Folgenden etwa der Fehler?
Ich verstand die folgende Anleitung nicht recht und verwendete danach diesen
Befehlsvorschlag "/usr/bin/mysql_secure_installation":
Also zuerst:

# /usr/bin/mysql_install_db
WARNING: The host 'gentoo64' could not be looked up with resolveip.
This probably means that your libc libraries are not 100 % compatible
with this binary MySQL version. The MySQL daemon, mysqld, should work
normally with the exception that host name resolving will not work.
This means that you should use IP addresses instead of hostnames
when specifying MySQL privileges !
Installing MySQL system tables...
OK
Filling help tables...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h gentoo64 password 'new-password'

Alternatively you can run:
/usr/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com



# /usr/bin/mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

You already have a root password set, so you can safely answer 'n'.

Change the root password? [Y/n] n
... skipping.

By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] n
... skipping.

Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] y
... Success!

By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] y
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] y
... Success!

Cleaning up...
All done! If you've completed all of the above steps, your MySQL
installation should now be secure.
Thanks for using MySQL!

Wenn ich jetzt als User $ /usr/bin/mysql_install_db ausführe kommt diese Meldung, die auch auf den Fehler hinweisen könnte, ich verstehe es nur nicht recht.
Als Root ausgeführt kommt die gleiche Meldung, wie oben schon gepostet, nur ohne die "Warnungen".

~ $ /usr/bin/mysql_install_db
WARNING: The host 'gentoo64' could not be looked up with resolveip.
This probably means that your libc libraries are not 100 % compatible
with this binary MySQL version. The MySQL daemon, mysqld, should work
normally with the exception that host name resolving will not work.
This means that you should use IP addresses instead of hostnames
when specifying MySQL privileges !
Installing MySQL system tables...
100403 11:07:28 [Warning] Can't create test file /var/lib/mysql/gentoo64.lower-test
100403 11:07:28 [Warning] Can't create test file /var/lib/mysql/gentoo64.lower-test
100403 11:07:28 [Warning] One can only use the --user switch if running as root

100403 11:07:28 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
/usr/sbin/mysqld: File './mysqld-bin.index' not found (Errcode: 13)
100403 11:07:28 [ERROR] Aborting

100403 11:07:28 [Note] /usr/sbin/mysqld: Shutdown complete

Installation of system tables failed!

Examine the logs in /var/lib/mysql for more information.
You can try to start the mysqld daemon with:
/usr/sbin/mysqld --skip-grant &
and use the command line tool
/usr/bin/mysql to connect to the mysql
database and look at the grant tables:

shell> /usr/bin/mysql -u root mysql
mysql> show tables

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in /var/lib/mysql that may be helpful.

The latest information about MySQL is available on the web at
http://www.mysql.com
Please consult the MySQL manual section: 'Problems running mysql_install_db',
and the manual section that describes problems on your OS.
Another information source is the MySQL email archive.
Please check all of the above before mailing us!
And if you do mail us, you MUST use the /usr/bin/mysqlbug script!


Und wenn ich es recht sehe, kommen jetzt die Akonadi Probleme, jedenfalls
läuft er nicht:

~ $ pidof akonadi
~ $ akonadictl stop
akonadictl: symbol lookup error: akonadictl: undefined symbol:
_ZN5boost15program_options6detail7cmdline21set_add itional_parserENS_9function1IS
t4pairISsSsERKSsSaINS_13function_baseEEEE

~ $ akonadictl start
akonadictl: symbol lookup error: akonadictl: undefined symbol:
_ZN5boost15program_options6detail7cmdline21set_add itional_parserENS_9function1IS
t4pairISsSsERKSsSaINS_13function_baseEEEE


Die Pfade
.kde4/share/config/akonadi*
.config/akonadi/
.local/share/akonadi/ hatte ich gelöscht.

Niniveh
05.04.10, 09:37
Moin

Wie es aussieht, stellt Akonadi selbst Subprofis bei KDE-4.3.5 vor echte Probleme.
Erst ab KDE-4.4 scheint das zu funktionieren.
Der Rat ist, Akonadi einfach zu lassen, bis man bei diesen Versionsnummern angekommen ist.

P.s.:
Beim Upgrade auf KDE-4.4 muss man übrigens das .kde4 Verzeichniss neu anlegen, den KDE-Desktop also neu einrichten. Es tut sich hier anscheinend viel.

AndreasMeier
12.05.10, 10:01
Moin
P.s.:
Beim Upgrade auf KDE-4.4 muss man übrigens das .kde4 Verzeichniss neu anlegen, den KDE-Desktop also neu einrichten. Es tut sich hier anscheinend viel.

Ich hab ähnliche Probleme mit dem Akonadi.

Hab das Update auf 4.4 gemacht, allerdings nicht das .kde4-Verzeichnis neu angelegt.

Kann ich das nachträglich machen, indem ich es lösche und KDE neu starte ?

Danke und Gruß
Andreas

f_m
12.05.10, 14:42
Kann ich das nachträglich machen, indem ich es lösche und KDE neu starte ?

Grundsätzlich ja;
Empfehlenswert ist da immer zuerst mal nur umbennen und wenn es problemlos klappt dann löschen, so kann man bei Bedarf auch durch Rückumbenennen die Sache Rúckgängig machen ;)

gropiuskalle
12.05.10, 16:09
Und wozu soll das gut sein? Bei mir war es nicht notwendig, das komplette ~/.kde4 zu löschen.

Niniveh
12.05.10, 21:33
Hi

Anscheinend gibt es gelegentlich, aber nicht immer, Probleme beim Übergang zu kde4.4.
Empfohlen wird meist, wie oben beschrieben, ~.kde4 nur um zu benennen.
Wenn KDE4.4 danach gestartet wird, wird ~.kde4 neu in der Standardeinstellung angelegt.
Einiges kann man danach vom alten .kde4 zum neuen .kde4 kopieren.
Diese beispielsweise:
* ~/.kde4/share/apps/kmail
* ~/.kde4/share/config/emailidentities
* ~/.kde4/share/config/mailtransport

Hier muss man wohl ein wenig probieren. Wenn etwas funktioniert ist es gut, wenn nicht, muss man dies neu einstellen.
Man hat ja die Sicherung von .kde4.

gropiuskalle
12.05.10, 22:46
Das liest sich schon etwas differenzierter - ich hatte zu Anfang ebenfalls einige Probleme mit strigi / Akonadi, diese konnte ich irgendwann in den Griff bekommen, die fixes betrafen aber ausschließlich Konfigurationen im Zusammenhang mit Akonadi (bzw. strigi bzw. virtuoso etc.). Für mich ist nicht nachvollziehbar, weshalb man derart rigoros alle möglichen Einstellungen über Bord werfen soll.

AndreasMeier
13.05.10, 10:23
Den Akonadi starte ich nun über KDE-Autostart per Skript.
Das Skript wartet dann nach dem Akonadi und startet danach mein Kontact.
Ist mein Arbeitsrechner, daher läuft Kontact sowieso immer.

Damit hab ich die Akonadi-Fehlermeldung wegbekommen.
Zusätzlich hab ich aber die Akonadi-Config und noch andere Dateien (Log?) gelöscht.

Anleitung fürs Skript hatte ich hiervon (http://forum.ubuntuusers.de/topic/akonadi-fehlermedungen-endgueltig-abstellen/).
Die Datei-Löschung hatte ich aus ner anderen Quelle, die ich grad nicht wiederfinde.

Auch die Tipps zur manuellen Adressbuch-Anlage ganz unten im gen.Posting war hilfreich.

Seitdem läuft mein Akonadi, Kontact samt Adressbuch etc., alles ohne Fehlermeldung.
Scheinbar hat Akonadi ein Problem, wenn er "nachträglich" mit Kontact gestartet wird.

Was mir jetzt noch fehlt, ist die Anbindung von Akonadi an meine eGroupware.
Das geht m.E. über das GroupDAV-Modul von Akonadi, aber ich hab noch nicht die richtigen Einstellungen dafür gefunden.

Das Löschen des KDE4-Verzeichnisses hab ich NICHT gemacht, hab bis jetzt keine anderen Probleme festgestellt.

Gruß
Andreas

rkofler
14.11.11, 11:23
ERROR:
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!

my solution on kde 4.7.2:

rm -fr .kde4/share/config/akonadi*
rm -fr .config/akonadi/
rm -fr .local/share/akonadi/

I realized a mssing "akonadi" dir, so

mkdir ~/.local/share/akonadi
and
akonadictl start

done!