2 u010714784 u010714784 于 2014.12.17 18:48 提问

mysql经常挂掉,重启主机就好了

mysq日志

141211 10:50:25 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
141211 10:50:26 [Note] Plugin 'FEDERATED' is disabled.
141211 10:50:26 InnoDB: The InnoDB memory heap is disabled
141211 10:50:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141211 10:50:26 InnoDB: Compressed tables use zlib 1.2.3
141211 10:50:26 InnoDB: Using Linux native AIO
141211 10:50:26 InnoDB: Initializing buffer pool, size = 128.0M
141211 10:50:26 InnoDB: Completed initialization of buffer pool
141211 10:50:26 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!
141211 10:50:26 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...
141211 10:50:27 InnoDB: Waiting for the background threads to start
141211 10:50:28 InnoDB: 5.5.37 started; log sequence number 1595675
141211 10:50:28 [Note] Recovering after a crash using mysql-bin
141211 10:50:28 [Note] Starting crash recovery...
141211 10:50:28 [Note] Crash recovery finished.
141211 10:50:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141211 10:50:28 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141211 10:50:28 [Note] Server socket created on IP: '0.0.0.0'.
141211 10:50:28 [Note] Event Scheduler: Loaded 0 events
141211 10:50:28 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
141211 10:53:25 [Note] /alidata/server/mysql/bin/mysqld: Normal shutdown

141211 10:53:25 [Note] Event Scheduler: Purging the queue. 0 events
141211 10:53:25 InnoDB: Starting shutdown...
141211 10:53:26 InnoDB: Shutdown completed; log sequence number 1595675
141211 10:53:26 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete

141211 10:53:26 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
141211 10:57:45 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
141211 10:57:46 [Note] Plugin 'FEDERATED' is disabled.
141211 10:57:46 InnoDB: The InnoDB memory heap is disabled
141211 10:57:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141211 10:57:46 InnoDB: Compressed tables use zlib 1.2.3
141211 10:57:46 InnoDB: Using Linux native AIO
141211 10:57:46 InnoDB: Initializing buffer pool, size = 128.0M
141211 10:57:46 InnoDB: Completed initialization of buffer pool
141211 10:57:46 InnoDB: highest supported file format is Barracuda.
141211 10:57:46 InnoDB: Waiting for the background threads to start
141211 10:57:47 InnoDB: 5.5.37 started; log sequence number 1595675
141211 10:57:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141211 10:57:47 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141211 10:57:47 [Note] Server socket created on IP: '0.0.0.0'.
141211 10:57:47 [Note] Event Scheduler: Loaded 0 events
141211 10:57:47 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
141213 21:56:24 [Warning] IP address '42.156.250.117' could not be resolved: Name or service not known
141215 0:09:33 [Warning] IP address '107.150.52.84' could not be resolved: Name or service not known
141215 2:23:23 [Warning] IP address '114.113.55.141' could not be resolved: Name or service not known
141215 16:43:01 [Warning] IP address '61.156.44.98' could not be resolved: Name or service not known
141216 21:56:28 [Warning] IP address '42.120.142.220' could not be resolved: Name or service not known
141217 11:07:01 mysqld_safe Number of processes running now: 0
141217 11:07:01 mysqld_safe mysqld restarted
141217 11:07:01 [Note] Plugin 'FEDERATED' is disabled.
141217 11:07:01 InnoDB: The InnoDB memory heap is disabled
141217 11:07:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141217 11:07:01 InnoDB: Compressed tables use zlib 1.2.3
141217 11:07:01 InnoDB: Using Linux native AIO
141217 11:07:01 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141217 11:07:01 InnoDB: Completed initialization of buffer pool
141217 11:07:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141217 11:07:01 [ERROR] Plugin 'InnoDB' init function returned error.
141217 11:07:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141217 11:07:01 [ERROR] Unknown/unsupported storage engine: InnoDB
141217 11:07:01 [ERROR] Aborting

141217 11:07:01 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete

141217 11:07:01 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
141217 11:09:15 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
141217 11:09:15 [Note] Plugin 'FEDERATED' is disabled.
141217 11:09:15 InnoDB: The InnoDB memory heap is disabled
141217 11:09:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141217 11:09:15 InnoDB: Compressed tables use zlib 1.2.3
141217 11:09:15 InnoDB: Using Linux native AIO
141217 11:09:15 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141217 11:09:15 InnoDB: Completed initialization of buffer pool
141217 11:09:15 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141217 11:09:15 [ERROR] Plugin 'InnoDB' init function returned error.
141217 11:09:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141217 11:09:15 [ERROR] Unknown/unsupported storage engine: InnoDB
141217 11:09:15 [ERROR] Aborting

