MariaDB v5 不斷重啟

Question

我有一台Centos7服務器，MariaDB服務器已經開始玩起來了。 每隔 20 秒左右，無論白天還是黑夜，它都會重新啟動，沒有明顯的錯誤導致此問題。日志重復如下：

Aug 13 11:16:10 instance-1 systemd: Stopping MariaDB database server...
Aug 13 11:16:13 instance-1 systemd: Stopped MariaDB database server.
Aug 13 11:16:13 instance-1 systemd: Starting MariaDB database server...
Aug 13 11:16:13 instance-1 mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Aug 13 11:16:13 instance-1 mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Aug 13 11:16:13 instance-1 mysqld_safe: 220813 11:16:13 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Aug 13 11:16:13 instance-1 mysqld_safe: 220813 11:16:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Aug 13 11:16:15 instance-1 systemd: Started MariaDB database server.
Aug 13 11:16:45 instance-1 systemd: Stopping MariaDB database server...
Aug 13 11:16:49 instance-1 systemd: Stopped MariaDB database server.
Aug 13 11:16:49 instance-1 systemd: Starting MariaDB database server...
Aug 13 11:16:49 instance-1 mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Aug 13 11:16:49 instance-1 mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Aug 13 11:16:49 instance-1 mysqld_safe: 220813 11:16:49 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Aug 13 11:16:49 instance-1 mysqld_safe: 220813 11:16:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Aug 13 11:16:51 instance-1 systemd: Started MariaDB database server.

cpu load i 大約 0.1 服務器 memory 使用率約為 40% 使用中沒有交換。

這使得在服務器在完成之前關閉時無法進行任何數據庫轉儲。 停止 http 沒有區別，所以即使沒有查詢，它仍然像這樣循環

這是 /var/log/mariadb/mariadb.log 的一部分：

Version: '5.5.68-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
220813 11:25:41 [Note] /usr/libexec/mysqld: Normal shutdown
220813 11:25:41 [Note] Event Scheduler: Purging the queue. 0 events
220813 11:25:41  InnoDB: Starting shutdown...
220813 11:25:44  InnoDB: Shutdown completed; log sequence number 28842439769
220813 11:25:44 [Note] /usr/libexec/mysqld: Shutdown complete

220813 11:25:44 mysqld_safe mysqld from pid file /run/mariadb/mariadb.pid ended
220813 11:25:45 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
220813 11:25:45 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 22908 ...
220813 11:25:45 InnoDB: The InnoDB memory heap is disabled
220813 11:25:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
220813 11:25:45 InnoDB: Compressed tables use zlib 1.2.7
220813 11:25:45 InnoDB: Using Linux native AIO
220813 11:25:45 InnoDB: Initializing buffer pool, size = 128.0M
220813 11:25:45 InnoDB: Completed initialization of buffer pool
220813 11:25:45 InnoDB: highest supported file format is Barracuda.
220813 11:25:45  InnoDB: Waiting for the background threads to start
220813 11:25:46 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 28842439769
220813 11:25:46 [Note] Plugin 'FEEDBACK' is disabled.
220813 11:25:46 [Note] Server socket created on IP: '0.0.0.0'.
220813 11:25:46 [Note] Event Scheduler: Loaded 0 events
220813 11:25:46 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.68-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

有任何想法嗎？

Answer 1

這次關閉是由 TERM 信號引發的。 這通常使用 killall mysqld 或 kill $(pidof mysqld) 來完成。

如果您在 systemd 下運行，則 TERm 信號方法也是 systemctl stop mariadb.service 中使用的默認方法。