[MDEV-19583] [ERROR] mysqld got signal 11 Created: 2019-05-24  Updated: 2019-06-04  Resolved: 2019-05-24

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

Type: Bug Priority: Major
Reporter: Matteo Balzarotti Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: crash
Environment:

GNU/Linux CentOS 7.6; Ram : 64 GB; Cpu : 8 core; Disco : 120GB ( rootvg + swap ) ;


Attachments: Text File Errlog-bug.txt     Microsoft Word Query Cognos.rtf    
Issue Links:
Duplicate
duplicates MDEV-15837 Assertion `item1->type() == Item::FIE... Closed

 Description   

When we run the query in attachment from sql client tool or directly on the server we get the following error:

2019-05-24 11:15:02 18 [ERROR] Invalid (old?) table or database name '.cache'
2019-05-24 11:15:02 18 [ERROR] Invalid (old?) table or database name '.config'
2019-05-24 11:15:20 19 [ERROR] Invalid (old?) table or database name '.cache'
2019-05-24 11:15:20 19 [ERROR] Invalid (old?) table or database name '.config'
190524 11:15:37 [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.13-MariaDB-log
key_buffer_size=536870912
read_buffer_size=4194304
max_used_connections=8
max_threads=153
thread_count=15
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1781053 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fa1600009a8
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 = 0x7fa1daa6cd78 thread_stack 0x80000
/usr/local/mariadb/columnstore/mysql//bin/mysqld(my_print_stacktrace+0x29)[0x562bc7fabac9]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(handle_fatal_signal+0x33f)[0x562bc7ae46ff]
sigaction.c:0(__restore_rt)[0x7fa8b224e5d0]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(+0x6b0689)[0x562bc7a59689]
sql/sql_window.cc:435(compare_order_elements)[0x562bc7a598bc]
sql/sql_window.cc:572(compare_window_funcs_by_window_specs(Item_window_func*, Item_window_func*, void*))[0x562bc7a5cb09]
sql/sql_list.h:589(bubble_sort<Item_window_func>)[0x562bc79813a2]
sql/sql_select.cc:3340(JOIN::make_aggr_tables_info())[0x562bc7988251] 
sql/sql_list.h:589(bubble_sort<Item_window_func>)[0x562bc79813a2]
sql/sql_select.cc:3340(JOIN::make_aggr_tables_info())[0x562bc7988251]
sql/sql_select.cc:2635(JOIN::optimize_stage2())[0x562bc7989c0e]
sql/sql_select.cc:1934(JOIN::optimize_inner())[0x562bc798b52f]
sql/sql_select.cc:1453(JOIN::optimize())[0x562bc790631e]
sql/sql_derived.cc:935(mysql_derived_optimize(THD*, LEX*, TABLE_LIST*))[0x562bc7905bed]
sql/sql_derived.cc:197(mysql_handle_single_derived(LEX*, TABLE_LIST*, unsigned int))[0x562bc7989214]
sql/sql_select.cc:1727(JOIN::optimize_inner())[0x562bc798b52f]
sql/sql_select.cc:1453(JOIN::optimize())[0x562bc790631e]
sql/sql_derived.cc:935(mysql_derived_optimize(THD*, LEX*, TABLE_LIST*))[0x562bc7905bed]
sql/sql_derived.cc:197(mysql_handle_single_derived(LEX*, TABLE_LIST*, unsigned int))[0x562bc7989214]
sql/sql_select.cc:1727(JOIN::optimize_inner())[0x562bc798b52f]
sql/sql_select.cc:1453(JOIN::optimize())[0x562bc798cbf8]
sql/sql_select.cc:4511(mysql_select(THD*, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long$
sql/sql_select.cc:385(handle_select(THD*, LEX*, select_result*, unsigned long))[0x562bc793d539]
sql/sql_parse.cc:4290(mysql_execute_command(THD*))[0x562bc793dfa2]
sql/sql_parse.cc:8143(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x562bc793ea5d]
sql/sql_class.h:2871(THD::set_row_count_func(long long))[0x562bc7940054]
sql/sql_parse.cc:10955(idb_vtable_process(THD*, unsigned long long, Statement*))[0x562bc7942905]
sql/sql_parse.cc:1871(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x562bc7943f28]
sql/sql_parse.cc:1450(do_command(THD*))[0x562bc7a08024]
sql/sql_connect.cc:1403(do_handle_one_connection(CONNECT*))[0x562bc7a080e4]
sql/sql_connect.cc:1311(handle_one_connection)[0x562bc7f701f4]
pthread_create.c:0(start_thread)[0x7fa8b2246dd5]
/lib64/libc.so.6(clone+0x6d)[0x7fa8b01f1ead]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fa1600ab8a0): is an invalid pointer
Connection ID (thread ID): 18
Status: NOT_KILLED
 
Optimizer switch: index_merge=off,index_merge_union=off,index_merge_sort_union=off,index_merge_intersection=off,index_merge_sort_intersection=off,engine_con$
 
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.
 
We think the query pointer is invalid, but we will try to print it anyway.
Query: create temporary table infinidb_vtable.$vtable_18 engine = aria as WITH ^M `CNCTR_F0` AS ^M     (^M     SELECT^M         `MVC`.`CNTRP_EMT_ID`, ^M    $
 
190524 11:15:39 Columnstore: Started; Version: 1.2.3-1
190524 11:15:39 Columnstore: Started; Version: 1.2.3-1
2019-05-24 11:15:39 0 [Note] InnoDB: Using Linux native AIO
2019-05-24 11:15:39 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-05-24 11:15:39 0 [Note] InnoDB: Uses event mutexes
2019-05-24 11:15:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-05-24 11:15:39 0 [Note] InnoDB: Number of pools: 1
2019-05-24 11:15:39 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-05-24 11:15:39 0 [Note] InnoDB: Initializing buffer pool, total size = 25G, instances = 25, chunk size = 128M
2019-05-24 11:15:40 0 [Note] InnoDB: Completed initialization of buffer pool
2019-05-24 11:15:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriorit$
2019-05-24 11:15:40 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=413771860
2019-05-24 11:15:41 0 [Note] InnoDB: Last binlog file '/usr/local/mariadb/columnstore/mysql/db/mysql-bin.000004', position 402490717
2019-05-24 11:15:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-05-24 11:15:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-05-24 11:15:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-05-24 11:15:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-05-24 11:15:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-05-24 11:15:41 0 [Note] InnoDB: Setting file './ibtmp1' size to 200 MB. Physically writing the file full; Please wait ...
2019-05-24 11:15:41 0 [Note] InnoDB: File './ibtmp1' size is now 200 MB.
2019-05-24 11:15:41 0 [Note] InnoDB: 10.3.13 started; log sequence number 413771869; transaction id 981451
2019-05-24 11:15:41 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/mariadb/columnstore/mysql/db/ib_buffer_pool
2019-05-24 11:15:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-05-24 11:15:41 0 [Warning] /usr/local/mariadb/columnstore/mysql//bin/mysqld: unknown variable 'loose-server_audit_syslog_info=columnstore-1'
2019-05-24 11:15:41 0 [Note] Recovering after a crash using /usr/local/mariadb/columnstore/mysql/db/mysql-bin
2019-05-24 11:15:41 0 [Note] Starting crash recovery...
2019-05-24 11:15:41 0 [Note] Crash recovery finished.
2019-05-24 11:15:41 0 [Note] Server socket created on IP: '::'.
2019-05-24 11:15:41 0 [Warning] 'user' entry 'root@mariadbtest01.ufservizi.local' ignored in --skip-name-resolve mode.
2019-05-24 11:15:41 0 [Warning] 'user' entry '@mariadbtest01.ufservizi.local' ignored in --skip-name-resolve mode.
2019-05-24 11:15:41 0 [Warning] 'user' entry 'root@*' ignored in --skip-name-resolve mode.
2019-05-24 11:15:41 0 [Warning] 'user' entry 'root@mariadbtest01' ignored in --skip-name-resolve mode.
2019-05-24 11:15:41 0 [Warning] 'proxies_priv' entry '@% root@mariadbtest01.ufservizi.local' ignored in --skip-name-resolve mode.
2019-05-24 11:15:41 0 [Note] Reading of all Master_info entries succeded
2019-05-24 11:15:41 0 [Note] Added new Master_info '' to hash table
2019-05-24 11:15:41 0 [Note] /usr/local/mariadb/columnstore/mysql//bin/mysqld: ready for connections.
Version: '10.3.13-MariaDB-log'  socket: '/usr/local/mariadb/columnstore/mysql/lib/mysql/mysql.sock'  port: 3306  Columnstore 1.2.3-1
2019-05-24 11:15:41 0 [Note] InnoDB: Buffer pool(s) load completed at 190524 11:15:41



 Comments   
Comment by Alice Sherepa [ 2019-05-24 ]

Is looks like a duplicate of MDEV-15837, that was fixed in 10.3.15.
Please comment here in case the problem will be still reproducible on version >=10.3.15 and the bug will be reopened.

Comment by Matteo Balzarotti [ 2019-05-24 ]

Hello,

please re-open this ticket.
We are experiencing this issue on MariaDB Columnstore (not on pure server version) and the latest version we have installed has embedded 10.3.13

Do you know if exist a newer version of the columnstore we can install?
Please advise
Thanks
Matteo

Comment by David Hall (Inactive) [ 2019-05-24 ]

The fix will be in Columnstore 1.2.4 due out May 31, 2019, but may be running a little late.

Comment by Matteo Balzarotti [ 2019-05-29 ]

Hello David,

we have downloaded and installed on our local machine the develop-1.2 version so now we have Columnstore 1.2.4-1 and MariaDB 10.3.15
We have executed the same query and we got this error:

ERROR 2013 (HY000) at line 1 in file: 'querycog.sql': Lost connection to MySQL server during query

this is the log written into the directory /var/log/messages :

May 29 09:31:21 luraghi-hp kernel: mysqld[31324]: segfault at 300000095 ip 0000558c253d04b3 sp 00007f95478e1d40 error 4 in mysqld[558c24d11000+1204000]

I have attched the Errlog-bug file for your review.
Thanks&Regards
Matteo
Errlog-bug.txt

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