https://bugs.kde.org/show_bug.cgi?id=310381
Bug ID: 310381
Severity: normal
Version: 4.9
Priority: NOR
Assignee: kdepim-bugs@kde.org
Summary: Akonadi server selftest fail
Classification: Unclassified
OS: Linux
Reporter: roze...@volny.cz
Hardware: Archlinux Packages
Status: UNCONFIRMED
Component: server
Product: Akonadi
When starting kontact after plasma crash (see bug 309223) and computer reboot
(through logout, reboot menu items), Akonadi server fails wilth the following
error:
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/dtihelka/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/dtihelka/.local/share/akonadi/socket-uk508n02-kky/mysql.socket"
ServerPath=/usr/bin/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/bin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
s
erver executable is typically called 'mysqld'; its location varies depending on
the distribution.
Test 4: SUCCESS
--------
MySQL server is executable.
Details: MySQL server found: /usr/bin/mysqld Ver 5.5.28-log for Linux on
x86_64 (Source distribution)
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a
href='/home/dtihelka/.local/share/akonadi/db_data/mysql.err'>/home/dtihelka/.local/share/akonadi/db_data/mysq
l.err</a>' contains errors.
File content of '/home/dtihelka/.local/share/akonadi/db_data/mysql.err':
121119 21:38:43 InnoDB: The InnoDB memory heap is disabled
121119 21:38:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121119 21:38:43 InnoDB: Compressed tables use zlib 1.2.7
121119 21:38:43 InnoDB: Initializing buffer pool, size = 80.0M
121119 21:38:43 InnoDB: Completed initialization of buffer pool
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.
121119 21:38:43 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.
Reproducible: Didn't try
Well, I suppose that the error is more likely connected with MySQL, but I think
it is related to the crash of KDE desktop, which requires the restart of KDE.
It occures despite the fact that I invoked "logout" through Alt+F2 runner and
choose "restart" in kdm screen then.
What to do to make kontact running again?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
