19.03.2024, 09:47 UhrDeutsch | English
Hallo Gast [ Registrierung | Anmelden ]

Neues Thema eröffnen   Neue Antwort erstellen
Vorheriges Thema anzeigen Druckerfreundliche Version Einloggen, um private Nachrichten zu lesen Nächstes Thema anzeigen
Autor Nachricht
knegges
Titel: Akonadi startet nicht  BeitragVerfasst am: 16.06.2013, 22:40 Uhr



Anmeldung: 22. Jul 2008
Beiträge: 74

Hallo,
ich habe gestern DF installiert.
Merci für Eure Arbeit.

Leider kann ich kmail nicht benutzen, weil Akonadi nicht richtig startet, oder installiert ist.

Es kommen folgende Fehlermeldungen:
MySQL-Server enthält Fehler
Akonadi-Steuerprogramm nicht am D-Bus registriert
Akonadi-Serverprogramm nicht am D-Bus registriert
Nepumuk-Suchdienst nicht am D-Bus registriert
Keine Ressourcen-Vermittler gefunden
Aktuelles Fehlerprotokoll des Akonadi-Servers gefunden
Früheres Fehlerprotokoll des Akonadi-Servers gefunden

Das aktuelle Fehlerprotokoll sieht so aus:
---------------
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/user/.local/share/akonadi/mysql.conf", "--datadir=/home/user/.local/share/akonadi/db_data/", "--socket=/home/user/.local/share/akonadi/socket-kanotixbox/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x805dbd5]
1: akonadiserver() [0x805df1a]
2: linux-gate.so.1(__kernel_sigreturn+0) [0xb77c1400]
3: /lib/i386-linux-gnu/libc.so.6(gsignal+0x45) [0xb6ebf165]
4: /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb6ec25f3]
5: /usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x13c) [0xb7525bfc]
6: akonadiserver() [0x805ff18]
7: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xe8) [0xb75ce848]
8: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x117c7d) [0xb75dac7d]
9: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3e) [0xb75e3e6e]
10: akonadiserver() [0x80ddcba]
11: akonadiserver() [0x8060d81]
12: akonadiserver() [0x8062406]
13: akonadiserver() [0x8063a56]
14: akonadiserver() [0x8056f5a]
15: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0xb6eaa5b5]
16: akonadiserver() [0x8057a01]
]
" ----------------------

Habt Ihr ein paar Tipps, wie ich den Fehler beheben kann?

Gruss
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
Kano
Titel: Akonadi startet nicht  BeitragVerfasst am: 17.06.2013, 04:23 Uhr



Anmeldung: 17. Dez 2003
Beiträge: 16783

Code:
apt-get install virtuoso-minimal

dann mal ausloggen.
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
knegges
Titel: Akonadi startet nicht  BeitragVerfasst am: 17.06.2013, 21:14 Uhr



Anmeldung: 22. Jul 2008
Beiträge: 74

Hallo,

Ich hab' virtuoso-minimal installiert, aus- und eingeloggt und auch neugestartet.
Akonadi läuft aber immer noch nicht, es kommen leider noch die gleichen Fehlermeldungen.

Gruss
k
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
Kano
Titel: Akonadi startet nicht  BeitragVerfasst am: 17.06.2013, 21:17 Uhr



Anmeldung: 17. Dez 2003
Beiträge: 16783

Du kannst auch nicht kmail pur installieren, du brauchst immer kdepim. Ich nehme nie kmail, weils einfach nur nervt Winken
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
knegges
Titel: Akonadi startet nicht  BeitragVerfasst am: 17.06.2013, 21:44 Uhr



Anmeldung: 22. Jul 2008
Beiträge: 74

kdepim zieht ja einen Riesen Rattenschwanz hinter sich her, alles Programme, die ich nicht brauche!!
Kmail lief bei mir jetzt gut, auch ohne alle die anderen Programme.

Dann wechsle ich wohl doch lieber zu Icedove,
wenn das System sonst auch ohne Akonadi läuft?

Gruss
k
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
Kano
Titel: Akonadi startet nicht  BeitragVerfasst am: 18.06.2013, 06:14 Uhr



Anmeldung: 17. Dez 2003
Beiträge: 16783

Die paar Pakete machen nichts aus, aber kmail pur geht halt nicht, das rauszusuchen was man zusätzlich braucht dauert viel länger
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
knegges
Titel: Akonadi startet nicht  BeitragVerfasst am: 24.06.2013, 20:34 Uhr



Anmeldung: 22. Jul 2008
Beiträge: 74

Hallo,
hier ein Link, der zeigt, wie man kmail auch ohne kdepim und alle anderen Zusatzpakete laufen lassen kann:

http://docs.kde.org/stable/de/kdepim/km ... ation.html

LG
k
 
 Benutzer-Profile anzeigen Private Nachricht senden  
