[MDEV-20975] [ERROR] mysqld got signal 11 Created: 2019-11-05  Updated: 2020-02-14  Resolved: 2020-02-14

Status: Closed
Project: MariaDB Server
Component/s: Plugin - SQL_ERROR_LOG
Affects Version/s: 10.3.8
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Seungwon Assignee: Unassigned
Resolution: Incomplete Votes: 2
Labels: crash, need_feedback

Issue Links:
Duplicate
duplicates MDEV-21080 When i execute With query, database r... Closed

 Description   

my mariadb got the error message : [ERROR] mysqld got signal 11
and then, connection was stuck..
so i reboot the database, but still occur the same error and also service was not normal.
this is my error log

191104 23:47:49 [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.8-MariaDB-log
key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=97
max_threads=1002
thread_count=70
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4142942 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2ae43af2d108
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 = 0x2ae14edc1de8 thread_stack 0x40000
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace+0x29)[0x55912a8725f9]
/rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0x57d)[0x55912a3055ed]
2019-11-04 23:48:01 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-04 23:48:01 0 [Note] InnoDB: Uses event mutexes
2019-11-04 23:48:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-11-04 23:48:01 0 [Note] InnoDB: Number of pools: 1
2019-11-04 23:48:01 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-11-04 23:48:01 0 [Note] InnoDB: Initializing buffer pool, total size = 11G, instances = 8, chunk size = 128M
2019-11-04 23:48:01 0 [Note] InnoDB: Completed initialization of buffer pool
2019-11-04 23:48:01 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-11-04 23:48:01 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=12547168963
2019-11-04 23:48:01 0 [Note] InnoDB: Starting final batch to recover 2 pages from redo log.
2019-11-04 23:48:02 0 [Note] InnoDB: Last binlog file 'mysql-bin-changelog.000004', position 1065
2019-11-04 23:48:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-11-04 23:48:02 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-11-04 23:48:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-11-04 23:48:02 0 [Note] InnoDB: Setting file '/rdsdbdata/db/innodb/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-11-04 23:48:02 0 [Note] InnoDB: File '/rdsdbdata/db/innodb/ibtmp1' size is now 12 MB.
2019-11-04 23:48:02 0 [Note] InnoDB: Waiting for purge to start
2019-11-04 23:48:02 0 [Note] InnoDB: 10.3.8 started; log sequence number 12547169093; transaction id 1130423
2019-11-04 23:48:02 0 [Note] InnoDB: Loading buffer pool(s) from /rdsdbdata/db/innodb/ib_buffer_pool
2019-11-04 23:48:02 0 [Note] Plugin 'FEEDBACK' is disabled.
191104 23:48:02 server_audit: MariaDB Audit Plugin version 1.4.0 STARTED.
191104 23:48:02 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.2019-11-04 23:48:02 0 [Warning] /rdsdbbin/mysql/bin/mysqld: unknown variable 'loose-rocksdb_log_dir=/rdsdbdata/db/log'
2019-11-04 23:48:02 0 [Note] Recovering after a crash using /rdsdbdata/log/binlog/mysql-bin-changelog
2019-11-04 23:48:02 0 [Note] Starting crash recovery...
2019-11-04 23:48:02 0 [Note] Crash recovery finished.
2019-11-04 23:48:02 0 [Note] Server socket created on IP: '::'.
2019-11-04 23:48:02 0 [Note] Reading of all Master_info entries succeded
2019-11-04 23:48:02 0 [Note] Added new Master_info '' to hash table
2019-11-04 23:48:02 0 [Note] /rdsdbbin/mysql/bin/mysqld: ready for connections.
Version: '10.3.8-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution



 Comments   
Comment by Elena Stepanova [ 2019-11-05 ]

You have set the component to 'Plugin - SQL_ERROR_LOG'. Does it mean you have identified the query, specific configuration or use case which causes the failure?

Comment by Seungwon [ 2019-11-06 ]

