Akonadi does not run anymore
Alexandre
alexandre at linuxfr.eu
Tue Jun 9 21:27:43 BST 2020
Hello KDE,
I've asked some questions on IRC in the past few weeks, and haven't got an
answer form #akonadi.
So as per the channel topic, I'm emailing you now.
Having the same Debian testing system up-to-date on both my computers,
akonadi on my laptop fails to start (for about 2 weeks now).
When I launch akonadiconsole, it complains about not being able to connect to
mysql (while the server is running correctly)
When I click on the 'Details...' button to get more details about the error, nothing
is shown.
Checking the log file in ~/.local/share/akonadi/Akonadi.error I can see:
```
2020-06-09T09:47:50 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi
Server...
2020-06-09T09:48:55 [CRITICAL] org.kde.pim.akonadis2020-06-09T09:49:01 [INFO ]
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
"Can't connect to local MySQL server through socket '/run/user/1000/akonadi/
mysql.socket' (2) QMYSQL: Unable to connect"
2020-06-09T09:49:01 [INFO ] org.kde.pim.akonadiserver: Shutting down
AkonadiServer...
```
I can see the mysql (mariadb really) server running using ps:
```
/usr/sbin/mysqld --defaults-file=/home/user/.local/share/akonadi/mysql.conf --
datadir=/home/user/.local/share/akonadi/db_data/ --socket=/run/user/1000/
akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid
```...however there are indeed no sockets in /run/user/1000/akonadi/, only two
sockets named akonadiserver-cmd.socket and akonadiserver-ntf.socket.
Weirdly on my main computer where akonadi still works normally, I have no such
`/run/user/1000/akonadi/` directory shown (and my user id is 1000).
I've found a bug report that says using another locale that en_US for the 'lc-
messages' settings in my.cnf could prevent the mariadb server to run.
However I forced it to en_US (it wasn't set before) in ~/.local/share/akonadi/
mysql.conf, without any success.
(see https://jira.mariadb.org/browse/MDEV-21600[1] and https://bugs.debian.org/
cgi-bin/bugreport.cgi?bug=951059[2] )
Lastly, in `~/.local/share/akonadi/db_data/mysql.err, I have those messages:
```
» cat mysql.err
2020-06-09 9:47:50 0 [ERROR] mysqld: Can't lock aria control file '/home/
user/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11.
Will retry for 30 seconds
2020-06-09 9:48:21 0 [ERROR] mysqld: Got error 'Could not get an exclusive lock;
file is probably in use by another process' when trying to use aria control file '/
home/user/.local/share/akonadi/db_data/aria_log_control'
2020-06-09 9:48:21 0 [ERROR] Plugin 'Aria' init function returned error.
2020-06-09 9:48:21 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE
failed.
2020-06-09 9:48:21 0 [Note] InnoDB: Using Linux native AIO
2020-06-09 9:48:21 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic
builtins
2020-06-09 9:48:21 0 [Note] InnoDB: Uses event mutexes
2020-06-09 9:48:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-06-09 9:48:21 0 [Note] InnoDB: Number of pools: 1
2020-06-09 9:48:21 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-06-09 9:48:21 0 [Note] InnoDB: Initializing buffer pool, total size = 128M,
instances = 1, chunk size = 128M
2020-06-09 9:48:21 0 [Note] InnoDB: Completed initialization of buffer pool
2020-06-09 9:48:21 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-09 9:48:21 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:21 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:21 0 [Note] InnoDB: Retrying to lock the first data file
2020-06-09 9:48:22 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:22 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:23 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:23 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:24 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:24 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:25 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:25 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:26 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:26 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:27 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:27 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:28 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:28 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:29 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:29 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:30 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:30 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
2020-06-09 9:48:31 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-06-09 9:48:31 0 [Note] InnoDB: Check that you do not already have another
mysqld process using the same InnoDB data or log files.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20200609/e584d728/attachment-0001.htm>
More information about the kde-pim
mailing list