Antworten mit Zitat Nach oben
PitTux
15 Titel: Akonadi startet nicht  BeitragVerfasst am: 26.08.2013, 13:15 Uhr



Anmeldung: 26. Aug 2004
Beiträge: 1214
Wohnort: Hessen/Kassel-Fuldatal
Zitat:
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/PitTux/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


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/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 location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.31-1 for debian-linux-gnu on x86_64 ((Debian))


Test 5: ERROR
--------

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

File content of '/home/PitTux/.local/share/akonadi/db_data/mysql.err':
130826 14:12:20 [Note] Plugin 'FEDERATED' is disabled.
130826 14:12:20 InnoDB: The InnoDB memory heap is disabled
130826 14:12:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130826 14:12:20 InnoDB: Compressed tables use zlib 1.2.7
130826 14:12:20 InnoDB: Using Linux native AIO
130826 14:12:20 InnoDB: Initializing buffer pool, size = 80.0M
130826 14:12:20 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 67108862 bytes
InnoDB: than specified in the .cnf file 0 67108864 bytes!
130826 14:12:20 [ERROR] Plugin 'InnoDB' init function returned error.
130826 14:12:20 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130826 14:12:20 [ERROR] Unknown/unsupported storage engine: innodb
130826 14:12:20 [ERROR] Aborting

130826 14:12:20 [Note] /usr/sbin/mysqld: Shutdown complete



Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/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]

# 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


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/PitTux/.local/share/akonadi/mysql.conf'>/home/PitTux/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/PitTux/.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]

# 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


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.9.2


Test 10: 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 11: 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 12: ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: 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 14: 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/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.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
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'

Test 15: 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/PitTux/.local/share/akonadi/akonadiserver.error'>/home/PitTux/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/PitTux/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/PitTux/.local/share/akonadi/mysql.conf", "--datadir=/home/PitTux/.local/share/akonadi/db_data/", "--socket=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418114]
1: akonadiserver() [0x418541]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x35260) [0x7f01d1548260]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f01d15481e5]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f01d154b398]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f01d2ff7912]
6: akonadiserver() [0x41a3eb]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f01d3092190]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11858d) [0x7f01d309f58d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f01d30a8173]
10: akonadiserver() [0x486dba]
11: akonadiserver() [0x41b0b7]
12: akonadiserver() [0x41ce65]
13: akonadiserver() [0x41e487]
14: akonadiserver() [0x411f43]
15: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f01d1534995]
16: akonadiserver() [0x4128d1]
]
"


Test 16: 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/PitTux/.local/share/akonadi/akonadiserver.error.old'>/home/PitTux/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/PitTux/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/PitTux/.local/share/akonadi/mysql.conf", "--datadir=/home/PitTux/.local/share/akonadi/db_data/", "--socket=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418114]
1: akonadiserver() [0x418541]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x35260) [0x7f88fed86260]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f88fed861e5]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f88fed89398]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f8900835912]
6: akonadiserver() [0x41a3eb]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f89008d0190]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11858d) [0x7f89008dd58d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f89008e6173]
10: akonadiserver() [0x486dba]
11: akonadiserver() [0x41b0b7]
12: akonadiserver() [0x41ce65]
13: akonadiserver() [0x41e487]
14: akonadiserver() [0x411f43]
15: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f88fed72995]
16: akonadiserver() [0x4128d1]
]
"


Test 17: SUCCESS
--------

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

Test 18: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Naja probieren geht über studieren???

_________________
ich habe zwar keine Lösung, bewundere aber das Problem
Quad Intel Core i3-4350T /Quad Intel Pentium N3540 - Linux 5.0.0-5-generic x86_64 [ Kanotix buster KDE KANOTIX-Build 20190202-15:53; KaOS


Zuletzt bearbeitet von PitTux am 28.08.2013, 12:51 Uhr, insgesamt ein Mal bearbeitet
 
 Benutzer-Profile anzeigen Private Nachricht senden E-Mail senden MSN Messenger  
Antworten mit Zitat Nach oben
PitTux
15 Titel: Akonadi startet nicht  BeitragVerfasst am: 26.08.2013, 13:35 Uhr



Anmeldung: 26. Aug 2004
Beiträge: 1214
Wohnort: Hessen/Kassel-Fuldatal
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/PitTux/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


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/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 location varies depending on the distribution.

Test 4: SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.31-1 for debian-linux-gnu on x86_64 ((Debian))


Test 5: ERROR
--------

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

File content of '/home/PitTux/.local/share/akonadi/db_data/mysql.err':
130826 14:12:20 [Note] Plugin 'FEDERATED' is disabled.
130826 14:12:20 InnoDB: The InnoDB memory heap is disabled
130826 14:12:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130826 14:12:20 InnoDB: Compressed tables use zlib 1.2.7
130826 14:12:20 InnoDB: Using Linux native AIO
130826 14:12:20 InnoDB: Initializing buffer pool, size = 80.0M
130826 14:12:20 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 67108862 bytes
InnoDB: than specified in the .cnf file 0 67108864 bytes!
130826 14:12:20 [ERROR] Plugin 'InnoDB' init function returned error.
130826 14:12:20 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130826 14:12:20 [ERROR] Unknown/unsupported storage engine: innodb
130826 14:12:20 [ERROR] Aborting

130826 14:12:20 [Note] /usr/sbin/mysqld: Shutdown complete



Test 6: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/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]