yes i was plugin that component.
after that error i also got the same error message with query.
This one..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191104 23:48:03 [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.8-MariaDB-log
key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=2
max_threads=1002
thread_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4142942 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2b209a650008
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 = 0x2b1d4fe96de8 thread_stack 0x40000
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace+0x29)[0x55c03845f5f9]
mysys/stacktrace.c:270(my_print_stacktrace)[0x55c037ef25ed]
sigaction.c:0(__restore_rt)[0x2b1d50c15100]
/rdsdbbin/mysql/bin/mysqld(+0xde5d99)[0x55c03849ad99]
strings/ctype-utf8.c:5302(my_strcasecmp_utf8)[0x55c037d20636]
sql/sql_parse.cc:7297(check_table_access(THD*, unsigned long, TABLE_LIST*, bool, unsigned int, bool))[0x55c037d2690f]
sql/sql_parse.cc:3780(mysql_execute_command(THD*))[0x55c037d2e6cc]
sql/sql_parse.cc:8236(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x55c037d30fad]
sql/sql_parse.cc:1851(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x55c037d31b6f]
sql/sql_parse.cc:1399(do_command(THD*))[0x55c037dfaeec]
sql/sql_connect.cc:1445(do_handle_one_connection(CONNECT*))[0x55c037dfb0c4]
sql/sql_connect.cc:1353(handle_one_connection)[0x55c0384116fa]
pthread_create.c:0(start_thread)[0x2b1d50c0ddc5]
/lib64/libc.so.6(clone+0x6d)[0x2b1d51430c9d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2b209a6a06e0): WITH W_DATA AS ( SELECT 1 AS ORD_NUM , 'CNYS' AS CNYS_BRHS_TYPE , LPAD(REPLACE(A01.DONG_NAME, ' ', ''), 4, 0) AS DONG_ORD , A01.HO_NAME AS HO_ORD , A01.DONG_NAME /* / , A01.HO_NAME / / , A01.MVN_DATE / / , A01.LVHS_DATE / / , CONCAT(SUBSTR(IF(A01.MVN_USER_NAME, NULL, A02.USER_NAME), 1, 1), REGEXP_REPLACE(SUBSTR(IF(A01.MVN_USER_NAME, NULL, A02.USER_NAME), 2),'[ - a-z]','')) AS USER_NAME /* ( * ) / FROM RNDP.TB_SUP_CNYS_INFO A01 LEFT OUTER JOIN RNDP.TB_SYS_USER A02 / / ON A02.USER_NO = A01.MVN_USER_NO WHERE A01.MVN_USER_NAME != ' ' UNION ALL SELECT 2 AS ORD_NUM , 'BRHS' AS CNYS_BRHS_TYPE , DONG_NAME AS DONG_ORD , CASE / A, B A,B 11 ( ) / WHEN LEFT(A01.HO_NAME, 1) IN ('A', 'B') THEN LPAD(SUBSTRING(A01.HO_NAME, 2), 11, 0) ELSE LPAD(A01.HO_NAME, 11, 0) END HO_ORD / / , A01.DONG_NAME / / , A01.HO_NAME / / , A02.MVN_DATE / / , A02.LVHS_DATE / / , CONCAT(SUBSTR(IF(A03.USER_NAME, NULL, A02.MVN_NAME), 1, 1), REGEXP_REPLACE(SUBSTR(IF(A03.USER_NAME, NULL, A02.MVN_NAME), 2),'[ - a-z]','')) AS USER_NAME /* ( * ) / FROM RNDP.TB_SUP_BRHS_INFO A01 / / INNER JOIN RNDP.TB_SUP_BRHS_MVN_INFO A02 / / ON A01.MVN_SN = A02.MVN_SN LEFT OUTER JOIN RNDP.TB_SYS_USER A03 / / ON A03.USER_NO = A02.MVN_MAN_USER_NO ) SELECT A01.CNYS_BRHS_TYPE , A01.DONG_NAME / / , A01.HO_NAME / / , DATE_FORMAT(A01.MVN_DATE, '%Y.%m.%d') AS MVN_DATE / / , DATE_FORMAT(A01.LVHS_DATE, '%Y.%m.%d') AS LVHS_DATE / / , A01.USER_NAME / ( * ) */ FROM W_DATA A01 WHERE 1 = 1 LIMIT 0, 200
Connection ID (thread ID): 10
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Comment by Seungwon [ 2019-11-06 ]

and also this error message also show..

2019-11-05 0:39:25 127 [ERROR] mysqld: Can't find record in 'slow_log'
2019-11-05 0:39:25 127 [ERROR] Failed to write to mysql.slow_log: Can't find record in 'slow_log'

Comment by Seungwon [ 2019-11-26 ]

Hi, This is Jang.
i found how to replay this situation.
When i connect mariadb by client (Workbench, HeidiSQL...)
And.. if my session db value is NULL by 'show processlist' query.
at that time, when i execute WITH query, database restarted.
but, if i set my database by "use 'db_nameb'" query.
WITH query work well..
i hope this action help for you.
Thanks.

Comment by Elena Stepanova [ 2020-01-14 ]

There have been bugs fixed since 10.3.8 which were related to executing CTE without having the current database (just as you described). Although those failures didn't look exactly like your crash, they could still have the same root cause. It would be very helpful if you could try a recent 10.3 version and see if it still fails.

Generated at Thu Feb 08 09:03:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.