VPS侦探论坛

 找回密码
 注册
查看: 4156|回复: 3

MYSQL最近每天频繁挂掉,军哥方便帮看一下吗

[复制链接]
发表于 2015-10-5 23:49:42 | 显示全部楼层 |阅读模式

151004 12:44:57 mysqld_safe mysqld from pid file /usr/local/mysql/var/(none).pid ended
151004 12:45:26 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
151004 12:45:27 InnoDB: The InnoDB memory heap is disabled
151004 12:45:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151004 12:45:27 InnoDB: Compressed tables use zlib 1.2.7
151004 12:45:27 InnoDB: Initializing buffer pool, size = 16.0M
151004 12:45:27 InnoDB: Completed initialization of buffer pool
151004 12:45:27 InnoDB: highest supported file format is Barracuda.
151004 12:45:27  InnoDB: Waiting for the background threads to start
151004 12:45:28 InnoDB: 5.5.37 started; log sequence number 1595675
151004 12:45:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151004 12:45:28 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151004 12:45:28 [Note] Server socket created on IP: '0.0.0.0'.
151004 12:45:28 [Note] Event Scheduler: Loaded 0 events
151004 12:45:28 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
151004 14:36:52 [Warning] IP address '218.104.143.*' could not be resolved: Temporary failure in name resolution
151004 20:26:05 [Warning] IP address '107.151.202.*' could not be resolved: Name or service not known
151004 22:12:21 [Warning] IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:05:21 [Warning] IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:28:42 [Warning] IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:28:55 [Warning] IP address '180.97.106.*' could not be resolved: Name or service not known
151005  3:37:34 [Warning] IP address '115.28.56.*' could not be resolved: Name or service not known
151005  3:37:53 [Warning] IP address '222.186.190.*1' could not be resolved: Name or service not known
151005  7:34:46 [Warning] IP address '104.194.15.*' could not be resolved: Temporary failure in name resolution
151005 11:17:11 [Warning] IP address '5.39.222.*' could not be resolved: Name or service not known
151005 13:06:01 [Warning] IP address '210.212.98.*' could not be resolved: Name or service not known
151005 13:06:40 [Warning] IP address '80.82.64.*' could not be resolved: Name or service not known
151005 20:19:50 [Warning] IP address '61.157.96.*' could not be resolved: Name or service not known
Killed
151005 22:39:21 mysqld_safe Number of processes running now: 0
151005 22:39:21 mysqld_safe mysqld restarted
151005 22:39:21 InnoDB: The InnoDB memory heap is disabled
151005 22:39:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151005 22:39:21 InnoDB: Compressed tables use zlib 1.2.7
151005 22:39:21 InnoDB: Initializing buffer pool, size = 16.0M
151005 22:39:21 InnoDB: Completed initialization of buffer pool
151005 22:39:22 InnoDB: highest supported file format is Barracuda.
151005 22:39:22  InnoDB: Waiting for the background threads to start
151005 22:39:24 InnoDB: 5.5.37 started; log sequence number 1595675
151005 22:39:24 [Note] Recovering after a crash using mysql-bin
151005 22:39:26 [Note] Starting crash recovery...
151005 22:39:26 [Note] Crash recovery finished.
151005 22:39:26 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 22:39:26 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151005 22:39:29 [Note] Server socket created on IP: '0.0.0.0'.
Killed
151005 22:39:32 mysqld_safe Number of processes running now: 0
151005 22:39:32 mysqld_safe mysqld restarted
151005 22:39:33 InnoDB: The InnoDB memory heap is disabled
151005 22:39:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151005 22:39:33 InnoDB: Compressed tables use zlib 1.2.7
151005 22:39:33 InnoDB: Initializing buffer pool, size = 16.0M
151005 22:39:33 InnoDB: Completed initialization of buffer pool
151005 22:39:33 InnoDB: highest supported file format is Barracuda.
151005 22:39:33  InnoDB: Waiting for the background threads to start
151005 22:39:34 InnoDB: 5.5.37 started; log sequence number 1595675
151005 22:39:34 [Note] Recovering after a crash using mysql-bin
151005 22:39:34 [Note] Starting crash recovery...
151005 22:39:34 [Note] Crash recovery finished.
151005 22:39:34 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 22:39:34 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151005 22:39:34 [Note] Server socket created on IP: '0.0.0.0'.
151005 22:39:34 [Note] Event Scheduler: Loaded 0 events
151005 22:39:34 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
151005 23:01:01 [Warning] IP address '61.157.96.*' could not be resolved: Name or service not known
151005 23:16:32 [Warning] IP address '222.186.51.*' could not be resolved: Name or service not known
Killed
151005 23:19:27 mysqld_safe Number of processes running now: 0
151005 23:19:27 mysqld_safe mysqld restarted
151005 23:19:29 InnoDB: The InnoDB memory heap is disabled
151005 23:19:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151005 23:19:29 InnoDB: Compressed tables use zlib 1.2.7
151005 23:19:29 InnoDB: Initializing buffer pool, size = 16.0M
151005 23:19:29 InnoDB: Completed initialization of buffer pool
151005 23:19:30 InnoDB: highest supported file format is Barracuda.
Killed
151005 23:19:31 mysqld_safe mysqld from pid file /usr/local/mysql/var/(none).pid ended
151005 23:39:18 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
151005 23:39:19 InnoDB: The InnoDB memory heap is disabled
151005 23:39:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151005 23:39:19 InnoDB: Compressed tables use zlib 1.2.7
151005 23:39:19 InnoDB: Initializing buffer pool, size = 16.0M
151005 23:39:19 InnoDB: Completed initialization of buffer pool
151005 23:39:19 InnoDB: highest supported file format is Barracuda.
151005 23:39:19  InnoDB: Waiting for the background threads to start
151005 23:39:20 InnoDB: 5.5.37 started; log sequence number 1595675
151005 23:39:20 [Note] Recovering after a crash using mysql-bin
151005 23:39:20 [Note] Starting crash recovery...
151005 23:39:20 [Note] Crash recovery finished.
151005 23:39:20 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 23:39:20 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151005 23:39:20 [Note] Server socket created on IP: '0.0.0.0'.
151005 23:39:20 [Note] Event Scheduler: Loaded 0 events
151005 23:39:20 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
151005 23:39:46 [Warning] IP address '61.157.96.*' could not be resolved: Name or service not known
151005 23:41:21 [Warning] IP address '222.186.51.*' could not be resolved: Name or service not known

天天要重启VPS
美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
发表于 2015-10-6 09:40:53 | 显示全部楼层


看日志没有错误信息直接被kill,可能内存不够用被系统kill了,你可以看看被kill时段的内存占用情况
Linux下Nginx+MySQL+PHP自动安装工具:https://lnmp.org
 楼主| 发表于 2015-10-6 14:39:26 | 显示全部楼层

回复 2# 的帖子


好多日志,要上传哪个日志呢?
美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
发表于 2015-10-6 20:07:35 | 显示全部楼层

回复 3# 的帖子




2楼已经说了原因没让你上传其他日志
Linux下Nginx+MySQL+PHP自动安装工具:https://lnmp.org
您需要登录后才可以回帖 登录 | 注册

本版积分规则

小黑屋|手机版|Archiver|VPS侦探 ( 鲁ICP备16040043号-1 )

GMT+8, 2024-11-17 06:29 , Processed in 0.026251 second(s), 16 queries .

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

快速回复 返回顶部 返回列表