[MDEV-20270] Userstat causing signal 11 crash in 10.4.7 Created: 2019-08-07  Updated: 2019-10-06  Resolved: 2019-10-06

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.4.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Todd Stoffel (Inactive) Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Centos 7



 Description   

my.cnf files that include the following line:

userstat = ON

cause MariaDB server to crash with signal 11

2019-08-06 17:56:58 0 [Note] InnoDB: Using Linux native AIO
2019-08-06 17:56:58 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-08-06 17:56:58 0 [Note] InnoDB: Uses event mutexes
2019-08-06 17:56:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-08-06 17:56:58 0 [Note] InnoDB: Number of pools: 1
2019-08-06 17:56:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-08-06 17:56:58 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2019-08-06 17:56:58 0 [Note] InnoDB: Completed initialization of buffer pool
2019-08-06 17:56:58 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-08-06 17:56:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-08-06 17:56:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-08-06 17:56:58 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-08-06 17:56:58 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-08-06 17:56:58 0 [Note] InnoDB: Waiting for purge to start
2019-08-06 17:56:58 0 [Note] InnoDB: 10.4.7 started; log sequence number 48353487654; transaction id 144244470
2019-08-06 17:56:58 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
190806 17:56:58 [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.4.7-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=65537
thread_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 142751901 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fd9cc007ab8
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 = 0x7fd9cbffec60 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55ca3ae626be]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55ca3a8f181f]
sigaction.c:0(__restore_rt)[0x7fda857f35d0]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fd9cc00eb30): create table if not exists mysql.spider_xa(  format_id int not null default 0,  gtrid_length int not null default 0,  bqual_length int not null default 0,  data char(128) charset binary not null default '',  status char(8) not null default '',  primary key (data, format_id, gtrid_length),  key idx1 (status)) engine=MyISAM default charset=utf8 collate=utf8_bin
Connection ID (thread ID): 7
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=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             14969                14969                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       14969                14969                signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us
Core pattern: core



 Comments   
Comment by Alice Sherepa [ 2019-08-07 ]

Could you please provide your .cnf file, I could not reproduce the crash:

MariaDB [(none)]> create table if not exists mysql.spider_xa(  format_id int not null default 0,  gtrid_length int not null default 0,  bqual_length int not null default 0,  data char(128) charset binary not null default '',  status char(8) not null default '',  primary key (data, format_id, gtrid_length),  key idx1 (status)) engine=MyISAM default charset=utf8 collate=utf8_bin;
Query OK, 0 rows affected (0.006 sec)
 
MariaDB [(none)]> show variables like 'userstat';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| userstat      | ON    |
+---------------+-------+
1 row in set (0.001 sec)
 
MariaDB [(none)]> select version();
+----------------+
| version()      |
+----------------+
| 10.4.7-MariaDB |
+----------------+
1 row in set (0.000 sec)

Comment by Elena Stepanova [ 2019-09-04 ]

toddstoffel,

The crash in your log happens on startup. Is it bootstrap which you run manually, or is it package installation (spider package installation, to be precise), or...?

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