Re: MySQL 5.6.21 signal 11 crashing instantaneously after START SLAVE

[Wagner Bianchi]

Carry on analyzing this problem, I've started just the IO_THREAD and it seems not be the problem.

2014-10-08 14:03:41 38397 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.21' socket: '/var/mysql/logs/mysql.sock' port: 3306 MySQL Community Server (GPL)
2014-10-08 14:03:41 38397 [Warning] Access denied for user 'UNKNOWN_MYSQL_USER'@'localhost' (using password: NO)
2014-10-08 15:12:25 38397 [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.
2014-10-08 15:12:25 38397 [Note] Slave I/O thread: connected to master 'repl56@192.168.168.202:3306',replication started in log 'ndb5-bin.006822' at position 34727464
2014-10-08 15:12:25 38397 [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
2014-10-08 15:12:25 38397 [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.5.37-35.1-log), even though it is on the slave (version: 5.6.21), Error_code: 1193

But, starting the SQL_THREAD, it worked for some minutes and then, crashed

18:15:41 UTC - mysqld got signal 11 ;
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=131072
max_used_connections=1
max_threads=151
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68245 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7efbbc000990
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...
stack_bottom = 7efbdc3da7e0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8dbbb5]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x665f24]
/lib64/libpthread.so.0(+0xf710)[0x7f077beca710]
/usr/sbin/mysqld(_ZN10Copy_field13get_copy_funcEP5FieldS1_+0x3a)[0x7cb35a]
/usr/sbin/mysqld(_ZN10Copy_field3setEP5FieldS1_b+0x11e)[0x7cb9fe]
/usr/sbin/mysqld(_Z10unpack_rowPK14Relay_log_infoP5TABLEjPKhPK9st_bitmapPS5_PmS5_+0x26c)[0x8989ac]
/usr/sbin/mysqld(_ZN14Rows_log_event24do_index_scan_and_updateEPK14Relay_log_info+0x100)[0x873c50]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0x852)[0x877c32]
/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x74)[0x87fb54]
/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x263)[0x8aefd3]
/usr/sbin/mysqld[0x8b0cf2]
/usr/sbin/mysqld(handle_slave_sql+0xb09)[0x8b27c9]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xb00b1a]
/lib64/libpthread.so.0(+0x79d1)[0x7f077bec29d1]
/lib64/libc.so.6(clone+0x6d)[0x7f077ac2b86d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 4
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.
141008 15:15:41 mysqld_safe Number of processes running now: 0
141008 15:15:41 mysqld_safe mysqld restarted

...

Wagner Bianchi - [phone]
Profile: bit.ly/toG94v
Blog: wagnerbianchi.com/blog
Twitter: @wagnerbianchijr
Skype: wbianchijr