MySQL 近两三个月莫名其妙停止两次了

2022-04-10 11:11:37 +08:00
 tlerbao

MySQL 近两三个月莫名其妙停止两次了。

下面是日志,具体是什么原因呢,看不懂。

凌晨 3 点有备份数据库到阿里云 OSS 的计划任务,难道是备份数据库导致的,意外停止?


2022-04-10 01:45:33 27880 [Note] Plugin 'FEDERATED' is disabled.
2022-04-10 01:45:33 27880 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-04-10 01:45:33 27880 [Note] InnoDB: The InnoDB memory heap is disabled
2022-04-10 01:45:33 27880 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-04-10 01:45:33 27880 [Note] InnoDB: Memory barrier is not used
2022-04-10 01:45:33 27880 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-10 01:45:33 27880 [Note] InnoDB: Using Linux native AIO
2022-04-10 01:45:33 27880 [Note] InnoDB: Using CPU crc32 instructions
2022-04-10 01:45:33 27880 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2022-04-10 01:45:33 27880 [Note] InnoDB: Completed initialization of buffer pool
2022-04-10 01:45:33 27880 [Note] InnoDB: Highest supported file format is Barracuda.
2022-04-10 01:45:33 27880 [Note] InnoDB: The log sequence numbers 18031304 and 18031304 in ibdata files do not match the log sequence number 38084462 in the ib_logfiles!
2022-04-10 01:45:33 27880 [Note] InnoDB: Database was not shutdown normally!
2022-04-10 01:45:33 27880 [Note] InnoDB: Starting crash recovery.
2022-04-10 01:45:33 27880 [Note] InnoDB: Reading tablespace information from the .ibd files...
2022-04-10 01:45:33 27880 [Note] InnoDB: Restoring possible half-written data pages 
2022-04-10 01:45:33 27880 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 292392, file name mysql-bin.000549
2022-04-10 01:45:34 27880 [Note] InnoDB: 128 rollback segment(s) are active.
2022-04-10 01:45:34 27880 [Note] InnoDB: Waiting for purge to start
2022-04-10 01:45:34 27880 [Note] InnoDB: 5.6.50 started; log sequence number 38084462
2022-04-10 01:45:34 27880 [Note] Recovering after a crash using mysql-bin
2022-04-10 01:45:34 27880 [Note] Starting crash recovery...
2022-04-10 01:45:34 27880 [Note] Crash recovery finished.
2022-04-10 01:45:35 27880 [Note] RSA private key file not found: /www/server/data//private_key.pem. Some authentication plugins will not work.
2022-04-10 01:45:35 27880 [Note] RSA public key file not found: /www/server/data//public_key.pem. Some authentication plugins will not work.
2022-04-10 01:45:35 27880 [Note] Server hostname (bind-address): '*'; port: 3306
2022-04-10 01:45:35 27880 [Note] IPv6 is available.
2022-04-10 01:45:35 27880 [Note]   - '::' resolves to '::';
2022-04-10 01:45:35 27880 [Note] Server socket created on IP: '::'.
2022-04-10 01:45:35 27880 [Warning] Insecure configuration for --pid-file: Location '/www/server/data' in the path is accessible to all OS users. Consider choosing a different directory.
2022-04-10 01:45:38 27880 [Note] Event Scheduler: Loaded 0 events
2022-04-10 01:45:38 27880 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.6.50-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
2022-04-10 03:00:19 32674 [Note] Plugin 'FEDERATED' is disabled.
2022-04-10 03:00:19 32674 [Note] InnoDB: Using atomics to ref count buffer pool pages
2022-04-10 03:00:19 32674 [Note] InnoDB: The InnoDB memory heap is disabled
2022-04-10 03:00:19 32674 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-04-10 03:00:19 32674 [Note] InnoDB: Memory barrier is not used
2022-04-10 03:00:19 32674 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-10 03:00:19 32674 [Note] InnoDB: Using Linux native AIO
2022-04-10 03:00:20 32674 [Note] InnoDB: Using CPU crc32 instructions
2022-04-10 03:00:20 32674 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2022-04-10 03:00:20 32674 [Note] InnoDB: Completed initialization of buffer pool
2022-04-10 03:00:33 32674 [Note] InnoDB: Highest supported file format is Barracuda.
2022-04-10 03:01:06 32674 [Note] InnoDB: The log sequence numbers 18031304 and 18031304 in ibdata files do not match the log sequence number 38084472 in the ib_logfiles!
2022-04-10 03:01:15 32674 [Note] InnoDB: Database was not shutdown normally!
2022-04-10 03:01:18 32674 [Note] InnoDB: Starting crash recovery.
2022-04-10 03:01:24 32674 [Note] InnoDB: Reading tablespace information from the .ibd files...
1310 次点击
所在节点    问与答
3 条回复
Chism
2022-04-10 11:28:34 +08:00
我遇到过的停止是因为内存太小
CEBBCAT
2022-04-10 13:20:14 +08:00
你这贴的是不是启动日志?可以上云的话就上云吧
kingjpa
2022-04-10 17:03:22 +08:00
我之前遇到和 1 楼一样,是内存很小导致,当时主机只有 512 内存, 后来挂载 swap 分区 成功解决

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/846035

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX