[MDEV-14546] MariaDB server crashed Created: 2017-11-30  Updated: 2018-01-08

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.2.10
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Michael Graf Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: crash
Environment:

Windows Server 2016 Datacenter
RAM: 32 GB


Attachments: File mysqld.err    

 Description   

The excerpt from the MariaDB errorlog is appended.



 Comments   
Comment by Elena Stepanova [ 2017-11-30 ]

From the attached error log

2017-11-28 12:54:01 14328 [ERROR] Got error 134 when reading table '.\zisarchdata\numeric_archive_data_14_106152_0'
2017-11-28 12:54:01 14328 [ERROR] mysqld.exe: Kann Datensatz in 'numeric_archive_data_14_106152_0' nicht finden
171128 12:54:01 [ERROR] mysqld got exception 0xc0000005 ;
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.2.10-MariaDB
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=147
max_threads=302
thread_count=153
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1373599 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x17ff74e8cf8
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...
mysqld.exe!?next_partition@Frame_unbounded_preceding@@UEAAX_K@Z()
mysqld.exe!mysql_num_fields()
mysqld.exe!mysql_num_fields()
mysqld.exe!mysql_num_fields()
mysqld.exe!strmov()
mysqld.exe!?ha_index_last@handler@@QEAAHPEAE@Z()
mysqld.exe!?join_read_key2@@YAHPEAVTHD@@PEAUst_join_table@@PEAUTABLE@@PEAUst_table_ref@@@Z()
mysqld.exe!?sub_select@@YA?AW4enum_nested_loop_state@@PEAVJOIN@@PEAUst_join_table@@_N@Z()
mysqld.exe!?disjoin@?$List@VItem@@@@QEAAXPEAV1@@Z()
mysqld.exe!?exec_inner@JOIN@@QEAAXXZ()
mysqld.exe!?exec@JOIN@@QEAAXXZ()
mysqld.exe!?mysql_select@@YA_NPEAVTHD@@PEAUTABLE_LIST@@IAEAV?$List@VItem@@@@PEAVItem@@IPEAUst_order@@434_KPEAVselect_result@@PEAVst_select_lex_unit@@PEAVst_select_lex@@@Z()
mysqld.exe!?handle_select@@YA_NPEAVTHD@@PEAULEX@@PEAVselect_result@@K@Z()
mysqld.exe!?execute_init_command@@YAXPEAVTHD@@PEAUst_mysql_lex_string@@PEAUst_mysql_rwlock@@@Z()
mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@@Z()
mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEADIPEAVParser_state@@_N3@Z()
mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI_N3@Z()
mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
mysqld.exe!?do_handle_one_connection@@YAXPEAVCONNECT@@@Z()
mysqld.exe!handle_one_connection()
mysqld.exe!pthread_join()
mysqld.exe!?traverse_cond@Item@@UEAAXP6AXPEBV1@PEAX@Z1W4traverse_order@1@@Z()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x17ff773cff0): SELECT nad_id,nad_unixtime,nad_state,nad_value,nad_text FROM numeric_archive_data_14_106055_0 ORDER BY nad_unixtime DESC LIMIT 0,1
Connection ID (thread ID): 348
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

Comment by Elena Stepanova [ 2017-12-01 ]

Could you please provide the output of

SHOW CREATE TABLE numeric_archive_data_14_106055_0;
SHOW INDEX IN numeric_archive_data_14_106055_0;

and attach your ini file(s) (or, if you already provided them in other reports, point at the one which has the correct config file)?

Comment by Michael Graf [ 2017-12-05 ]

SHOW CREATE TABLE numeric_archive_data_14_106055_0;
 
CREATE TABLE `numeric_archive_data_14_106055_0` (
  `nad_id` bigint(20) NOT NULL AUTO_INCREMENT,
  `nad_unixtime` bigint(20) NOT NULL,
  `nad_value` double DEFAULT NULL,
  `nad_text` text NOT NULL,
  `nad_state` tinyint(3) unsigned NOT NULL,
  PRIMARY KEY (`nad_id`),
  UNIQUE KEY `uidx` (`nad_unixtime`,`nad_id`)
) ENGINE=Aria AUTO_INCREMENT=279036 DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1

SHOW INDEX IN numeric_archive_data_14_106055_0;
# Table, Non_unique, Key_name, Seq_in_index, Column_name, Collation, Cardinality, Sub_part, Packed, Null, Index_type, Comment, Index_comment
'numeric_archive_data_14_106055_0', '0', 'PRIMARY', '1', 'nad_id', 'A', '69360', NULL, NULL, '', 'BTREE', '', ''
'numeric_archive_data_14_106055_0', '0', 'uidx', '1', 'nad_unixtime', 'A', '69360', NULL, NULL, '', 'BTREE', '', ''
'numeric_archive_data_14_106055_0', '0', 'uidx', '2', 'nad_id', 'A', '69360', NULL, NULL, '', 'BTREE', '', ''

Comment by Elena Stepanova [ 2018-01-02 ]

Was it a one-time occurrence, or do you keep getting the failure?
It seems suspicious that you got errors about a different table the same second when the crash occurred

2017-11-28 12:54:01 14328 [ERROR] Got error 134 when reading table '.\zisarchdata\numeric_archive_data_14_106152_0'
2017-11-28 12:54:01 14328 [ERROR] mysqld.exe: Kann Datensatz in 'numeric_archive_data_14_106152_0' nicht finden

Did you try to run check/repair on both tables to see if anything is wrong with them?

Comment by Michael Graf [ 2018-01-02 ]

>Was it a one-time occurrence, or do you keep getting the failure?
Until now it's a one-time occurrence.

>It seems suspicious that you got errors about a different table the same second when the crash occurred
Repairs on tables are executed in parallel by the handler which uses these tables.

Maybe this error has the same source as https://jira.mariadb.org/browse/MDEV-14646.

Comment by Elena Stepanova [ 2018-01-07 ]

The attached fragment of the error log starts from those error messages. Were there more earlier, at the time of the crash or shortly before?

Comment by Michael Graf [ 2018-01-08 ]

No, there were no error messages before.

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