Bug#1015189: mariadb-server: stopping mariadb.service never finishes
Paul Gevers
Version: 1:10.6.8-1
Severity: important
Dear maintainer,
For a while now, I can't properly shut down my laptop, because MariaDb
doesn't finish gracefully.
I just ran a manual $(systemctl stop mariadb.service) to see if I
could spot what's going wrong but there is no output and I killed it
after 7 minutes.
Please let me know if there is more to test or try or if you need more
info from my system.
Paul
paul@mulciber ~ $ sudo systemctl stop mariadb.service
^C
paul@mulciber ~ $ sudo systemctl status mariadb.service
● mariadb.service - MariaDB 10.6.8 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) since Sun 2022-07-17 13:52:47 CEST; 7min ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 1043 (mariadbd)
Status: "Waiting to flush the buffer pool"
Tasks: 6 (limit: 4255)
Memory: 33.8M
CPU: 1min 9.598s
CGroup: /system.slice/mariadb.service
└─1043 /usr/sbin/mariadbd
jul 14 16:16:58 mulciber mariadbd[1043]: Version: '10.6.8-MariaDB-1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian buildd-unstable
jul 14 16:16:58 mulciber mariadbd[1043]: 2022-07-14 16:16:58 0 [Note] InnoDB: Buffer pool(s) load completed at 220714 16:16:58
jul 14 16:16:58 mulciber systemd[1]: Started MariaDB 10.6.8 database server.
jul 14 16:16:58 mulciber /etc/mysql/debian-start[1245]: Upgrading MySQL tables if necessary.
jul 17 13:52:47 mulciber systemd[1]: Stopping MariaDB 10.6.8 database server...
jul 17 13:52:47 mulciber mariadbd[1043]: 2022-07-17 13:52:47 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
jul 17 13:52:47 mulciber mariadbd[1043]: 2022-07-17 13:52:47 0 [Note] InnoDB: FTS optimize thread exiting.
jul 17 13:52:47 mulciber mariadbd[1043]: 2022-07-17 13:52:47 0 [Note] InnoDB: Starting shutdown...
jul 17 13:52:47 mulciber mariadbd[1043]: 2022-07-17 13:52:47 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
jul 17 13:52:47 mulciber mariadbd[1043]: 2022-07-17 13:52:47 0 [Note] InnoDB: Buffer pool(s) dump completed at 220717 13:52:47
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-server depends on:
ii mariadb-server-10.6 1:10.6.8-1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- no debconf information
Faustin Lammler
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
| 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
Paul Gevers
On 23-08-2022 13:10, Faustin Lammler wrote:
> Could you verify if you have still the pb with 10.6.9?
nicely. One addition test I did is that I hibernated once with
mariadb-server running, but also then I could stop it nicely. So, either
10.6.9 fixed the issue, or the root cause for the symptom went away somehow.
I suggest we close this bug, but I'll reopen it again if the problem
resurfaces.
Paul
Faustin Lammler
Paul Gevers <elb...@debian.org>,
23/08/2022 – 22:03:01 (+0200):
> After enabling mariadb-server again, at this moment I can indeed stop
> it nicely. One addition test I did is that I hibernated once with
> mariadb-server running, but also then I could stop it nicely. So,
> either 10.6.9 fixed the issue, or the root cause for the symptom went
> away somehow.
> I suggest we close this bug, but I'll reopen it again if the problem
> resurfaces.
--
Faustin