Description:
I'm using MySQL to store data on a Plant PC. During the last two week the server stop to work (the icon of MySQL Notifier become red) and in the Server Logs section in MySQL workbench I found the error reporte below:
-------------------------------------------------------------
2016-07-18T11:58:46, 0, ERROR, InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=238]. You may have to recover from a backup.
2016-07-18T11:59:48, 0, Note, InnoDB: page_cleaner: 1000ms intended loop took 61646ms. The settings might not be optimal. (flushed=0 and evicted=6, during the time.)
2016-07-18T11:59:48, 0, Note, InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex af831c37000000ee000000000000000000000000016c560d0006000000000000000000000000fffffffe00000000000000070000015e12ec0000015e007800000000000000023c320000015e0000017a000001c8ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff [truncated, 48.0 KB total]
InnoDB: End of page dump
2016-07-18T12:01:02, 0, Note, InnoDB: Uncompressed page, stored checksum in field1 2944605239, calculated checksums for fie
2016-07-18T12:01:02, 0, Note, InnoDB: Uncompressed page, stored checksum in field1 2944605239, calculated checksums for field1: crc32 4055747236/3704247746, innodb 757643983, none 3735928559, stored checksum in field2 359945591, calculated checksums for field2: crc32 4055747236/3704247 [truncated, 468 bytes total]
, , , InnoDB: Page may be a system page
2016-07-18T12:01:02, 0, Note, InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the co [truncated, 451 bytes total]
2016-07-18T12:01:02, 0, ERROR] [FATAL, InnoDB: Aborting because of a corrupt database page in the system tablespace. Or, there was a failure in tagging the tablespace as corrupt.
, , , 2016-07-18 14:01:02 0x7ec InnoDB: Assertion failure in thread 2028 in file ut0ut.cc line 920
, , , 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.7/en/forcing-innodb-recovery.html
, , , InnoDB: about forcing recovery.
, , , 12:01:02 UTC - mysqld got exception 0x80000003 ;
, , , This could be because you hit a bug. It is also possible that this binary
, , , or one of the libraries it was linked against is corrupt, improperly built,
, , , or misconfigured. This error can also be caused by malfunctioning hardware.
, , , Attempting to collect some information that could help diagnose the problem.
, , , As this is a crash and something is definitely wrong, the information
, , , collection process might fail.
, , , key_buffer_size=8388608
, , , read_buffer_size=65536
, , , max_used_connections=18
, , , max_threads=151
, , , thread_count=13
, , , connection_count=13
, , , It is possible that mysqld could use up to
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58346 K bytes of memory
, , , Hope that's ok; if not, decrease some variables in the equation.
, , , Thread pointer: 0x0
, , , Attempting backtrace. You can use the following information to find out
, , , where mysqld died. If you see no messages after this, something went
, , , terribly wrong...
-------------------------------------------------------------------
I'have already tried to uninstal and install again the MySQL software, but after few hours the error appear. How can i fix it?
Now I cannot restart the MySQL server 5.7, an error message appear.
Best regards
How to repeat:
I have to uninstall the MySQL software, re-instal the MySQL software and then wait tha the error appear again.
