Description:
I have installed and configured a MySQL slave server, version 5.6.13 on Windows Server 2012 Standard x64. I have make a dump of master server (version 5.1.51 on SuSE Linux Enterprise Server SP1 x64) and then restored on this slave server.
When I start the replication, MySQL crashes with this error message (server.err):
[Note] Plugin 'FEDERATED' is disabled.
[Warning] option 'innodb-autoextend-increment': unsigned value 10485760 adjusted to 1000
InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
[Note] InnoDB: The InnoDB memory heap is disabled
[Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
[Note] InnoDB: Compressed tables use zlib 1.2.3
[Note] InnoDB: Not using CPU crc32 instructions
[Note] InnoDB: Initializing buffer pool, size = 256.0M
[Note] InnoDB: Completed initialization of buffer pool
[Note] InnoDB: Highest supported file format is Barracuda.
[Note] InnoDB: 128 rollback segment(s) are active.
[Note] InnoDB: Waiting for purge to start
[Note] InnoDB: 5.6.13 started; log sequence number 1604057824
[Note] Server hostname (bind-address): '*'; port: 60010
[Note] IPv6 is available.
[Note] - '::' resolves to '::';
[Note] Server socket created on IP: '::'.
[Warning] Slave I/O: Unknown system variable 'SERVER_UUID' on master. A probable cause is that the variable is not supported on the master (version: 5.1.51-log), even though it is on the slave (version: 5.6.13-log), Error_code: 1193
[Note] Event Scheduler: Loaded 0 events
[Note] mysqld.exe: ready for connections.
Version: '5.6.13-log' socket: '' port: 60010 MySQL Community Server (GPL)
[Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
[Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0
[Note] Slave SQL thread initialized, starting replication in log 'mysql_test-bin.000075' at position 752092254, relay log '.\test-relay-bin.000003' position: 43419
[Note] 'SQL_SLAVE_SKIP_COUNTER=5' executed at relay_log_file='.\test-relay-bin.000003', relay_log_pos='43419', master_log_name='mysql_test-bin.000075', master_log_pos='752092254' and new position at relay_log_file='.\test-relay-bin.000003', relay_log_pos='46142', master_log_name='mysql_test-bin.000075', master_log_pos='752094977'
07:00:04 UTC - mysqld got exception 0xc0000005 ;
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=8388608
read_buffer_size=65536
max_used_connections=3
max_threads=100
thread_count=5
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 41442 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2e13d7c0
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...
[Note] Slave I/O thread: connected to master 'user@server:60010',replication started in log 'mysql_test-bin.000076' at position 5152410
[Warning] Slave I/O: Notifying master by SET @master_binlog_checksum= @@global.binlog_checksum failed with error: Unknown system variable 'binlog_checksum', Error_code: 1193
[Warning] Slave I/O: Unknown system variable 'SERVER_UUID' on master. A probable cause is that the variable is not supported on the master (version: 5.1.51-log), even though it is on the slave (version: 5.6.13-log), Error_code: 1193
7f76c09b593 mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c08412c mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c081454 mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c0ad65f mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c0b19d8 mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c0b25b4 mysqld.exe!?opt_sum_query@@YAHPEAVTHD@@PEAUTABLE_LIST@@AEAV?$List@VItem@@@@PEAVItem@@@Z()
7f76c2c13a6 mysqld.exe!xor_string()
7f76c0d3a4e mysqld.exe!win_pthread_mutex_trylock()
7f76c35ab8b mysqld.exe!my_mb_ctype_mb()
7f76c35ac1f mysqld.exe!my_mb_ctype_mb()
7f833e51832 KERNEL32.DLL!BaseThreadInitThunk()
7f83463d609 ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 41
Status: NOT_KILLED
How to repeat:
Configure replication and run 'START SLAVE;'