# 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


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/PitTux/.local/share/akonadi/mysql.conf'>/home/PitTux/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/PitTux/.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]

# 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


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.9.2


Test 10: 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 11: 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 12: ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 13: 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 14: 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/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.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
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'

Test 15: 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/PitTux/.local/share/akonadi/akonadiserver.error'>/home/PitTux/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/PitTux/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/PitTux/.local/share/akonadi/mysql.conf", "--datadir=/home/PitTux/.local/share/akonadi/db_data/", "--socket=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418114]
1: akonadiserver() [0x418541]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x35260) [0x7f01d1548260]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f01d15481e5]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f01d154b398]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f01d2ff7912]
6: akonadiserver() [0x41a3eb]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f01d3092190]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11858d) [0x7f01d309f58d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f01d30a8173]
10: akonadiserver() [0x486dba]
11: akonadiserver() [0x41b0b7]
12: akonadiserver() [0x41ce65]
13: akonadiserver() [0x41e487]
14: akonadiserver() [0x411f43]
15: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f01d1534995]
16: akonadiserver() [0x4128d1]
]
"


Test 16: 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/PitTux/.local/share/akonadi/akonadiserver.error.old'>/home/PitTux/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/PitTux/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/PitTux/.local/share/akonadi/mysql.conf", "--datadir=/home/PitTux/.local/share/akonadi/db_data/", "--socket=/home/PitTux/.local/share/akonadi/socket-PitTuxBox/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418114]
1: akonadiserver() [0x418541]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x35260) [0x7f88fed86260]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f88fed861e5]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f88fed89398]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f8900835912]
6: akonadiserver() [0x41a3eb]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f89008d0190]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11858d) [0x7f89008dd58d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f89008e6173]
10: akonadiserver() [0x486dba]
11: akonadiserver() [0x41b0b7]
12: akonadiserver() [0x41ce65]
13: akonadiserver() [0x41e487]
14: akonadiserver() [0x411f43]
15: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f88fed72995]
16: akonadiserver() [0x4128d1]
]
"


Test 17: SUCCESS
--------

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

Test 18: SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Naja probieren geht über studieren???

_________________
ich habe zwar keine Lösung, bewundere aber das Problem
Quad Intel Core i3-4350T /Quad Intel Pentium N3540 - Linux 5.0.0-5-generic x86_64 [ Kanotix buster KDE KANOTIX-Build 20190202-15:53; KaOS
 
 Benutzer-Profile anzeigen Private Nachricht senden E-Mail senden MSN Messenger  
Antworten mit Zitat Nach oben
PitTux
Titel: Akonadi startet nicht  BeitragVerfasst am: 28.08.2013, 12:54 Uhr



Anmeldung: 26. Aug 2004
Beiträge: 1214
Wohnort: Hessen/Kassel-Fuldatal
Ordner home/usr/share/akonadi gelöscht, dann neu gestartet, hat das Problem behoben Winken

_________________
ich habe zwar keine Lösung, bewundere aber das Problem
Quad Intel Core i3-4350T /Quad Intel Pentium N3540 - Linux 5.0.0-5-generic x86_64 [ Kanotix buster KDE KANOTIX-Build 20190202-15:53; KaOS
 
 Benutzer-Profile anzeigen Private Nachricht senden E-Mail senden MSN Messenger  
Antworten mit Zitat Nach oben
Beiträge vom vorherigen Thema anzeigen:     
Gehe zu:  
Alle Zeiten sind GMT + 1 Stunde
Neues Thema eröffnen   Neue Antwort erstellen
Vorheriges Thema anzeigen Druckerfreundliche Version Einloggen, um private Nachrichten zu lesen Nächstes Thema anzeigen
PNphpBB2 © 2003-2007 
 
Deutsch | English
Logos and trademarks are the property of their respective owners, comments are property of their posters, the rest is © 2004 - 2006 by Jörg Schirottke (Kano).
Consult Impressum and Legal Terms for details. Kanotix is Free Software released under the GNU/GPL license.
This CMS is powered by PostNuke, all themes used at this site are released under the GNU/GPL license. designed and hosted by w3you. Our web server is running on Kanotix64-2006.