[debian-mysql] Bug#829489: Bug#829489: mariadb-server-10.0: Fails to stop, package can't be uninstalled/purged

[Otto Kekäläinen]

Thanks for looking into MariaDB.

2016-07-03 21:42 GMT+03:00 Axel Beckert <abe at debian.org>:
> Removing mariadb-server-10.0 (10.0.26-1) ...
> [FAIL] Stopping MariaDB database server: mysqld failed!
> invoke-rc.d: initscript mysql, action "stop" failed.
> dpkg: error processing package mariadb-server-10.0 (--purge):
>  subprocess installed pre-removal script returned error exit status 1
> [FAIL] Stopping MariaDB database server: mysqld failed!
> invoke-rc.d: initscript mysql, action "stop" failed.

What happens here is that the prerm script invokes the MariaDB service
and tries to stop it. For some reason the mysqld daemon does not die,
and thus the service script emits an error, which the prerm script in
turn sees as an error code and assumes that prerm step failed,
aborting further dpkg operations for that package.

There are many potential reasons why mysqld failed to die. Check the
syslog or /var/log/mysql/* logs.

What do you suggest here? To proceed with pruging the package even if
the mysqld daemon is running? Users expect the service to stop on
removal.

Maybe you can come up with some nice logic in the prerm script to
handle this kind of scenario?

I am happy to accept patches. The prerm script in mysql-5.6 is
identical, you if you make a patch, it can and should be applied to
both variants.