Description:
stack dump trace is :
0x80a8e99 handle_segfault + 533
0x83825d8 pthread_sighandler + 184
0x80542ba replace_equal_field__10Item_fieldPc + 34
0x804d9ee transform__4ItemPM4ItemFP4ItemPc_P4ItemPc + 54
0x8060aec transform__9Item_funcPM4ItemFP4ItemPc_P4ItemPc + 64
0x80fca85 substitute_for_best_equal_field__FP4ItemP10COND_EQUALPv + 629
0x80fc8f1 substitute_for_best_equal_field__FP4ItemP10COND_EQUALPv + 225
0x80fc8f1 substitute_for_best_equal_field__FP4ItemP10COND_EQUALPv + 225
0x80efa9e optimize__4JOIN + 2070
0x80f2afb mysql_select__FP3THDPPP4ItemP10TABLE_LISTUiRt4List1Z4ItemP4ItemUiP8st_orderT7T5T7UxP13select_resultP18st_select_lex_unitP13st_s + 843
0x80ee5d4 handle_select__FP3THDP6st_lexP13select_resultUl + 244
0x80be1fc mysql_execute_command__FP3THD + 9868
0x81b401a exec_core__13sp_instr_stmtP3THDPUi + 26
0x81b3d26 reset_lex_and_exec_core__13sp_lex_keeperP3THDPUibP8sp_instr + 206
0x81b3eed execute__13sp_instr_stmtP3THDPUi + 133
0x81b1544 execute__7sp_headP3THD + 928
0x81b1a96 execute_trigger__7sp_headP3THDPCcT2P13st_grant_info + 330
0x81bd4e9 process_triggers__19Table_triggers_listP3THD14trg_event_type20trg_action_time_typeb + 157
0x81191ff mysql_update__FP3THDP10TABLE_LISTRt4List1Z4ItemT2P4ItemUiP8st_orderUx15enum_duplicatesb + 3867
0x80bddfd mysql_execute_command__FP3THD + 8845
0x80c2d17 mysql_parse__FP3THDPCcUiPPCc + 311
0x80ba60b dispatch_command__F19enum_server_commandP3THDPcUi + 1839
0x80b9e16 do_command__FP3THD + 198
0x80b9304 handle_one_connection + 860
0x837fd8c pthread_start_thread + 220
I got the error :
Number of processes running now: 0
110224 19:41:02 mysqld restarted
110224 19:41:02 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
InnoDB: Log scan progressed past the checkpoint lsn 16 361199445
110224 19:41:02 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: Doing recovery: scanned up to log sequence number 16 361696549
110224 19:41:02 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 8942063, file name /mysqllog/CI/binlogs/bin.005147
110224 19:41:05 InnoDB: Started; log sequence number 16 361696549
110224 19:41:05 [Note] Recovering after a crash using /mysqllog/CI/binlogs/bin
110224 19:41:05 [Note] Starting crash recovery...
110224 19:41:05 [Note] Crash recovery finished.
110224 19:41:06 [Note] /mysql/CI/basedir/bin/mysqld: ready for connections.
Version: '5.0.89-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
110224 20:11:32 - 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=209715200
read_buffer_size=10485760
max_used_connections=28
max_connections=300
threads_connected=26
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 618496 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xa22e620
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=0xffc3df98, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a8e99
0x83825d8
0x80542ba
0x804d9ee
0x8060aec
0x80fca85
0x80fc8f1
0x80fc8f1
0x80efa9e
0x80f2afb
0x80ee5d4
0x80be1fc
0x81b401a
0x81b3d26
0x81b3eed
0x81b1544
0x81b1a96
0x81bd4e9
0x81191ff
0x80bddfd
0x80c2d17
0x80ba60b
0x80b9e16
0x80b9304
0x837fd8c
0x83cfc1a
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 0xa30c798 = insert into datasync.sym_data_event (node_id, data_id, channel_id, transaction_id) (select node_id, last_insert_id(), 'ci_sapdata_channel', datasync.fn_transaction_id() from datasync.sym_node c where ^M
c.node_group_id='bo' and c.sync_enabled=1 and (@sync_node_disabled is null or @sync_node_disabled != c.node_id)and c.node_id= NAME_CONST('lTEMP_STORE_ID',_latin1'A040' COLLATE 'latin1_swedish_ci'))
thd->thread_id=154
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.
please tell me what is the problem , is this table is creating a problem.
How to repeat:
we are using symmetric DS tool , this table is part of that schema.
i am not able to repeat it on another test servers, this is happening on production server only
