无标题文档
WDCDN联

盟内部测试火热进行中
wdCP系统 (介绍,功能特性,运行环境,安装说明,演示,常见问题,使用教程) wdCDN系统 (介绍,功能特性,运行环境,安装说明,演示,常见问题,使用手册)
wdOS系统 (介绍,功能特性,运行环境,安装说明,演示,常见问题,使用教程) wdDNS系统 (介绍,功能特性,运行环境,安装说明,演示,常见问题,使用手册)
注册 发贴 提问 回复-必看必看 wddns免费智能 DNS 开通 本地或虚拟机使 用wdcp 一键包在mysql编 译时"卡住"
【300G高防】双线 无视攻击 wdcp官方技术支持/服务 阿里云8折优惠券 无敌云 腾讯云优惠中,现注册更有260代金额券赠送
返回列表 发帖
提问三步曲: 提问先看教程/FAQ索引(wdcp,wdcp_v3,一键包)及搜索,会让你更快解决问题
1 提供详细,如系统版本,wdcp版本,软件版本等及错误的详细信息,贴上论坛或截图发论坛
2 做过哪些操作或改动设置等

温馨提示:信息不详,很可能会没人理你!论坛有教程说明的,也可能没人理!因为,你懂的

[求助] WDCP运行一段时间后数据库会挂掉到不到原因

每天都会出现数据库挂掉,重启又OK了,找不到原因,附上以下日志,望各老大能帮忙看看!谢谢了!

  • 操作系统CentOS 6.8 64位
  • CPU1核
  • 内存1GB
  • 系统盘20GB(本地磁盘)
  • 公网带宽1Mbps

当前版本: wdCP v3.2.4
操作系统:2.6.32-642.6.2.el6.x86_64


170518  0:39:03 [Warning] IP address '211.180.107.240' could not be resolved: Name or service not known
170518  0:57:20 [Warning] IP address '123.57.4.56' could not be resolved: Name or service not known
170518  1:13:39 [Warning] IP address '121.41.113.41' could not be resolved: Name or service not known
170518  1:44:35 [Warning] IP address '180.153.100.123' could not be resolved: Name or service not known
170518  2:26:36 [Warning] IP address '118.129.170.41' could not be resolved: Name or service not known
170518  2:33:49 [Warning] IP address '47.90.92.26' could not be resolved: Name or service not known
170518  3:56:22 [Warning] IP address '119.145.255.181' could not be resolved: Name or service not known
170518  5:08:29 [Warning] IP address '222.186.22.243' could not be resolved: Name or service not known
170518  5:15:12 [Warning] IP address '118.184.33.101' could not be resolved: Name or service not known
170518  6:15:35 [Warning] IP address '123.249.27.95' could not be resolved: Temporary failure in name resolution
170518  6:57:04 [Note] Plugin 'FEDERATED' is disabled.
170518  6:57:04 InnoDB: The InnoDB memory heap is disabled
170518  6:57:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170518  6:57:04 InnoDB: Compressed tables use zlib 1.2.3
170518  6:57:04 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
170518  6:57:04 InnoDB: Completed initialization of buffer pool
170518  6:57:04 InnoDB: Fatal error: cannot allocate memory for the buffer pool
170518  6:57:04 [ERROR] Plugin 'InnoDB' init function returned error.
170518  6:57:04 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170518  6:57:04 [ERROR] Unknown/unsupported storage engine: InnoDB
170518  6:57:04 [ERROR] Aborting

170518  6:57:04 [Note] /www/wdlinux/mysql-5.5.54/bin/mysqld: Shutdown complete

170519 15:18:27 [Note] Plugin 'FEDERATED' is disabled.
170519 15:18:27 InnoDB: The InnoDB memory heap is disabled
170519 15:18:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170519 15:18:27 InnoDB: Compressed tables use zlib 1.2.3
170519 15:18:27 InnoDB: Initializing buffer pool, size = 128.0M
170519 15:18:27 InnoDB: Completed initialization of buffer pool
170519 15:18:27 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!
170519 15:18:27  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: Last MySQL binlog file position 0 507869, file name ./mysql-bin.000006
170519 15:18:28  InnoDB: Waiting for the background threads to start
170519 15:18:29 InnoDB: 5.5.54 started; log sequence number 60923990
170519 15:18:29 [Note] Recovering after a crash using mysql-bin
170519 15:18:29 [Note] Starting crash recovery...
170519 15:18:29 [Note] Crash recovery finished.
170519 15:18:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170519 15:18:29 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170519 15:18:29 [Note] Server socket created on IP: '0.0.0.0'.
170519 15:18:29 [Note] Event Scheduler: Loaded 0 events
170519 15:18:29 [Note] /www/wdlinux/mysql-5.5.54/bin/mysqld: ready for connections.
Version: '5.5.54-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170519 18:33:35 [Warning] IP address '59.110.6.177' could not be resolved: Name or service not known
玩玩SEO

wdcp是不会和系统冲突的,就算会,也不可能会影响到mysql这些WEB应用环境

系统版本,mysql版本,以及相关设置或配置,则是有可能冲突的
看清提问三步曲及多看教程/FAQ索引(wdcp,v3,一键包,wdOS),益处多多.wdcp工具集 阿里云主机8折优惠码

TOP

解决了,应该是WDCP和系统冲突导致的,换了另一家的LANP,运行了一个星期都没挂过
玩玩SEO

TOP

回复 6# qiuss


   每天才2个独立 IP,基本上都是自己在访问。流量很小的
玩玩SEO

TOP

如果流量大的话 1G内存是不是有点小?
qiusongsong.net/dh/

TOP

回复 4# nong2106


   这个试过了,还是一样过一段时间会卡死掉。
玩玩SEO

TOP

删除mysql  data下的 ib_logfile0、ib_logfile1这2个文件,然后启动MYSQL就好了。
我呀

TOP

回复 2# admin


  我的网站都没有其它人访问的。就只有我一个人打开……有没有办法帮忙处理一下:handshake
玩玩SEO

TOP

看像是有内存溢出
看清提问三步曲及多看教程/FAQ索引(wdcp,v3,一键包,wdOS),益处多多.wdcp工具集 阿里云主机8折优惠码

TOP

返回列表