[MDEV-19721] use information_schema results in "[ERROR] mysqld got signal 11" Created: 2019-06-08  Updated: 2019-06-10  Resolved: 2019-06-10

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.15
Fix Version/s: 10.3.16

Type: Bug Priority: Major
Reporter: Gordan Bobic Assignee: Anel Husakovic
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 7, x86-64


Issue Links:
Duplicate
is duplicated by MDEV-19490 show tables fails when selecting the ... Closed

 Description   

# mysql
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 10
Server version: 10.3.15-MariaDB-log MariaDB Server
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
MariaDB [(none)]> use information_schema
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
 
Database changed
MariaDB [information_schema]> show tables;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
ERROR: Can't connect to the server
 
unknown [information_schema]> 

190608 16:16:40 [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 https://mariadb.com/kb/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.3.15-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=4
max_threads=153
thread_count=11
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467420 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f6e040009a8
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 = 0x7f6e62f27d00 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55f02512391e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55f024bc053f]
sigaction.c:0(__restore_rt)[0x7f6e7527c5d0]
/usr/sbin/mysqld(+0xd1acb7)[0x55f02515ccb7]
/usr/sbin/mysqld(_Z17find_schema_tableP3THDPK25st_mysql_const_lex_stringPb+0x55)[0x55f024a596b5]
/usr/sbin/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjPP19Sroutine_hash_entryjP19Prelocking_strategy+0x942)[0x55f024990632]
/usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTjj+0x67)[0x55f024991217]
/usr/sbin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x35)[0x55f024a49415]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x24ad)[0x55f0249f404d]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x13e)[0x55f0249f473e]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1aa)[0x55f024ac579a]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55f024ac58bd]
/usr/sbin/mysqld(+0xc9629d)[0x55f0250d829d]
pthread_create.c:0(start_thread)[0x7f6e75274dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f6e73616ead]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f6e0400f4a0): 
Connection ID (thread ID): 23
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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             63309                63309                processes 
Max open files            16364                16364                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       63309                63309                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        

This is related to full loading of table structures in information_schema by the mysql client on database change. Starting mysql client with mysql -A results in a workable information_schema. Manually doing "SHOW CREATE TABLE" on each of the tables in the information_schema or "SELECT * FROM" each of the tables doesn't result in the segfault.



 Comments   
Comment by Anel Husakovic [ 2019-06-09 ]

Patch `ef04a7123a7beed5bf20736`

Comment by Anel Husakovic [ 2019-06-10 ]

10.3.15 is already released, this bug is fixed in 10.3.16.

Generated at Thu Feb 08 08:53:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.