2017-08-17T01:50:44.770345Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2017-08-17T01:50:44.770345Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.17-log) starting as process 6024 ...
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Uses event mutexes
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Number of pools: 1
2017-08-17T01:50:44.770345Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-08-17T01:50:44.785950Z 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2017-08-17T01:50:44.785950Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 16369721
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16369749
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16369749
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Database was not shutdown normally!
2017-08-17T01:50:44.801575Z 0 [Note] InnoDB: Starting crash recovery.
2017-08-17 09:50:44 0x66c InnoDB: Assertion failure in thread 1644 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
01:50:44 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=16384
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 51099 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...
7ff7f052fde2 mysqld.exe!my_errno()
7ff7f08d9fc9 mysqld.exe!my_wildcmp_mb()
7ff7f08d8ec0 mysqld.exe!my_wildcmp_mb()
7ff7f0640f78 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f0794cf4 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f0797a96 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f07971de mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f079f521 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f079ec73 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f069b1a0 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f06157fc mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7f0569bdc mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff7efdf07fe mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
7ff7eff03d68 mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
7ff7eff0391b mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
7ff7efdc1015 mysqld.exe!?init_connection_acceptor@?$Connection_acceptor@VShared_mem_listener@@@@QEAA_NXZ()
7ff7efdc5e8e mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
7ff7efdc3847 mysqld.exe!?mysql_service@@YAHPEAX@Z()
7ff7f08cbf93 mysqld.exe!my_wildcmp_mb()
7ff7f08cc04c mysqld.exe!my_wildcmp_mb()
7ffe1b0013d2 KERNEL32.DLL!BaseThreadInitThunk()
7ffe1d6454e4 ntdll.dll!RtlUserThreadStart()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
uj5u.com熱心網友回復：
mysql的程式出問題了。新裝的mysql啟不起來，還是正常的mysql服務器突然壞了？轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/109765.html