Description:
While trying to reproduce bug #26489 I got this crash with debug binary of 5.0.48-enterprise:
071003 16:28:27 [Note] Error reading relay log event: slave SQL thread was killed
071003 16:28:27 [Note] Slave SQL thread initialized, starting replication in log 'anon-bin.000001' at position 977771354, relay log '/home/sbester/server/5.0/mysql-enterprise-gpl-5.0.48-linux-i686-glibc23/data/www-relay-bin.000380' position: 140
071003 16:28:27 [ERROR] Slave I/O thread: error connecting to master 'root@192.168.250.6:3306': Error: '' errno: 1159 retry-time: 60 retries: 86400
071003 16:28:27 [Note] Slave I/O thread killed while connecting to master
071003 16:28:27 [Note] Slave I/O thread exiting, read up to log 'anon-bin.000001', position 977771354
071003 16:28:27 [Note] Error reading relay log event: slave SQL thread was killed
071003 16:28:28 [Note] Slave SQL thread initialized, starting replication in log 'anon-bin.000001' at position 977771354, relay log '/home/sbester/server/5.0/mysql-enterprise-gpl-5.0.48-linux-i686-glibc23/data/www-relay-bin.000380' position: 140
071003 16:28:28 [Note] Slave I/O thread: connected to master 'root@192.168.250.6:3306', replication started in log 'anon-bin.000001' at position 977771354
071003 16:28:28 [Note] Slave I/O thread killed while reading event
071003 16:28:28 [Note] Slave I/O thread exiting, read up to log 'anon-bin.000001', position 977771354
071003 16:28:28 [Note] Error reading relay log event: slave SQL thread was killed
071003 16:28:28 [Note] Slave SQL thread initialized, starting replication in log 'anon-bin.000001' at position 977771354, relay log '/home/sbester/server/5.0/mysql-enterprise-gpl-5.0.48-linux-i686-glibc23/data/www-relay-bin.000380' position: 140
071003 16:28:28 [Note] Slave I/O thread: connected to master 'root@192.168.250.6:3306', replication started in log 'anon-bin.000001' at position 977771354
071003 16:28:29 [Note] Slave I/O thread killed while reading event
071003 16:28:29 [Note] Slave I/O thread exiting, read up to log 'anon-bin.000001', position 977771354
071003 16:28:29 [Note] Error reading relay log event: slave SQL thread was killed
safe_mutex: Trying to lock mutex at slave.cc, line 685, when the mutex was already locked at slave.cc, line 770 in thread T@11166176
071003 16:28:43 - mysqld got signal 6;
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=8388600
read_buffer_size=131072
max_used_connections=9
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8b68790
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...
Cannot determine thread, fp=0x428e21fc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81901c5 handle_segfault + 427
0xffffe410 _end + -140834688
0x400e5b75 _end + 933855205
0x83e4683 safe_mutex_lock + 243
0x8287256 terminate_slave_thread(THD*, st_safe_mutex_t*, st_safe_mutex_t*, pthread_cond_t*, unsigned int volatile*) + 78
0x8287107 terminate_slave_threads(st_master_info*, int, bool) + 229
0x82878d2 start_slave_threads(bool, bool, st_master_info*, char const*, char const*, int) + 298
0x8293884 start_slave(THD*, st_master_info*, bool) + 698
0x81a7643 mysql_execute_command(THD*) + 5245
0x81acfe2 mysql_parse(THD*, char const*, unsigned int, char const**) + 334
0x81a5075 dispatch_command(enum_server_command, THD*, char*, unsigned int) + 1663
0x81a49ea do_command(THD*) + 442
0x81a3ca4 handle_one_connection + 812
0x40045aa7 _end + 933199639
0x40176c2e _end + 934449310
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8b82b60 = start slave
thd->thread_id=34648
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
071003 16:28:43 mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
071003 16:28:44 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 1373826, file name anon-bin.000001
071003 16:28:44 InnoDB: Started; log sequence number 0 1014729845
How to repeat:
start replication
replicate things from the master
run start slave and stop slave continuously
kill processlist entries on the slave continuously
Suggested fix:
correct locking semantics
