MariaDB v5不断重启

dzjeubhm  于 2022-11-08  发布在  其他
关注(0)|答案(1)|浏览(199)

我有一个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负载i约为0.1服务器内存使用率约为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

有什么想法吗?

xwbd5t1u

xwbd5t1u1#

这个关闭是由一个TERM信号引起的。这通常是用killall mysqld或kill $(pidof mysqld)来完成的。
如果您在systemd下运行,则TErm信号方法也是systemctl stop mariadb. service中使用的默认方法。

相关问题