[debian-mysql] Bug#1015189: Bug#1015189: mariadb-server: stopping mariadb.service never finishes

[Faustin Lammler]

Hi Paul!
I am not able to reproduce this with 10.6.9, at least in containers
with:

| podman run --name 1015189 --rm -d fauust/docker-systemd:debian-sid
| podman exec -it 1015189 bash -c "apt-get update \
|   && apt-get -y install mariadb-server \
|   && systemctl start mariadb \
|   && systemctl stop mariadb \
|   && systemctl status mariadb"
| ...
| ○ mariadb.service - MariaDB 10.6.9 database server
|      Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
|      Active: inactive (dead) since Tue 2022-08-23 11:02:36 UTC; 55ms ago
|    Duration: 11ms
|        Docs: man:mariadbd(8)
|              https://mariadb.com/kb/en/library/systemd/
|     Process: 1124 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
|     Process: 1125 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
|     Process: 1127 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
|     Process: 1156 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
|     Process: 1169 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
|     Process: 1171 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
|    Main PID: 1156 (code=exited, status=0/SUCCESS)
|      Status: "MariaDB server is down"
|         CPU: 204ms
| 
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: FTS optimize thread exiting.
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Starting shutdown...
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Buffer pool(s) dump completed at 220823 11:02:35
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] InnoDB: Shutdown completed; log sequence number 42159; transaction id 15
| Aug 23 11:02:35 32a0256b22b9 mariadbd[1156]: 2022-08-23 11:02:35 0 [Note] /usr/sbin/mariadbd: Shutdown complete
| Aug 23 11:02:36 32a0256b22b9 systemd[1]: mariadb.service: Deactivated successfully.
| Aug 23 11:02:36 32a0256b22b9 systemd[1]: Stopped MariaDB 10.6.9 database server.

Could you verify if you have still the pb with 10.6.9?
Could you also verify if you have the pb with 10.6.9 from MariaDB repo
(https://mariadb.org/downloads)?

Depending on the previous, could you maybe share with me the content of
the DB and the configuration so I could try to reproduce it locally (and
in a VM since podman is probably not the best way to debug systemd
services).

Also, if this is not related to Debian packaging, I suggest you report
this directly upstream at https://jira.mariadb.org, I could not find any
relevant issue there so far.

Cheers!

-- 
Faustin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20220823/eb6ce488/attachment.sig>