0529 DZ经常数据库崩溃

cclylycc

QQ截图20170528090035.jpg (85.03 KB, 下载次数: 0)

2017-5-28 09:02 上传

点击文件名下载附件

Vultr 512M JP，用的Kangle，内存是够的，但是问题没找到。

要每次service restart才能解决

QQ截图20170529134428.jpg (47.32 KB, 下载次数: 0)

2017-5-29 13:43 上传

点击文件名下载附件

太占CPU了啊，问题不知道出在哪里

献上部分日志：

Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 14:06:58 mysqld_safe Number of processes running now: 0
170527 14:06:58 mysqld_safe mysqld restarted
170527 14:06:58  InnoDB: Initializing buffer pool, size = 8.0M
170527 14:06:58  InnoDB: Completed initialization of buffer pool
170527 14:06:58  InnoDB: Started; log sequence number 0 46608
170527 14:06:58 [Note] Event Scheduler: Loaded 0 events
170527 14:06:58 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 14:36:12 mysqld_safe Number of processes running now: 0
170527 14:36:12 mysqld_safe mysqld restarted
170527 14:36:12  InnoDB: Initializing buffer pool, size = 8.0M
170527 14:36:12  InnoDB: Completed initialization of buffer pool
170527 14:36:12  InnoDB: Started; log sequence number 0 46608
170527 14:36:12 [Note] Event Scheduler: Loaded 0 events
170527 14:36:12 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 16:04:00 mysqld_safe Number of processes running now: 0
170527 16:04:00 mysqld_safe mysqld restarted
170527 16:04:00  InnoDB: Initializing buffer pool, size = 8.0M
170527 16:04:00  InnoDB: Completed initialization of buffer pool
170527 16:04:00  InnoDB: Started; log sequence number 0 46608
170527 16:04:00 [Note] Event Scheduler: Loaded 0 events
170527 16:04:00 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 16:19:57 mysqld_safe Number of processes running now: 0
170527 16:19:57 mysqld_safe mysqld restarted
170527 16:19:58  InnoDB: Initializing buffer pool, size = 8.0M
170527 16:19:58  InnoDB: Completed initialization of buffer pool
170527 16:19:58  InnoDB: Started; log sequence number 0 46608
170527 16:19:58 [Note] Event Scheduler: Loaded 0 events
170527 16:19:58 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 20:18:57 mysqld_safe Number of processes running now: 0
170527 20:18:58 mysqld_safe mysqld restarted
170527 20:18:58  InnoDB: Initializing buffer pool, size = 8.0M
170527 20:18:58  InnoDB: Completed initialization of buffer pool
170527 20:18:58  InnoDB: Started; log sequence number 0 46608
170527 20:19:05 [Note] Event Scheduler: Loaded 0 events
170527 20:19:05 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 20:19:07 mysqld_safe Number of processes running now: 0
170527 20:19:07 mysqld_safe mysqld restarted
170527 20:19:08  InnoDB: Initializing buffer pool, size = 8.0M
170527 20:19:08  InnoDB: Completed initialization of buffer pool
170527 20:19:08  InnoDB: Started; log sequence number 0 46608
170527 20:19:13 [Note] Event Scheduler: Loaded 0 events
170527 20:19:13 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
170527 20:19:13 mysqld_safe Number of processes running now: 0
170527 20:19:13 mysqld_safe mysqld restarted
170527 20:19:14  InnoDB: Initializing buffer pool, size = 8.0M
170527 20:19:14  InnoDB: Completed initialization of buffer pool
170527 20:19:14  InnoDB: Started; log sequence number 0 46608
170527 20:19:19 mysqld_safe Number of processes running now: 0
170527 20:19:19 mysqld_safe mysqld restarted
170527 20:19:19  InnoDB: Initializing buffer pool, size = 8.0M
170527 20:19:19  InnoDB: Completed initialization of buffer pool
170527 20:19:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
170528 00:59:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170528  0:59:07  InnoDB: Initializing buffer pool, size = 8.0M
170528  0:59:07  InnoDB: Completed initialization of buffer pool
170528  0:59:07  InnoDB: Started; log sequence number 0 46608
170528  0:59:07 [Note] Event Scheduler: Loaded 0 events
170528  0:59:07 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

cclylycc

yulan 发表于 2017-5-29 11:12
问题应该在kangle，我之前用搬瓦工装的kangle然后做了个站，数据库天天炸。然后我就换成了amh，一直稳定到 ...

但是之前都是好好的，kangle什么的都没有变动，就是在最近出问题了

yulan

问题应该在kangle，我之前用搬瓦工装的kangle然后做了个站，数据库天天炸。然后我就换成了amh，一直稳定到现在。

tyucom

Vultr   应该是很稳定的。

不像那些 OVZ的  ramnode 和  xvmlabs天天给你杀死mysql进程。
数据库经常坏。

坏的时候你可在phpmyadmin里查看一下mysql状态，是不是在线时间一直正常。
如果在线时间被重启了，就得看看是不是环境有啥重启脚本。

cclylycc

用户名 发表于 2017-5-29 10:59
目测你换了vps可能就没事了

毕竟vu便宜.得超卖

那就只有升配置了嘛，用mysql还是得1G以上

用户名

目测你换了vps可能就没事了

毕竟vu便宜.得超卖

cclylycc

yockii 发表于 2017-5-29 06:24
会不会是兼容性问题

兼容性没问题，以前都是这样的，就是最近一直出2002

yockii

会不会是兼容性问题

cclylycc

求大神，刚刚又崩溃了一次

cclylycc

yumijie 发表于 2017-5-28 12:42
kangle问题?

不会吧，kangle我也没改什么东西，都是默认的