Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL)
-
CentOS release 6.4 (Final)
Description
The stack trace indicates that the issue was caused while writing the server's own binlogs (this is verified by the binlogs which were not written properly):
150408 12:13:53 [ERROR] 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.
|
|
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
|
|
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.
|
|
Server version: 10.0.17-MariaDB-log
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=226
|
max_threads=302
|
thread_count=200
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 794455 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x7ee81d936008
|
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 = 0x7ee79d89dd30 thread_stack 0x30000
|
(my_addr_resolve failure: fork)
|
/usr/sbin/mysqld(my_print_stacktrace+0x2b) [0xb743db]
|
/usr/sbin/mysqld(handle_fatal_signal+0x398) [0x726a38]
|
/lib64/libpthread.so.0() [0x3891e0f500]
|
/lib64/libc.so.6(memcpy+0xa0) [0x3891a89900]
|
/usr/sbin/mysqld(_my_b_write+0x4f) [0xb5a36f]
|
/usr/sbin/mysqld(Log_event::wrapper_my_b_safe_write(st_io_cache*, unsigned char const*, unsigned long)+0x5a) [0x7ded3a]
|
/usr/sbin/mysqld(User_var_log_event::write(st_io_cache*)+0xfd) [0x7df76d]
|
/usr/sbin/mysqld(MYSQL_BIN_LOG::write(Log_event*, char*)+0x40b) [0x7d271b]
|
/usr/sbin/mysqld(close_temporary_tables(THD*)+0x389) [0x591e29]
|
/usr/sbin/mysqld(THD::cleanup()+0x3d) [0x5a6cfd]
|
/usr/sbin/mysqld(unlink_thd(THD*)+0x13) [0x54bd43]
|
/usr/sbin/mysqld(one_thread_per_connection_end(THD*, bool)+0x10) [0x54bf50]
|
/usr/sbin/mysqld(do_handle_one_connection(THD*)+0x29b) [0x69621b]
|
/usr/sbin/mysqld(handle_one_connection+0x42) [0x6964a2]
|
/lib64/libpthread.so.0() [0x3891e07851]
|
/lib64/libc.so.6(clone+0x6d) [0x3891ae894d]
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x0): is an invalid pointer
|
Connection ID (thread ID): 62268
|
Status: KILL_CONNECTION
|
|
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=off,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=off,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=on,mrr_cost_based=on,mrr_sort_keys=off,outer_join_with_cache=off,semijoin_with_cache=off,join_cache_incremental=off,join_cache_hashed=off,join_cache_bka=off,optimize_join_buffer_size=off,table_elimination=off,extended_keys=on,exists_to_in=on
|
|
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.
|
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
The stack trace indicates that the issue was caused while writing the server's own binlogs (this is verified by the binlogs which were not written properly): 150408 12:13:53 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 10.0.17-MariaDB-log key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=226 max_threads=302 thread_count=200 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 794455 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7ee81d936008 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 = 0x7ee79d89dd30 thread_stack 0x30000 (my_addr_resolve failure: fork) /usr/sbin/mysqld(my_print_stacktrace+0x2b) [0xb743db] /usr/sbin/mysqld(handle_fatal_signal+0x398) [0x726a38] /lib64/libpthread.so.0() [0x3891e0f500] /lib64/libc.so.6(memcpy+0xa0) [0x3891a89900] /usr/sbin/mysqld(_my_b_write+0x4f) [0xb5a36f] /usr/sbin/mysqld(Log_event::wrapper_my_b_safe_write(st_io_cache*, unsigned char const*, unsigned long)+0x5a) [0x7ded3a] /usr/sbin/mysqld(User_var_log_event::write(st_io_cache*)+0xfd) [0x7df76d] /usr/sbin/mysqld(MYSQL_BIN_LOG::write(Log_event*, char*)+0x40b) [0x7d271b] /usr/sbin/mysqld(close_temporary_tables(THD*)+0x389) [0x591e29] /usr/sbin/mysqld(THD::cleanup()+0x3d) [0x5a6cfd] /usr/sbin/mysqld(unlink_thd(THD*)+0x13) [0x54bd43] /usr/sbin/mysqld(one_thread_per_connection_end(THD*, bool)+0x10) [0x54bf50] /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x29b) [0x69621b] /usr/sbin/mysqld(handle_one_connection+0x42) [0x6964a2] /lib64/libpthread.so.0() [0x3891e07851] /lib64/libc.so.6(clone+0x6d) [0x3891ae894d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 62268 Status: KILL_CONNECTION Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=off,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=off,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=on,mrr_cost_based=on,mrr_sort_keys=off,outer_join_with_cache=off,semijoin_with_cache=off,join_cache_incremental=off,join_cache_hashed=off,join_cache_bka=off,optimize_join_buffer_size=off,table_elimination=off,extended_keys=on,exists_to_in=on 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. |
The stack trace indicates that the issue was caused while writing the server's own binlogs (this is verified by the binlogs which were not written properly): {noformat} 150408 12:13:53 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 10.0.17-MariaDB-log key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=226 max_threads=302 thread_count=200 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 794455 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7ee81d936008 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 = 0x7ee79d89dd30 thread_stack 0x30000 (my_addr_resolve failure: fork) /usr/sbin/mysqld(my_print_stacktrace+0x2b) [0xb743db] /usr/sbin/mysqld(handle_fatal_signal+0x398) [0x726a38] /lib64/libpthread.so.0() [0x3891e0f500] /lib64/libc.so.6(memcpy+0xa0) [0x3891a89900] /usr/sbin/mysqld(_my_b_write+0x4f) [0xb5a36f] /usr/sbin/mysqld(Log_event::wrapper_my_b_safe_write(st_io_cache*, unsigned char const*, unsigned long)+0x5a) [0x7ded3a] /usr/sbin/mysqld(User_var_log_event::write(st_io_cache*)+0xfd) [0x7df76d] /usr/sbin/mysqld(MYSQL_BIN_LOG::write(Log_event*, char*)+0x40b) [0x7d271b] /usr/sbin/mysqld(close_temporary_tables(THD*)+0x389) [0x591e29] /usr/sbin/mysqld(THD::cleanup()+0x3d) [0x5a6cfd] /usr/sbin/mysqld(unlink_thd(THD*)+0x13) [0x54bd43] /usr/sbin/mysqld(one_thread_per_connection_end(THD*, bool)+0x10) [0x54bf50] /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x29b) [0x69621b] /usr/sbin/mysqld(handle_one_connection+0x42) [0x6964a2] /lib64/libpthread.so.0() [0x3891e07851] /lib64/libc.so.6(clone+0x6d) [0x3891ae894d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 62268 Status: KILL_CONNECTION Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=off,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=off,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=on,mrr_cost_based=on,mrr_sort_keys=off,outer_join_with_cache=off,semijoin_with_cache=off,join_cache_incremental=off,join_cache_hashed=off,join_cache_bka=off,optimize_join_buffer_size=off,table_elimination=off,extended_keys=on,exists_to_in=on 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. {noformat} |
Due Date | 2015-05-14 |
Due Date | 2015-05-14 |
Assignee | Elena Stepanova [ elenst ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 10.1 [ 16100 ] | |
Fix Version/s | 10.0 [ 16000 ] | |
Fix Version/s | 5.5 [ 15800 ] | |
Affects Version/s | 10.1 [ 16100 ] | |
Affects Version/s | 10.0 [ 16000 ] | |
Affects Version/s | 5.5 [ 15800 ] | |
Affects Version/s | 10.0.17 [ 18300 ] | |
Assignee | Elena Stepanova [ elenst ] | Sergei Golubchik [ serg ] |
Labels | verified |
Assignee | Sergei Golubchik [ serg ] | Elena Stepanova [ elenst ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Assignee | Elena Stepanova [ elenst ] | Sergei Golubchik [ serg ] |
Component/s | Replication [ 10100 ] | |
Fix Version/s | 10.0.18 [ 18702 ] | |
Fix Version/s | 10.1.5 [ 18813 ] | |
Fix Version/s | 5.5.43 [ 18601 ] | |
Fix Version/s | 5.5 [ 15800 ] | |
Fix Version/s | 10.0 [ 16000 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Workflow | MariaDB v2 [ 60393 ] | MariaDB v3 [ 65508 ] |
Workflow | MariaDB v3 [ 65508 ] | MariaDB v4 [ 149022 ] |
Some additional details:
1.) This node has no slave nodes connected - binlogs are written in case point in time recovery is needed
2.) This is a slave of 2x hosts and uses multi-source replication - the last transaction received from one of the hosts was a rollback after a DROP TEMPORARY TABLE xxx / generated by server /
3.) Thread pool is not being used