Description:
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=16777216
read_buffer_size=1044480
max_used_connections=56
max_connections=100
threads_connected=12
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 220783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x4305b778
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=0xbf99d308, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a0a12
0x82fb4e8
0x815380f
0x805386b
0x81858ac
0x818b60d
0x8189699
0x8188d3b
0x818966c
0x8186947
0x818732b
0x8066d69
0x8066cb1
0x83980ae
0x8053943
0x8055deb
0x8189161
0x8188d3b
0x8189134
0x8186947
0x8186e67
0x81921b9
0x80d9aa5
0x80fa95c
0x80b4332
0x8101f7f
0x8101115
0x80b0d18
0x80b06f3
0x80afc84
0x82f8c9c
0x83412ea
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 0x4307d058 is invalid pointer
thd->thread_id=5411
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
070309 11:08:30 mysqld restarted
070309 11:08:31 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=strato5-bin' to avoid this problem.
070309 11:08:31 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...
070309 11:08:31 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1442570400.
InnoDB: Doing recovery: scanned up to log sequence number 0 1442573589
070309 11:08:32 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 7210585, file name ./strato5-bin.000006
070309 11:08:32 InnoDB: Started; log sequence number 0 1442573589
070309 11:08:32 [Note] Recovering after a crash using strato5-bin
070309 11:08:32 [Note] Starting crash recovery...
070309 11:08:32 [Note] Crash recovery finished.
070309 11:08:33 [Note] /usr/share/mysql-standard-5.0.27/bin/mysqld: ready for connections.
Version: '5.0.27-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
----------------------------------------------------------------
mysqld.stack
0x80a0a12 handle_segfault + 430
0x82fb4e8 pthread_sighandler + 184
0x815380f field_conv__FP5FieldT0 + 375
0x805386b save_in_field__10Item_fieldP5Fieldb + 111
0x81858ac sp_eval_expr__FP3THDP5FieldPP4Item + 112
0x818b60d set_return_value__11sp_rcontextP3THDPP4Item + 33
0x8189699 exec_core__16sp_instr_freturnP3THDPUi + 41
0x8188d3b reset_lex_and_exec_core__13sp_lex_keeperP3THDPUibP8sp_instr + 223
0x818966c execute__16sp_instr_freturnP3THDPUi + 36
0x8186947 execute__7sp_headP3THD + 875
0x818732b execute_function__7sp_headP3THDPP4ItemUiP5Field + 1095
0x8066d69 execute_impl__12Item_func_spP3THDP5Field + 101
0x8066cb1 execute__12Item_func_spPP5Field + 157
0x83980ae val_str__12Item_func_spP6String + 110
0x8053943 save_in_field__4ItemP5Fieldb + 147
0x8055deb set_value__18Item_trigger_fieldP3THDP11sp_rcontextPP4Item + 91
0x8189161 exec_core__26sp_instr_set_trigger_fieldP3THDPUi + 41
0x8188d3b reset_lex_and_exec_core__13sp_lex_keeperP3THDPUibP8sp_instr + 223
0x8189134 execute__26sp_instr_set_trigger_fieldP3THDPUi + 36
0x8186947 execute__7sp_headP3THD + 875
0x8186e67 execute_trigger__7sp_headP3THDPCcT2P13st_grant_info + 315
0x81921b9 process_triggers__19Table_triggers_listP3THD14trg_event_type20trg_action_time_typeb + 157
0x80d9aa5 fill_record_n_invoke_before_triggers__FP3THDRt4List1Z4ItemT1bP19Table_triggers_list14trg_event_type + 73
0x80fa95c mysql_insert__FP3THDP13st_table_listRt4List1Z4ItemRt4List1Zt4List1Z4ItemT2T215enum_duplicatesb + 1480
0x80b4332 mysql_execute_command__FP3THD + 7966
0x8101f7f execute__18Prepared_statementP6Stringb + 551
0x8101115 mysql_stmt_execute__FP3THDPcUi + 289
0x80b0d18 dispatch_command__F19enum_server_commandP3THDPcUi + 1560
0x80b06f3 do_command__FP3THD + 195
0x80afc84 handle_one_connection + 764
0x82f8c9c pthread_start_thread + 220
0x83412ea thread_start + 4
How to repeat:
Mysql Version: 5.0.27-standard running in production on suse 8 linux server.
