打印

军哥mysql老挂,php进程数已经调低,但还是不行,帮忙看看什么原因?

军哥mysql老挂,php进程数已经调低,但还是不行,帮忙看看什么原因?

军哥mysql老挂,php进程数已经调低,也把程序优化了一下,但是效果还是不理想,麻烦军哥看看什么原因?下面是mysql的日志。
180930  8:11:36 [ERROR] Got error 134 when reading table './wx_zhaog/ims_core_cache'
180930  8:11:39 [ERROR] Got error 134 when reading table './wx_zhaog/ims_core_cache'
180930  8:11:40 [ERROR] Got error 134 when reading table './wx_zhaog/ims_core_cache'
180930  8:11:42 [ERROR] Got error 134 when reading table './wx_zhaog/ims_core_cache'
180930  8:12:45 [Note] Plugin 'FEDERATED' is disabled.
180930  8:12:45 InnoDB: The InnoDB memory heap is disabled
180930  8:12:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180930  8:12:45 InnoDB: Compressed tables use zlib 1.2.7
180930  8:12:45 InnoDB: Initializing buffer pool, size = 128.0M
180930  8:12:45 InnoDB: Completed initialization of buffer pool
180930  8:12:45 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!
180930  8:12:45  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 5830760, file name ./mysql-bin.000225
180930  8:12:46  InnoDB: Waiting for the background threads to start
180930  8:12:47 InnoDB: 5.5.56 started; log sequence number 3908621716
180930  8:12:47 [Note] Recovering after a crash using mysql-bin
180930  8:12:47 [Note] Starting crash recovery...
180930  8:12:47 [Note] Crash recovery finished.
180930  8:12:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180930  8:12:47 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180930  8:12:47 [Note] Server socket created on IP: '0.0.0.0'.
180930  8:12:47 [Note] Event Scheduler: Loaded 0 events
180930  8:12:47 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.56-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
180930 10:58:54 [Note] Plugin 'FEDERATED' is disabled.
180930 10:58:54 InnoDB: The InnoDB memory heap is disabled
180930 10:58:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180930 10:58:54 InnoDB: Compressed tables use zlib 1.2.7
180930 10:58:54 InnoDB: Initializing buffer pool, size = 128.0M
180930 10:58:55 InnoDB: Completed initialization of buffer pool
180930 10:58:55 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!
180930 10:58:55  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 917272, file name ./mysql-bin.000226
180930 10:58:57  InnoDB: Waiting for the background threads to start
180930 10:58:58 InnoDB: 5.5.56 started; log sequence number 3908622076
180930 10:58:58 [Note] Recovering after a crash using mysql-bin
180930 10:58:58 [Note] Starting crash recovery...
180930 10:58:58 [Note] Crash recovery finished.
180930 10:58:58 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180930 10:58:58 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180930 10:58:58 [Note] Server socket created on IP: '0.0.0.0'.
180930 10:58:58 [Note] Event Scheduler: Loaded 0 events
180930 10:58:58 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.56-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

TOP

[ERROR] Got error 134 when reading table './wx_zhaog/ims_core_cache'
这个的话是数据库表有损坏,修复一下就行
其他就是mysql异常退出,不清楚原因,有可能是系统资源不够被kill掉了

LNMP付费问题排查/LNMP技术支持/Paypal信用卡代付/代购VPS,域名,软件等 QQ 503228080 旺旺 lzhenbao
军哥淘宝店铺
QQ/旺旺仅提供代购及付费代维/问题解决等服务,其他不回复!LNMP相关问题请在本论坛发帖,提问前先搜索,按https://bbs.vpser.net/thread-2555-1-1.html 要求反馈问题!

TOP