18:48 提问
mysql经常挂掉，重启主机就好了
:50:25 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
:50:26 [Note] Plugin 'FEDERATED' is disabled.
:50:26 InnoDB: The InnoDB memory heap is disabled
:50:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
:50:26 InnoDB: Compressed tables use zlib 1.2.3
:50:26 InnoDB: Using Linux native AIO
:50:26 InnoDB: Initializing buffer pool, size = 128.0M
:50:26 InnoDB: Completed initialization of buffer pool
: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!
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...
InnoDB: Waiting for the background threads to start
:50:28 InnoDB: 5.5.37 log sequence number 1595675
:50:28 [Note] Recovering after a crash using mysql-bin
:50:28 [Note] Starting crash recovery...
:50:28 [Note] Crash recovery finished.
:50:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
:50:28 [Note]
- '0.0.0.0' resolves to '0.0.0.0';
:50:28 [Note] Server socket created on IP: '0.0.0.0'.
:50:28 [Note] Event Scheduler: Loaded 0 events
: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)
:53:25 [Note] /alidata/server/mysql/bin/mysqld: Normal shutdown
:53:25 [Note] Event Scheduler: Purging the queue. 0 events
InnoDB: Starting shutdown...
InnoDB: S log sequence number 1595675
:53:26 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete
:53:26 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
:57:45 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
:57:46 [Note] Plugin 'FEDERATED' is disabled.
:57:46 InnoDB: The InnoDB memory heap is disabled
:57:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
:57:46 InnoDB: Compressed tables use zlib 1.2.3
:57:46 InnoDB: Using Linux native AIO
:57:46 InnoDB: Initializing buffer pool, size = 128.0M
:57:46 InnoDB: Completed initialization of buffer pool
:57:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Waiting for the background threads to start
:57:47 InnoDB: 5.5.37 log sequence number 1595675
:57:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
:57:47 [Note]
- '0.0.0.0' resolves to '0.0.0.0';
:57:47 [Note] Server socket created on IP: '0.0.0.0'.
:57:47 [Note] Event Scheduler: Loaded 0 events
: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)
:56:24 [Warning] IP address '42.156.250.117' could not be resolved: Name or service not known
:09:33 [Warning] IP address '107.150.52.84' could not be resolved: Name or service not known
:23:23 [Warning] IP address '114.113.55.141' could not be resolved: Name or service not known
:43:01 [Warning] IP address '61.156.44.98' could not be resolved: Name or service not known
:56:28 [Warning] IP address '42.120.142.220' could not be resolved: Name or service not known
:07:01 mysqld_safe Number of processes running now: 0
:07:01 mysqld_safe mysqld restarted
:07:01 [Note] Plugin 'FEDERATED' is disabled.
:07:01 InnoDB: The InnoDB memory heap is disabled
:07:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
:07:01 InnoDB: Compressed tables use zlib 1.2.3
:07:01 InnoDB: Using Linux native AIO
:07:01 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap( bytes) errno 12
:07:01 InnoDB: Completed initialization of buffer pool
:07:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
:07:01 [ERROR] Plugin 'InnoDB' init function returned error.
:07:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
:07:01 [ERROR] Unknown/unsupported storage engine: InnoDB
:07:01 [ERROR] Aborting
:07:01 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete
:07:01 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
:09:15 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
:09:15 [Note] Plugin 'FEDERATED' is disabled.
:09:15 InnoDB: The InnoDB memory heap is disabled
:09:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
:09:15 InnoDB: Compressed tables use zlib 1.2.3
:09:15 InnoDB: Using Linux native AIO
:09:15 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap( bytes) errno 12
:09:15 InnoDB: Completed initialization of buffer pool
:09:15 InnoDB: Fatal error: cannot allocate memory for the buffer pool
:09:15 [ERROR] Plugin 'InnoDB' init function returned error.
:09:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
:09:15 [ERROR] Unknown/unsupported storage engine: InnoDB
:09:15 [ERROR] Aborting
:09:15 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete
:09:15 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
按赞数排序
关闭机器的杀毒软件和防火墙然后再试。
其他相似问题当前位置： →
日期： 09:01:38&&来源：本站整理
Shutdown命令关机失效
Q：我的Windows 7系统以前可以使用诸如：at 23:00 shutdown -s的命令来倒计时关机，现在使用该命令却不行了。请问这是什么原因？
A：该命令的正常运行需要系统中的“task scheduler”服务来支持，如果该服务被关闭了，就有可能会出现该命令不起作用的情况。解决方法：按“Win+R”，输入“Services.msc”并回车打开服务管理器，找到上面的服务并确保其处于运行状态。此外，在输入上面的命令时请使用英文输入法，如果在中文输入法状态下输入就可能会出现不执行的情况。
?上一篇文章：
?下一篇文章：
电脑维修学习广告联系QQ
Copyright & . All Rights Reserved
页面执行时间：3,265.62500 毫秒用户名：reminis
访问量：7882
注册日期：
阅读量：1297
阅读量：3317
阅读量：442834
阅读量：1128935
51CTO推荐博文
& & 在linux环境下，tomcat 执行shutdown.sh之后，进程仍然存在，这是个让人头疼的问题，个人认为最根本的原因是有一些非deamon thread 存在，这种情况下，tomcat关闭后，整个进程并不会结束。如何判这种情况呢？& & 大家可以按照以下步骤去判断：& & 1、找到tomcat当前运行的pid（使用ps -ef |grep tomcat），& & 2、找到jdk的目录，可以使用which java 命令，并切换到bin目录&&&&3、在bin目录下执行jstack pid，查看每个thread，找出非deamon thread，进而判断这些thread为何没有停止例：之前我遇到过的一个场景是在使用Quatz的定时任务，由于没有设置定时任务为deamon的，造成tomcat的进程没有停止。后来配置了Quatz的thread为deamon thread就把这个问题解决了。下面是相关配置，&&&&&&&&&property name="quartzProperties"&
& & &props&
&prop key="org.quartz.scheduler.makeSchedulerThreadDaemon"&true&/prop&
&prop key="org.quartz.threadPool.makeThreadsDaemons"&true&/prop&
& & &/props&
& &&/property&以上配置放在了class="org.springframework.scheduling.quartz.SchedulerFactoryBean" 的bean配置项中。本文出自 “” 博客，请务必保留此出处
了这篇文章
类别：┆阅读(0)┆评论(0)