Bug #50776 rpl_ndb_row_001 crashes on PB
Submitted: 1 Feb 2010 5:50
Reporter: Libing Song Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.2 OS:Mac OS X
Assigned to: CPU Architecture:Any
Tags: mysql-5.6.0-beta-osx10.5-i386
Triage: Triaged: D3 (Medium) / R6 (Needs Assessment) / E6 (Needs Assessment)

[1 Feb 2010 5:50] Libing Song
Description:
rpl_ndb_row_001 crashes on PB.
----------------------------
CURRENT_TEST: rpl_ndb.rpl_ndb_row_001
mysqltest: In included file "./include/ndb_not_readonly.inc": At line 25: query 'replace into mysql.ndb_apply_status values(0,0,"",0,0)' failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 0...
Failed to read from '/Volumes/hd3/pb2/test/sb_1-1266039-1264847303.56/mysql-5.6.0-beta-osx10.5-i386-test/mysql-test/var-n_mix/log/rpl_ndb_row_001.log', errno: 22

Server [mysqld.1.1 - pid: 89289, winpid: 89289, exit: 256] failed during test run
Server log from this test:
100130 14:23:02 [Warning] Setting lower_case_table_names=2 because file system for /Volumes/hd3/pb2/test/sb_1-1266039-1264847303.56/mysql-5.6.0-beta-osx10.5-i386-test/mysql-test/var-n_mix/mysql_cluster.1/mysqld.1/data/ is case insensitive
100130 14:23:03 [Note] Plugin 'FEDERATED' is disabled.
100130 14:23:03 [Note] Plugin 'InnoDB' is disabled.
100130 14:23:13 [Note] Starting MySQL Cluster Binlog Thread
100130 14:23:13 [Warning] /Volumes/hd3/pb2/test/sb_1-1266039-1264847303.56/mysql-5.6.0-beta-osx10.5-i386-test/libexec/mysqld: unknown variable 'loose-debug-sync-timeout=300'
100130 14:23:13 [Note] Event Scheduler: Loaded 0 events
100130 14:23:13 [Note] /Volumes/hd3/pb2/test/sb_1-1266039-1264847303.56/mysql-5.6.0-beta-osx10.5-i386-test/libexec/mysqld: ready for connections.
Version: '5.6.0-beta-log'  socket: '/Volumes/hd3/pb2/test/sb_1-1266039-1264847303.56/tmp/LrtpSaQH28/mysqld.1.1.sock'  port: 13002  Source distribution
100130 14:23:15 - mysqld got signal 10 ;
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=1048576
read_buffer_size=131072
max_used_connections=2
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60041 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x1038200
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 = 0xb0094f5c thread_stack 0x30000
0   mysqld                              0x0047a5b8 my_print_stacktrace + 40
1   mysqld                              0x000cb20d handle_segfault + 1037
2   libSystem.B.dylib                   0x927ea2bb _sigtramp + 43
3   ???                                 0xffffffff 0x0 + 4294967295
4   mysqld                              0x004944fc my_wildcmp_unicode + 2556
5   mysqld                              0x00125933 _Z13check_db_nameP19st_mysql_lex_string + 227
6   mysqld                              0x000da9f2 _ZN13st_select_lex17add_table_to_listEP3THDP11Table_identP19st_mysql_lex_stringm13thr_lock_typeP4ListI10Index_hintES5_ + 946
7   mysqld                              0x0000cce6 _Z14set_part_stateP10Alter_infoP14partition_info15partition_state + 422
8   mysqld                              0x00011ac7 _Z22mysql_unpack_partitionP3THDPKcjS2_jP5TABLEbP10handlertonPb + 167
9   mysqld                              0x0012881c _Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb + 780
10  mysqld                              0x001c49b3 _Z27ha_create_table_from_engineP3THDPKcS2_ + 563
11  mysqld                              0x00274df5 _Z28ndb_create_table_from_engineP3THDPKcS2_ + 85
12  mysqld                              0x0028989a _Z36ndbcluster_setup_binlog_table_sharesP3THD + 378
13  mysqld                              0x0027be2b ndb_util_thread_func + 1723
14  libSystem.B.dylib                   0x927af155 _pthread_start + 321
15  libSystem.B.dylib                   0x927af012 thread_start + 34
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x0 is an invalid pointer
thd->thread_id=0
thd->killed=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.
Writing a core file

How to repeat:
http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2777602