MariaDB restarts

SYSTEM INFORMATION
OS type and version Debian 12
Webmin version 2.105
Virtualmin version 7.9.0

It’s a big problem. MariaDB restarts all the time.

systemctl status mysql.service
● mariadb.service - MariaDB 10.11.6 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: signal) since Sun 2024-03-03 05:00:10 CET; 1s ago
Docs: man:mariadbd(8)
systemd - MariaDB Knowledge Base
Process: 63459 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 63460 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 63462 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=cd /usr/bin/..; /usr/bin/galera_recovery; [ $? -eq 0 ] && system>
Process: 63527 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 63539 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 63541 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Main PID: 63527 (code=killed, signal=ABRT)
Status: “Taking your SQL requests now…”
CPU: 806ms

journalctl -xe right after shows:
Mar 03 05:00:14 mydomain.com mariadbd[55221]: Core pattern: core
Mar 03 05:00:14 mydomain.com mariadbd[55221]: Kernel version: Linux version 6.1.0-18-cloud-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.>
Mar 03 05:00:14 mydomain.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process’ exit code is ‘killed’ and its exit status is 6.
Mar 03 05:00:14 mydomain.com systemd[1]: mariadb.service: Failed with result ‘signal’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ The unit mariadb.service has entered the ‘failed’ state with result ‘signal’.
Mar 03 05:00:16 mydomain.com systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 54.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ Automatic restarting of the unit mariadb.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Mar 03 05:00:16 mydomain.com systemd[1]: Stopped mariadb.service - MariaDB 10.11.6 database server.
░░ Subject: A stop job for unit mariadb.service has finished
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A stop job for unit mariadb.service has finished.
░░
░░ The job identifier is 39346 and the job result is done.
Mar 03 05:00:16 mydomain.com systemd[1]: Starting mariadb.service - MariaDB 10.11.6 database server…
░░ Subject: A start job for unit mariadb.service has begun execution
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A start job for unit mariadb.service has begun execution.
░░
░░ The job identifier is 39346.

There are just seconds between the restarts.
It works in a few seconds.
I would appreciate some help, please

OOM killer, almost certainly. You probably don’t have enough memory for the amount of stuff you’re running on the system.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.