maria-developers team mailing list archive

[Roberto Spadim <roberto@xxxxxxxxxxxxx>]

information at crash
​


161222  2:52:15 [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.1.5-MariaDB-log
key_buffer_size=629145600
read_buffer_size=4194304
max_used_connections=34
max_threads=52
thread_count=14
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
1041422 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f10b5d10008
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 = 0x7f10ea1fae80 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0x7f10f241eb0b]
sql/signal_handler.cc:153(handle_fatal_signal)[0x7f10f1fb8db5]
/lib64/libpthread.so.0(+0x10d00)[0x7f10f0b4bd00]
sql/sql_plist.h:181(I_P_List_iterator)[0x7f10f1f6af03]
mysys/lf_hash.c:125(lfind)[0x7f10f24281a0]
sql/table_cache.cc:1084(tdc_iterate(THD*, char (*)(void*, void*), void*,
bool))[0x7f10f1f6c4e3]
sql/table_cache.cc:267(tc_add_table(THD*, TABLE*))[0x7f10f1f6c808]
sql/sql_base.cc:2572(open_table(THD*, TABLE_LIST*,
Open_table_context*))[0x7f10f1e01272]
sql/sql_base.cc:4016(open_and_process_table)[0x7f10f1e050c8]
sql/sql_base.cc:5184(open_and_lock_tables(THD*, DDL_options_st const&,
TABLE_LIST*, bool, unsigned int, Prelocking_strategy*))[0x7f10f1e05394]
sql/sql_insert.cc:719(mysql_insert(THD*, TABLE_LIST*, List<Item>&,
List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates,
bool))[0x7f10f1e2e56e]
sql/sql_parse.cc:3866(mysql_execute_command(THD*))[0x7f10f1e45d2c]
sql/sql_parse.cc:7173(mysql_parse)[0x7f10f1e4bc3d]
sql/sql_parse.cc:1470(dispatch_command(enum_server_command, THD*, char*,
unsigned int))[0x7f10f1e4e2a8]
sql/sql_parse.cc:1095(do_command(THD*))[0x7f10f1e4e83b]
sql/sql_connect.cc:1347(do_handle_one_connection(THD*))[0x7f10f1f115ef]
sql/sql_connect.cc:1260(handle_one_connection)[0x7f10f1f11747]
/lib64/libpthread.so.0(+0x7654)[0x7f10f0b42654]
/lib64/libc.so.6(clone+0x6d)[0x7f10f02667dd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f10a85ba020): is an invalid pointer
Connection ID (thread ID): 35347
Status: NOT_KILLED

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=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,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.
161222 02:52:16 mysqld_safe Number of processes running now: 0
161222 02:52:16 mysqld_safe mysqld restarted
2016-12-22  2:52:16 140012144617344 [Warning] 'THREAD_CONCURRENCY' is
deprecated and will be removed in a future release.
2016-12-22  2:52:16 140012144617344 [Note] /usr/mariadb/mariadb/bin//mysqld
(mysqld 10.1.5-MariaDB-log) starting as process 31925 ...
2016-12-22  2:52:16 140012144617344 [Note] mysqld: Aria engine: starting
recovery
recovered pages: 0% 3082852397% 0%161222  2:52:16 [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