开发者社区> 问答> 正文

mysql无故崩溃,日志在此求问?报错

140727 21:04:38 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140727 21:04:38 [Note] Plugin 'FEDERATED' is disabled.
140727 21:04:38 InnoDB: The InnoDB memory heap is disabled
140727 21:04:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140727 21:04:38 InnoDB: Compressed tables use zlib 1.2.3.4
140727 21:04:38 InnoDB: Initializing buffer pool, size = 128.0M
140727 21:04:38 InnoDB: Completed initialization of buffer pool
140727 21:04:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140727 21:04:38  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 doublewrite
InnoDB: buffer...
140727 21:04:39  InnoDB: Waiting for the background threads to start
140727 21:04:40 InnoDB: 5.5.38 started; log sequence number 195543902
140727 21:04:40 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140727 21:04:40 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
140727 21:04:40 [Note] Server socket created on IP: '0.0.0.0'.
140727 21:04:41 [Note] Event Scheduler: Loaded 0 events
140727 21:04:41 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.38-0ubuntu0.12.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
140727 21:05:16 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140727 21:05:16 [Note] Plugin 'FEDERATED' is disabled.
140727 21:05:16 InnoDB: The InnoDB memory heap is disabled
140727 21:05:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140727 21:05:16 InnoDB: Compressed tables use zlib 1.2.3.4
140727 21:05:17 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140727 21:05:21 InnoDB: Completed initialization of buffer pool
140727 21:05:21 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140727 21:05:21 [ERROR] Plugin 'InnoDB' init function returned error.
140727 21:05:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140727 21:05:21 [ERROR] Unknown/unsupported storage engine: InnoDB
140727 21:05:21 [ERROR] Aborting


140727 21:05:22 [Note] /usr/sbin/mysqld: Shutdown complete

140727 21:05:23 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140727 21:05:23 [Note] Plugin 'FEDERATED' is disabled.
140727 21:05:23 InnoDB: The InnoDB memory heap is disabled
140727 21:05:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140727 21:05:23 InnoDB: Compressed tables use zlib 1.2.3.4
140727 21:05:23 InnoDB: Initializing buffer pool, size = 128.0M
140727 21:05:23 InnoDB: Completed initialization of buffer pool
140727 21:05:23 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140727 21:05:23  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 doublewrite
InnoDB: buffer...
140727 21:05:23  InnoDB: Waiting for the background threads to start
140727 21:05:24 InnoDB: 5.5.38 started; log sequence number 195543912
140727 21:05:24 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140727 21:05:24 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
140727 21:05:24 [Note] Server socket created on IP: '0.0.0.0'.
140727 21:05:24 [Note] Event Scheduler: Loaded 0 events
140727 21:05:24 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.38-0ubuntu0.12.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
140727 21:06:07 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140727 21:06:07 [Note] Plugin 'FEDERATED' is disabled.
140727 21:06:07 InnoDB: The InnoDB memory heap is disabled
140727 21:06:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140727 21:06:07 InnoDB: Compressed tables use zlib 1.2.3.4
140727 21:06:07 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140727 21:06:07 InnoDB: Completed initialization of buffer pool
140727 21:06:07 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140727 21:06:07 [ERROR] Plugin 'InnoDB' init function returned error.



这些都是从日志里面扒出来的……没有mysql报错调试的经验,请大家指正。

展开
收起
爱吃鱼的程序员 2020-06-15 19:43:20 553 0
1 条回答
写回答
取消 提交回答
  • https://developer.aliyun.com/profile/5yerqm5bn5yqg?spm=a2c6h.12873639.0.0.6eae304abcjaIB

    InnoDB:Fatalerror:cannotallocatememoryfor thebufferpool

    楼主看不懂英文?不会用搜索引擎?

    回复 @leo108: @leo108而且我不是没有百度啊,问题是众说纷纭啊……如果你觉得我的态度有问题,我可以反思我表达的方式。我真的一点mysql的挑错经验都没有。而且确实是正在百度。 @leo108而且你的语气是怎么回事? @leo108问题是我一点解决经验都没有,我在问你细节。给层主回血 只要删除MySQL目录下的ib_logfile0和ib_logfile1两个文件,就可以解决问题了。回复 @Tuesday:请问该如何解决呢?这可能成坑,注意innodb引擎.我觉得导出数据,重做一下mysql比较安全.这个……重做过……没有解决

    http://www.oschina.net/question/2962_115815

    我觉得问问题之前一定要先做做功课,OSC搜一下就发现有人问过一样的问题

    真心没搜到这个……

    会不会是 innodb_buffer_pool_size设置的太高了,超过了你的机器内存,请尝试降低该内存配置。

    使用innodb最好还是根据机器修改默认配置哦。

    之前没有设置过这个属性

    引用来自“玻璃渣”的评论

    会不会是 innodb_buffer_pool_size设置的太高了,超过了你的机器内存,请尝试降低该内存配置。

    使用innodb最好还是根据机器修改默认配置哦。

    之前没有修改过
    2020-06-15 19:43:37
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
PostgresChina2018_赖思超_PostgreSQL10_hash索引的WAL日志修改版final 立即下载
Kubernetes下日志实时采集、存储与计算实践 立即下载
日志数据采集与分析对接 立即下载

相关镜像