VPS侦探论坛 › LNMP一键安装包 › MYSQL最近每天频繁挂掉，军哥方便帮看一下吗

疯狂痴呆 发表于 2015-10-5 23:49:42

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

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:27InnoDB: Waiting for the background threads to start
151004 12:45:28 InnoDB: 5.5.37 started; log sequence number 1595675
151004 12:45:28 Server hostname (bind-address): '0.0.0.0'; port: 3306
151004 12:45:28    - '0.0.0.0' resolves to '0.0.0.0';
151004 12:45:28 Server socket created on IP: '0.0.0.0'.
151004 12:45:28 Event Scheduler: Loaded 0 events
151004 12:45:28 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
151004 14:36:52 IP address '218.104.143.*' could not be resolved: Temporary failure in name resolution
151004 20:26:05 IP address '107.151.202.*' could not be resolved: Name or service not known
151004 22:12:21 IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:05:21 IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:28:42 IP address '180.97.106.*' could not be resolved: Name or service not known
151004 23:28:55 IP address '180.97.106.*' could not be resolved: Name or service not known
1510053:37:34 IP address '115.28.56.*' could not be resolved: Name or service not known
1510053:37:53 IP address '222.186.190.*1' could not be resolved: Name or service not known
1510057:34:46 IP address '104.194.15.*' could not be resolved: Temporary failure in name resolution
151005 11:17:11 IP address '5.39.222.*' could not be resolved: Name or service not known
151005 13:06:01 IP address '210.212.98.*' could not be resolved: Name or service not known
151005 13:06:40 IP address '80.82.64.*' could not be resolved: Name or service not known
151005 20:19:50 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:22InnoDB: Waiting for the background threads to start
151005 22:39:24 InnoDB: 5.5.37 started; log sequence number 1595675
151005 22:39:24 Recovering after a crash using mysql-bin
151005 22:39:26 Starting crash recovery...
151005 22:39:26 Crash recovery finished.
151005 22:39:26 Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 22:39:26    - '0.0.0.0' resolves to '0.0.0.0';
151005 22:39:29 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:33InnoDB: Waiting for the background threads to start
151005 22:39:34 InnoDB: 5.5.37 started; log sequence number 1595675
151005 22:39:34 Recovering after a crash using mysql-bin
151005 22:39:34 Starting crash recovery...
151005 22:39:34 Crash recovery finished.
151005 22:39:34 Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 22:39:34    - '0.0.0.0' resolves to '0.0.0.0';
151005 22:39:34 Server socket created on IP: '0.0.0.0'.
151005 22:39:34 Event Scheduler: Loaded 0 events
151005 22:39:34 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
151005 23:01:01 IP address '61.157.96.*' could not be resolved: Name or service not known
151005 23:16:32 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:19InnoDB: Waiting for the background threads to start
151005 23:39:20 InnoDB: 5.5.37 started; log sequence number 1595675
151005 23:39:20 Recovering after a crash using mysql-bin
151005 23:39:20 Starting crash recovery...
151005 23:39:20 Crash recovery finished.
151005 23:39:20 Server hostname (bind-address): '0.0.0.0'; port: 3306
151005 23:39:20    - '0.0.0.0' resolves to '0.0.0.0';
151005 23:39:20 Server socket created on IP: '0.0.0.0'.
151005 23:39:20 Event Scheduler: Loaded 0 events
151005 23:39:20 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
151005 23:39:46 IP address '61.157.96.*' could not be resolved: Name or service not known
151005 23:41:21 IP address '222.186.51.*' could not be resolved: Name or service not known

天天要重启VPS

licess 发表于 2015-10-6 09:40:53

看日志没有错误信息直接被kill，可能内存不够用被系统kill了，你可以看看被kill时段的内存占用情况

疯狂痴呆 发表于 2015-10-6 14:39:26

回复 2# 的帖子

好多日志，要上传哪个日志呢？

licess 发表于 2015-10-6 20:07:35

回复 3# 的帖子

2楼已经说了原因没让你上传其他日志

查看完整版本: MYSQL最近每天频繁挂掉，军哥方便帮看一下吗