MYSQL 不停自动重新启动，寻找解决方案

feichangdaxia 2017-09-22 09:00:45
170922 09:40:01 mysqld_safe mysqld restarted
2017-09-22 09:40:01 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.29-log) starting as process 2258 ...
2017-09-22 09:40:01 2258 [Note] Plugin 'FEDERATED' is disabled.
2017-09-22 09:40:01 2258 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-22 09:40:01 2258 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-22 09:40:01 2258 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-22 09:40:01 2258 [Note] InnoDB: Memory barrier is not used
2017-09-22 09:40:01 2258 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-22 09:40:01 2258 [Note] InnoDB: Using CPU crc32 instructions
2017-09-22 09:40:01 2258 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2017-09-22 09:40:02 2258 [Note] InnoDB: Completed initialization of buffer pool
2017-09-22 09:40:02 2258 [Note] InnoDB: Highest supported file format is Barracuda.
2017-09-22 09:40:02 2258 [Note] InnoDB: The log sequence numbers 962097288 and 962097288 in ibdata files do not match the log sequence number 962097308 in the ib_logfiles!
2017-09-22 09:40:02 2258 [Note] InnoDB: Database was not shutdown normally!
2017-09-22 09:40:02 2258 [Note] InnoDB: Starting crash recovery.
2017-09-22 09:40:02 2258 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-09-22 09:40:02 2258 [Note] InnoDB: Restoring possible half-written data pages
2017-09-22 09:40:02 2258 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 1122, file name mysql-bin.001029
2017-09-22 09:40:02 2258 [Note] InnoDB: 128 rollback segment(s) are active.
2017-09-22 09:40:02 2258 [Note] InnoDB: Waiting for purge to start
2017-09-22 09:40:02 2258 [Note] InnoDB: 5.6.29 started; log sequence number 962097308
2017-09-22 09:40:02 2258 [Note] Recovering after a crash using mysql-bin
2017-09-22 09:40:02 2258 [Note] Starting crash recovery...
2017-09-22 09:40:02 2258 [Note] Crash recovery finished.
2017-09-22 09:40:02 2258 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
2017-09-22 09:40:02 2258 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2017-09-22 09:40:02 2258 [Note] Server socket created on IP: '0.0.0.0'.
2017-09-22 09:40:02 2258 [Note] Event Scheduler: Loaded 0 events
2017-09-22 09:40:02 2258 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.29-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
170922 09:57:02 mysqld_safe Number of processes running now: 0
170922 09:57:02 mysqld_safe mysqld restarted
2017-09-22 09:57:02 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.29-log) starting as process 2648 ...
2017-09-22 09:57:02 2648 [Note] Plugin 'FEDERATED' is disabled.
2017-09-22 09:57:02 2648 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-22 09:57:02 2648 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-22 09:57:02 2648 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-22 09:57:02 2648 [Note] InnoDB: Memory barrier is not used
2017-09-22 09:57:02 2648 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-22 09:57:02 2648 [Note] InnoDB: Using CPU crc32 instructions
2017-09-22 09:57:02 2648 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2017-09-22 09:57:02 2648 [Note] InnoDB: Completed initialization of buffer pool
2017-09-22 09:57:02 2648 [Note] InnoDB: Highest supported file format is Barracuda.
2017-09-22 09:57:02 2648 [Note] InnoDB: The log sequence numbers 962097288 and 962097288 in ibdata files do not match the log sequence number 962097318 in the ib_logfiles!
2017-09-22 09:57:02 2648 [Note] InnoDB: Database was not shutdown normally!
2017-09-22 09:57:02 2648 [Note] InnoDB: Starting crash recovery.
2017-09-22 09:57:02 2648 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-09-22 09:57:02 2648 [Note] InnoDB: Restoring possible half-written data pages
2017-09-22 09:57:02 2648 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 1122, file name mysql-bin.001029
2017-09-22 09:57:02 2648 [Note] InnoDB: 128 rollback segment(s) are active.
2017-09-22 09:57:02 2648 [Note] InnoDB: Waiting for purge to start
2017-09-22 09:57:02 2648 [Note] InnoDB: 5.6.29 started; log sequence number 962097318
2017-09-22 09:57:02 2648 [Note] Recovering after a crash using mysql-bin
2017-09-22 09:57:02 2648 [Note] Starting crash recovery...
2017-09-22 09:57:02 2648 [Note] Crash recovery finished.
2017-09-22 09:57:02 2648 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
2017-09-22 09:57:02 2648 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2017-09-22 09:57:02 2648 [Note] Server socket created on IP: '0.0.0.0'.
2017-09-22 09:57:02 2648 [Note] Event Scheduler: Loaded 0 events
2017-09-22 09:57:02 2648 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.29-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
170922 10:00:02 mysqld_safe Number of processes running now: 0
170922 10:00:02 mysqld_safe mysqld restarted
2017-09-22 10:00:02 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.29-log) starting as process 2790 ...
2017-09-22 10:00:02 2790 [Note] Plugin 'FEDERATED' is disabled.
2017-09-22 10:00:02 2790 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-22 10:00:02 2790 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-22 10:00:02 2790 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-22 10:00:02 2790 [Note] InnoDB: Memory barrier is not used
2017-09-22 10:00:02 2790 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-22 10:00:02 2790 [Note] InnoDB: Using CPU crc32 instructions
170922 10:00:02 mysqld_safe mysqld from pid file /data/mysql/mysql.pid ended

