Hey Otto
$ pgrep -x --nslist pid --ns $$ "mysqld|mariadbd"
362286
$ pgrep -af "mysql|mariadb"
362286 /usr/sbin/mysqld
--defaults-file=/home/username/.local/share/akonadi/mysql.conf
--datadir=/home/username/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid
The akonadiserver is controlled by
[email protected], so that's what I stopped for
the upgrade. I don't use the KDE calendar or the rest of the KDE PIM
suite, so I don't know if it was really a good idea to just interrupt
this service. I also have no clue how akonadi-backend-mysql would
handle mysqld/mariadbd upgrades.
Would it be a good idea to limit the search for running
mysqlds/mariadbds to those run by the mysql user (and perhaps root)?
Greetings
-Steven
On 27/02/2023 06:46, Otto Kekäläinen wrote:
Hi!
Thanks for reporting this. What does the exact process listing look
like on a system that has the Akonadi server running?
What do these commands below yield on your system?
pgrep -x --nslist pid --ns $$ "mysqld|mariadbd"
pgrep -af "mysql|mariadb"
Indeed, the preinst has a section where it tries to stop any existing
servers. This section has been there for years and years, this is
nothing new in 10.11. Maybe it should have an extra check for Akonadi
in particular, or maybe some trigger for Akonadi to restart the
embedded MariaDB it has.