141217 11:09:15 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete

141217 11:09:15 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended

1个回答

ACMAIN_CHM
ACMAIN_CHM   Ds   Rxr 2014.12.17 23:04

关闭机器的杀毒软件和防火墙然后再试。

Csdn user default icon
上传中...
上传图片
插入图片
准确详细的回答,更有利于被提问者采纳,从而获得C币。复制、灌水、广告等回答会被删除,是时候展现真正的技术了!
其他相关推荐
阿里云服务器 mysql经常自动停止挂掉重启的完美解决方式
阿里云服务器 MySQL 经常自动停止、挂掉、重启。 打开 MySQL 的 error.log 错误信息,在阿里云 CentOS 的路径为 /alidata/log/mysql/error.log,如下: 2016-03-13 00:16:37 0[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please us
服务器经常挂掉的6个原因
如果没有任何经验,学习如何扩展一个网站是相当困难的。假设现在你有很多像highscalability.com那样网站,你需要一些好的解决方案来扩展它们,但是世上没有“万能药”,没有哪个解决方案可以适应所有网站的需要。你不得不自己动手,通过不断地思考来找到一个能满足你的需求的解决方案。我也是这样做的。 几年以前,我的老板来找我,然后对我说:“我们有一个新项目想交给你来做。主要是一个网站的重构,
关于MySQL数据库 启动之后使用一段时间挂掉问题
问题发生的场景 mysql 日志 问题解决方法 问题发生的场景 由于本人在自己的云服务器上搭建了一套网站系统,主要用于各种实验用。在前两天偶想起自己的博客好久没有更新了,自己堕落成这样。于是在chrome 地址栏中熟练的输入我那令人魂牵梦绕的博客地址。回车一按,傻眼了。五姑娘废了。。。。 上服务器上一看。原来是MySQL服务器挂了,果然还是自己太嫩。当初考虑问题太简单。...
今天服务器挂了 OA服务停止 紧张半死。。。 最后原来是数据库死锁
<br />今天服务器挂了  OA服务停止  紧张半死。。。  最后原来是数据库死锁<br /> <br /> <br />物理重新启动 就可以了,不过治标不治本。<br /> <br /> <br />长个经验吧。
网站发布以后频繁不能访问,需要重启IIS服务才能正常工作的解决办法
公司的网站经常出现不能正常访问e
别让你的mongodb宕机了
接下来就要面临双十一这场惊心动魄的处女秀考验, 我们项目中会有一个wcf集群,而集群地址则放在mongodb中,所以mongodb的核心地位可想而知,如果mongodb挂掉,整个项目也就陷入 瘫痪,想让mongodb不宕机,最简单的方法就是要做双机热备,跟传统的关系型数据库的双机热备模式一样,一个主服务器,一个备份服务器, 一个仲裁服务器。如果热备集群中的主服务器宕掉,会有仲裁服务器参与投票
hadoop 2 datanode 经常自动挂掉原因
最近在VMware上部署了Hadoop2的集群,
“电脑突然没声音,重启后正常”的解决办法
故障说明: 整个系统如果没有任何声音,重启以后正常! 分析过程: 之前也偶尔遇到过,重启就好了,所以就没足够重视! 今天使用“Rosetta Stone Version 3”的时候,过一会就出现这故障了, 过几分钟就重启一次,那不是要搞死人啊。!!! 我尝试了如下方法后,根据我的故障发生情况,最终找到解决办法: 1. 重启"Windwos Audio服务"-----因为我用的是Windows Server 2003系统, XP用户可略过 2. 依次禁用
MYSQL死掉后自动重启脚本
最近服务器的MYSQL老是挂掉,而且经常是在半夜里挂掉! 真想骂娘! 兴许是由于配置文件设置的不够好,已经在调优。但调优期间也要做到无人值守自动化啊,所以有了下面这个脚本~~ #!/bin/bash pgrep -x mysqld &> /dev/null if [ $? -ne 0 ] then echo "At time: `date` :MySQL err
Oracle 10.1实例启动后一分钟后自动挂掉的处理方法
接到一同事的电话说数据库启动后一分钟自动挂掉。 1、查看alert.log文件,重要信息如下: Fri Nov 30 12:10:55 2012 Errors in file c:\oracle\product\10.1.0\admin\orcl\bdump\orcl_reco_952.trc: ORA-02068: following severe error from DBL_