After a while akonadi is crashing, because of a communication error. The MySQL sockets seems to disappear, even if the MySQL server is still running. # MySQL Server still running after Akonadi crash /usr/sbin/mysqld-akonadi --defaults-file=/home/maltegerth/.local/share/akonadi/mysql.conf --datadir=/home/maltegerth/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid # Socket file is missing $ ll /run/user/1000/akonadi/mysql.socket ls: cannot access '/run/user/1000/akonadi/mysql.socket': No such file or directory # Akonadi error log 2020-06-29T21:17:29 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi Server... 2020-06-29T21:18:34 [CRITICAL] org.kde.pim.akonadiserver: Failed to connect to database! 2020-06-29T21:18:34 [CRITICAL] org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2) QMYSQL: Unable to connect" 2020-06-29T21:18:40 [INFO ] org.kde.pim.akonadiserver: Shutting down AkonadiServer.. # MySQL error log 2020-06-29 21:17:29 0 [ERROR] mysqld-akonadi: Can't lock aria control file '/home/maltegerth/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds 2020-06-29 21:18:00 0 [ERROR] mysqld-akonadi: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/maltegerth/.local/share/akonadi/db_data/aria_log_control' 2020-06-29 21:18:00 0 [ERROR] Plugin 'Aria' init function returned error. 2020-06-29 21:18:00 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2020-06-29 21:18:00 0 [Note] InnoDB: Using Linux native AIO 2020-06-29 21:18:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-06-29 21:18:00 0 [Note] InnoDB: Uses event mutexes 2020-06-29 21:18:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-06-29 21:18:00 0 [Note] InnoDB: Number of pools: 1 2020-06-29 21:18:00 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-06-29 21:18:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-06-29 21:18:00 0 [Note] InnoDB: Completed initialization of buffer pool 2020-06-29 21:18:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-06-29 21:18:00 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-29 21:18:00 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-06-29 21:18:00 0 [Note] InnoDB: Retrying to lock the first data file 2020-06-29 21:18:01 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-29 21:18:01 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-06-29 21:18:02 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
I experience the same with KDE Neon: Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-111-generic The issue disappears after deleting all *akonadi* files in $HOME/. However, after some new boots (max. three) the issue is back. Also I tried to reinstall all Akonadi and Kontact modules - no success, same behavior. Help is needed please. Happy to support!
Created attachment 130272 [details] akonadictl start log
Additionally worth to be mentioned: I am running akonadi on another computer with openSUSE Tumbleweed: Operating System: openSUSE Tumbleweed 20200717 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.7-1-default On that computer there is NO issue with akonadi.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
(In reply to Justin Zobel from comment #4) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Hi Justin, I am sorry but meanwhile I moved to Evolution. I have uninstalled all Akonadi and Kontact modules. Best regards Sebastian
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!