Dear all, I have found that at least in my case sending a SIGSTOP followed by a SIGCONT to the MariaDB process, i.e., kill -STOP $(pgrep -f mariadb) ; kill -CONT $(pgrep -f mariadb)
is sufficient to bring it back to life. I believe this approach has fewer side effects compared to using SIGKILL. Also attaching gdb and detaching it works, too, this is how I found out about this. Best regards, Max On Tue, 21 Jan 2025 20:06:18 +0100 Bernhard Schmidt <be...@debian.org> wrote: > When you kill one client process you can connect and issue "show > processlist", you see all slots busy with easy update/select queries > that have been running for hours. You need to SIGKILL mariadbd to > recover.
