2014-03-02 16:41:03 4168 [Note] mysql\bin\mysqld.exe: Shutdown complete
2014-03-02 17:05:22 15316 [Warning] You need to use --log-bin to make --binlog-format work.
2014-03-02 17:05:22 15316 [Note] Plugin 'FEDERATED' is disabled.
2014-03-02 17:05:22 15316 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-02 17:05:22 15316 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-02 17:05:22 15316 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-02 17:05:22 15316 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-02 17:05:22 15316 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-02 17:05:22 15316 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-02 17:05:22 15316 [Note] InnoDB: Completed initialization of buffer pool
2014-03-02 17:05:22 15316 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-02 17:05:23 15316 [Note] InnoDB: 128 rollback segment(s) are active.
2014-03-02 17:05:23 15316 [Note] InnoDB: Waiting for purge to start
2014-03-02 17:05:23 15316 [Note] InnoDB: 5.6.16 started; log sequence number 380914759
2014-03-02 17:05:23 15316 [Note] Server hostname (bind-address): '*'; port: 3306
2014-03-02 17:05:23 15316 [Note] IPv6 is available.
2014-03-02 17:05:23 15316 [Note] - '::' resolves to '::';
2014-03-02 17:05:23 15316 [Note] Server socket created on IP: '::'.
InnoDB: Error: tablespace id is 493 in the data dictionary
InnoDB: but in file .\mysql\slave_master_info.ibd it is 4!
2014-03-02 17:05:23 294c InnoDB: Assertion failure in thread 10572 in file fil0fil.cc line 796
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.
22:05:23 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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=262144
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 = 133777 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x12d78338
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...
1268300 mysqld.exe!my_thread_name()
14a1d3d mysqld.exe!my_mb_ctype_mb()
12ed380 mysqld.exe!murmur3_32()
12f0f38 mysqld.exe!murmur3_32()
13bfc93 mysqld.exe!murmur3_32()
13c04ed mysqld.exe!murmur3_32()
1320353 mysqld.exe!murmur3_32()
137b0a4 mysqld.exe!murmur3_32()
137b161 mysqld.exe!murmur3_32()
137b656 mysqld.exe!murmur3_32()
132482f mysqld.exe!murmur3_32()
132495a mysqld.exe!murmur3_32()
1328e58 mysqld.exe!murmur3_32()
128f9ee mysqld.exe!murmur3_32()
101f5e6 mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHH@Z()
110b773 mysqld.exe!?open_table_from_share@@YAHPAVTHD@@PAUTABLE_SHARE@@PBDIIIPAUTABLE@@_N@Z()
10671f4 mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_context@@@Z()
1067887 mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ()
1068946 mysqld.exe!?open_tables@@YA_NPAVTHD@@PAPAUTABLE_LIST@@PAIIPAVPrelocking_strategy@@@Z()
1068b74 mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@PAUTABLE_LIST@@_NIPAVPrelocking_strategy@@@Z()
1068d29 mysqld.exe!?open_n_lock_single_table@@YAPAUTABLE@@PAVTHD@@PAUTABLE_LIST@@W4thr_lock_type@@IPAVPrelocking_strategy@@@Z()
125f41c mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
125d1b2 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257374 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257444 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257689 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257ca2 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1253574 mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1012548 mysqld.exe!?win_main@@YAHHPAPAD@Z()
10127e7 mysqld.exe!?mysql_service@@YAHPAX@Z()
149c89a mysqld.exe!my_mb_ctype_mb()
75c6336a kernel32.dll!BaseThreadInitThunk()
77b39f72 ntdll.dll!RtlInitializeExceptionChain()
77b39f45 ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED
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.