就是一直重新启动 然后死掉
...全文
443 3 打赏 收藏 转发到动态 举报
写回复
用AI写文章
3 条回复
切换为时间正序
请发表友善的回复…
发表回复
feichangdaxia 2017-09-23
  • 打赏
  • 举报
 回复
引用 1 楼 ACMAIN_CHM 的回复:
检查杀毒软件。
看了进程 后台也没有杀毒软件 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ntpd 562 ntp 16u IPv4 9843 0t0 UDP *:ntp ntpd 562 ntp 17u IPv6 14363 0t0 UDP *:ntp ntpd 562 ntp 18u IPv4 14370 0t0 UDP iZ94of0966tZ:ntp ntpd 562 ntp 20u IPv4 14515 0t0 UDP iZ94of0966tZ:ntp ntpd 562 ntp 21u IPv4 10209 0t0 UDP TEST:ntp sshd 965 root 3u IPv4 13851 0t0 TCP *:ssh (LISTEN) sshd 1868 root 3u IPv4 13997 0t0 TCP TEST:ssh->180.154.157.136:59509 (ESTABLISHED) java 2011 root 41u IPv4 14190 0t0 TCP *:http (LISTEN) java 2011 root 42u IPv4 14909 0t0 TCP *:https (LISTEN) java 2011 root 43u IPv4 14193 0t0 TCP *:8009 (LISTEN) java 2011 root 48u IPv4 23460 0t0 TCP TEST:18407->TEST:mysql (ESTABLISHED) java 2011 root 49u IPv4 24262 0t0 TCP TEST:18408->TEST:mysql (ESTABLISHED) java 2011 root 62u IPv4 14930 0t0 TCP iZ94of0966tZ:mxi (LISTEN) AliYunDun 2085 root 19u IPv4 14956 0t0 TCP TEST:27520->140.205.140.205:http (ESTABLISHED) aegis_qua 2134 root 5u IPv4 17449 0t0 TCP iZ94of0966tZ:15770 (LISTEN) aegis_qua 2134 root 19u IPv4 14956 0t0 TCP TEST:27520->140.205.140.205:http (ESTABLISHED) atd 2305 root 3u IPv4 17178 0t0 TCP TEST:mobile-file-dl->ns3082757.ip-91-121-2.eu:http (ESTABLISHED) mysqld 3012 mysql 16u IPv4 24198 0t0 TCP *:mysql (LISTEN) mysqld 3012 mysql 38u IPv4 23459 0t0 TCP TEST:mysql->180.154.157.136:60965 (ESTABLISHED) mysqld 3012 mysql 39u IPv4 24220 0t0 TCP TEST:mysql->TEST:18407 (ESTABLISHED) mysqld 3012 mysql 40u IPv4 23461 0t0 TCP TEST:mysql->TEST:18408 (ESTABLISHED)
feichangdaxia 2017-09-23
  • 打赏
  • 举报
 回复
LINUX怎么检查杀毒软件？ 我们是买阿里云的 我不太懂
ACMAIN_CHM 2017-09-23
  • 打赏
  • 举报
 回复
检查杀毒软件。
MySQL高可用架构之MHA原理及其部署,三种切换方式以及vip的漂移
            MySQL高可用架构之MHA 一.简介： MHA（Master High Availability）目前在MySQL高可用方面是一个相对成熟的解决方案，它由日本DeNA公司youshimaton（现就职于 Facebook公司）开发，是一套优秀的作为MySQL高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA能做到在 0~30秒之内自动完成...
微服务架构下分布式事务解决方案
前言在微服务架构中，随着服务的逐步拆分，数据库私有已经成为共识，这也导致所面临的分布式事务问题成为微服务落地过程中一个非常难以逾越的障碍，但是目前尚没有一个完整通用的解决方案。其实不仅仅是...
五大分布式集群架构问题解决方案
文章内容输出来源：拉勾教育Java高薪训练营。 前言 1 ⼀致性Hash算法 2 集群时钟同步问题 3 分布式ID解决⽅案 4 分布式调度问题 5 Session共享问题 Session共享及Session保持或者叫做Session⼀致性。
mysql如何获取慢SQL，以及慢查询的解决方式
浅谈MySQL中优化sql语句查询常用的30种方法 1.对查询进行优化，应尽量避免全表扫描，首先应考虑在 where 及 order by 涉及的列上建立索引。 2.应尽量避免在 where 子句中使用!=或<>操作符，否则将引擎放弃使用索引而进行全表扫描。 3.应尽量避免在 where 子句中对字段进行 null 值判断，否则将导致引擎放弃使用索引而进行全表扫描，如： select id from t where num is null 可以在num上设置默认值0，确保表中num列...
MySQL基础知识总结
1. 什么是MySQL? MySQL 是⼀种关系型数据库，在Java企业级开发中⾮常常⽤，因为 MySQL 是开源免费的，并且⽅便扩展。阿⾥巴巴数据库系统也⼤量⽤到了 MySQL，因此它的稳定性是有保障的。MySQL是开放源代码的，因此任何⼈都可以在 GPL(General Public License) 的许可下下载并根据个性化的需要对其进⾏修改。MySQL的默认端⼝号是3306 ...
MySQL

56,679

社区成员

56,709

社区内容

发帖
与我相关
我的任务
社区描述
MySQL相关内容讨论专区
社区管理员
  • MySQL
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章