您的位置:首页技术文章
文章详情页

mysql自动关闭,日志看不懂,希望大神解读下

【字号: 日期:2022-06-22 09:03:57浏览:62作者:猪猪

问题描述

Version: ’5.5.48’ socket: ’/tmp/mysql.sock’ port: 3306 Source distribution160515 14:15:17 mysqld_safe Number of processes running now: 0160515 14:15:17 mysqld_safe mysqld restarted160515 14:15:17 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:15:17 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:15:17 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 23912 ...160515 14:15:18 [Note] Plugin ’FEDERATED’ is disabled.160515 14:15:18 InnoDB: The InnoDB memory heap is disabled160515 14:15:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins160515 14:15:18 InnoDB: Compressed tables use zlib 1.2.7160515 14:15:18 InnoDB: Initializing buffer pool, size = 128.0M160515 14:15:18 InnoDB: Completed initialization of buffer pool160515 14:15:18 InnoDB: highest supported file format is Barracuda.InnoDB: The log sequence number in ibdata files does not matchInnoDB: the log sequence number in the ib_logfiles!160515 14:15:18 InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer...160515 14:15:18 InnoDB: Waiting for the background threads to start160515 14:15:19 InnoDB: 5.5.48 started; log sequence number 1667632160515 14:15:19 [Note] Server hostname (bind-address): ’0.0.0.0’; port: 3306160515 14:15:19 [Note] - ’0.0.0.0’ resolves to ’0.0.0.0’;160515 14:15:19 [Note] Server socket created on IP: ’0.0.0.0’.160515 14:15:19 [Note] Event Scheduler: Loaded 0 events160515 14:15:19 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: ready for connections.Version: ’5.5.48’ socket: ’/tmp/mysql.sock’ port: 3306 Source distribution160515 14:35:28 mysqld_safe Number of processes running now: 0160515 14:35:28 mysqld_safe mysqld restarted160515 14:35:29 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:35:29 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:35:29 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 24389 ...160515 14:35:29 [Note] Plugin ’FEDERATED’ is disabled.160515 14:35:29 InnoDB: The InnoDB memory heap is disabled160515 14:35:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins160515 14:35:29 InnoDB: Compressed tables use zlib 1.2.7160515 14:35:29 InnoDB: Initializing buffer pool, size = 128.0MInnoDB: mmap(137363456 bytes) failed; errno 12160515 14:35:29 InnoDB: Completed initialization of buffer pool160515 14:35:29 InnoDB: Fatal error: cannot allocate memory for the buffer pool160515 14:35:29 [ERROR] Plugin ’InnoDB’ init function returned error.160515 14:35:29 [ERROR] Plugin ’InnoDB’ registration as a STORAGE ENGINE failed.160515 14:35:29 [ERROR] Unknown/unsupported storage engine: InnoDB160515 14:35:29 [ERROR] Aborting

160515 14:35:29 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: Shutdown complete

160515 14:35:29 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.5.48/data/iZ236zu4tgyZ.pid ended160515 14:58:19 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.5.48/data160515 14:58:19 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:58:19 [Warning] ’THREAD_CONCURRENCY’ is deprecated and will be removed in a future release.160515 14:58:19 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 25030 ...160515 14:58:19 [Note] Plugin ’FEDERATED’ is disabled.160515 14:58:19 InnoDB: The InnoDB memory heap is disabled160515 14:58:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins160515 14:58:19 InnoDB: Compressed tables use zlib 1.2.7160515 14:58:19 InnoDB: Initializing buffer pool, size = 128.0M160515 14:58:19 InnoDB: Completed initialization of buffer pool160515 14:58:19 InnoDB: highest supported file format is Barracuda.InnoDB: The log sequence number in ibdata files does not matchInnoDB: the log sequence number in the ib_logfiles!160515 14:58:19 InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer...160515 14:58:19 InnoDB: Waiting for the background threads to start160515 14:58:20 InnoDB: 5.5.48 started; log sequence number 1667642160515 14:58:20 [Note] Server hostname (bind-address): ’0.0.0.0’; port: 3306160515 14:58:20 [Note] - ’0.0.0.0’ resolves to ’0.0.0.0’;160515 14:58:20 [Note] Server socket created on IP: ’0.0.0.0’.160515 14:58:20 [Note] Event Scheduler: Loaded 0 events160515 14:58:20 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: ready for connections.Version: ’5.5.48’ socket: ’/tmp/mysql.sock’ port: 3306 Source distribution

上面的关闭这段时间的错误日志内容,大概是怎么一回事额

问题解答

回答1:

160515 14:35:29 InnoDB: Fatal error: cannot allocate memory for the buffer pool

看这个是机器内存太小,innodb的的buffer pool分配内存失败