I am working on a wordpress website locally, and mysql is going offline on visit some of posts/pages.
I have following error in mysql log:
2013-11-22 05:50:24 6404 [Note] Plugin 'FEDERATED' is disabled.
2013-11-22 05:50:24 6404 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-22 05:50:24 6404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-22 05:50:24 6404 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-22 05:50:24 6404 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-22 05:50:24 6404 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-11-22 05:50:24 6404 [Note] InnoDB: Completed initialization of buffer pool
2013-11-22 05:50:24 6404 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-22 05:50:24 6404 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-22 05:50:24 6404 [Note] InnoDB: Waiting for purge to start
2013-11-22 05:50:24 6404 [Note] InnoDB: 5.6.12 started; log sequence number 189490334
2013-11-22 05:50:25 6404 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-22 05:50:25 6404 [Note] IPv6 is available.
2013-11-22 05:50:25 6404 [Note] - '::' resolves to '::';
2013-11-22 05:50:25 6404 [Note] Server socket created on IP: '::'.
2013-11-22 05:50:25 6404 [Note] Event Scheduler: Loaded 0 events
2013-11-22 05:50:25 6404 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-22 05:50:26 1740 InnoDB: Assertion failure in thread 5952 in file fts0que.cc line 2993
InnoDB: Failing assertion: ret == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
I have following error in mysql log:
2013-11-22 05:50:24 6404 [Note] Plugin 'FEDERATED' is disabled.
2013-11-22 05:50:24 6404 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-22 05:50:24 6404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-22 05:50:24 6404 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-22 05:50:24 6404 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-22 05:50:24 6404 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-11-22 05:50:24 6404 [Note] InnoDB: Completed initialization of buffer pool
2013-11-22 05:50:24 6404 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-22 05:50:24 6404 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-22 05:50:24 6404 [Note] InnoDB: Waiting for purge to start
2013-11-22 05:50:24 6404 [Note] InnoDB: 5.6.12 started; log sequence number 189490334
2013-11-22 05:50:25 6404 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-22 05:50:25 6404 [Note] IPv6 is available.
2013-11-22 05:50:25 6404 [Note] - '::' resolves to '::';
2013-11-22 05:50:25 6404 [Note] Server socket created on IP: '::'.
2013-11-22 05:50:25 6404 [Note] Event Scheduler: Loaded 0 events
2013-11-22 05:50:25 6404 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2013-11-22 05:50:26 1740 InnoDB: Assertion failure in thread 5952 in file fts0que.cc line 2993
InnoDB: Failing assertion: ret == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.