[MCOL-668] mysqld got signal 11 Created: 2017-04-19  Updated: 2017-06-03  Resolved: 2017-06-03

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.0.8
Fix Version/s: Icebox

Type: Bug Priority: Blocker
Reporter: Yanghan Assignee: Andrew Hutchings (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

centos 7 x86_64



 Description   

170419 9:24:51 [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.1.22-MariaDB
key_buffer_size=536870912
read_buffer_size=4194304
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1780777 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f4b62d5e8c8
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 = 0x7f4b2470cd98 thread_stack 0x80000
/usr/local/mariadb/columnstore/mysql//bin/mysqld(my_print_stacktrace+0x29)[0x7f4b6064cf09]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(handle_fatal_signal+0x305)[0x7f4b60212c65]
/lib64/libpthread.so.0(+0xf370)[0x7f4b5f864370]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(_Z18idb_vtable_processP3THDyP9Statement+0x85a)[0x7f4b600c2fca]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x2a3)[0x7f4b600d59a3]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(ZN18Prepared_statement12execute_loopEP6StringbPhS2+0xa6)[0x7f4b600d5e66]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0xc8)[0x7f4b600d6078]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xb66)[0x7f4b600c6d56]
mysys/stacktrace.c:268(my_print_stacktrace)[0x7f4b600c899c]
/usr/local/mariadb/columnstore/mysql//bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c4)[0x7f4b6017f6c4]
sql/sql_string.h:182(String::c_ptr())[0x7f4b6017f757]
sql/sql_parse.cc:1454(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x7f4b5f85cdc5]
/lib64/libc.so.6(clone+0x6d)[0x7f4b5da9373d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f4aec05dd58): is an invalid pointer
Connection ID (thread ID): 3
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_condition_pushdown=off,index_condition_pushdown=off,derived_merge=off,derived_with_keys=off,firstmatch=off,loosescan=off,materialization=off,in_to_exists=on,semijoin=off,partial_match_rowid_merge=off,partial_match_table_scan=off,subquery_cache=off,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=off,semijoin_with_cache=off,join_cache_incremental=off,join_cache_hashed=off,join_cache_bka=off,optimize_join_buffer_size=off,table_elimination=off,extended_keys=off,exists_to_in=on,orderby_uses_equalities=off

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: INSERT INTO `datawarehouse`.`zs_yjsf` (`ZSUUID`,`YZPZXH`,`YZPZMXXH`,`GLYZPZMXXH`,`YZPZZL_DM`,`DJXH`,`ZSDLFS_DM`,`NSSBRQ`,`YZFSRQ`,`YZGSRQ`,`KJJZRQ`,`YZCLRQ`,`CZLX_DM`,`TZLX_DM`,`SKCLLX_DM`,`SBSX_DM_1`,`KSSL`,`JSYJ`,`SL_1`,`YNSE`,`JMSE`,`YJSE`,`YBTSE`,`HY_DM`,`ZSXM_DM`,`ZSPM_DM`,`SKSSQQ`,`SKSSQZ`,`JKQX`,`YJKQX`,`CBSX_DM`,`DJZCLX_DM`,`DWLSGX_DM`,`JDXZ_DM`,`SSGLY_DM`,`KJDJXH`,`ZSFS_DM`,`SKZL_DM`,`SKSX_DM`,`YJSKZT_DM`,`SBFS_DM`,`ZSZM_DM`,`BZ`,`SYBH_1`,`SKSSSWJG_DM`,`ZGSWSKFJ_DM`,`ZSSWJG_DM`,`LRRQ`,`LRR_DM`,`XGRQ`,`XGR_DM`,`SJGSDQ`,`QRMXUUID`,`SJTB_SJ`,`RKRQ`,`YYZPZMXXH`,`KMBLGKTSGZ_DM`,`JZJTSKBZ`) VALUES ('23310215112710216387620000000002',2.3301010810001633e18,2,0,'BDA0619903',1.0123301000001055e19,'0','2015-11-27 10:06:55.000000','2015-11-27 10:06:55.000000','2015-11-27 10:06:55.000000','2015-11-27 10:06:55.000000','2016-02-15 00:00:00.000000','10','1','1','11',NULL,10221189,0.03,306635.67,0,0,306635.67,'7090','10119','101191111','2014-07-24 00:00:00.000000','2014-07-24 00:00:00.000000','2016-05-25 00:00:00.000000','2016-05-25 00:00:00.000000',NULL,'110','90','330102089',NULL,NULL,'100','10','0101','21','10',NULL,NULL,NULL,'23301010000','23301010030','23301010000','2015-11-27 10:06:55.000000','23301012636',NULL,NULL,'23301010000',NULL,'2016-09-28 04:18:29.000000','2016-02-16 00:00:00.000000',NULL,NULL,NULL)



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2017-04-24 ]

Hi,

Can you please send us the schema for `datawarehouse`.`zs_yjsf` so we can attempt to reproduce this?

Comment by David Thompson (Inactive) [ 2017-06-03 ]

Please re-open if you provide the schema / test case.

Generated at Thu Feb 08 02:22:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.