[MDEV-10710] [Draft] Assertion failed: ! is_set() with status KILL_BAD_DATA Created: 2016-08-31  Updated: 2018-10-29  Resolved: 2018-10-29

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.0, 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-10945 Assertion failed: ! is_set() with sta... Closed

 Description   

2016-08-26  1:44:19 3468 [ERROR] mysqld.exe: Can't find record in '#sql-ed8_b'
2016-08-26  1:44:24 3468 [ERROR] mysqld.exe: Can't find record in '#sql-ed8_b'
Assertion failed: ! is_set(), file E:\buildbot\bbwin1\win-rqg-se\build-debug\sql\sql_error.cc, line 378
R6010
- abort() has been called
160826  1:44:25 [ERROR] mysqld got exception 0x80000003 ;

mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!_wassert()[assert.c:380]
mysqld.exe!Diagnostics_area::set_ok_status()[sql_error.cc:378]
mysqld.exe!my_ok()[sql_class.h:4074]
mysqld.exe!mysql_insert()[sql_insert.cc:1150]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3896]
mysqld.exe!mysql_parse()[sql_parse.cc:7314]
mysqld.exe!dispatch_command()[sql_parse.cc:1489]
mysqld.exe!do_command()[sql_parse.cc:1107]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:238]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x38a54c9630): REPLACE INTO view1 SET field2 = NULL, field4 = 6, field4 = 6 /* QUERY_NO 327057 CON_ID 12 */
Connection ID (thread ID): 12
Status: KILL_BAD_DATA

E:\buildbot\rqg/runall.pl --no-mask --seed=time --threads=5 --duration=600 --queries=100M --reporters=QueryTimeout,Backtrace,ErrorLog,Deadlock,Shutdown --redefine=conf/mariadb/redefine_random_keys.yy --redefine=conf/mariadb/redefine_set_session_vars.yy --validators=TransformerNoComparator --transformers=ConvertSubqueriesToViews,DisableOptimizations,EnableOptimizations,ExecuteAsCTE,ExecuteAsInsertSelect,ExecuteAsPreparedThrice,ExecuteAsSelectItem,ExecuteAsUnion,ExecuteAsUpdateDelete,ExecuteAsView,NullIf,OrderBy,StraightJoin --grammar=conf/optimizer/updateable_views.yy --mysqld=--default-storage-engine=MyISAM --mysqld=--init-file=E:/buildbot/rqg/conf/optimizer/updateable_views.init --mtr-build-thread=300 --basedir1=E:\buildbot\bbwin1\win-rqg-se\build\..\build-debug --vardir1=E:\buildbot\bbwin1\win-rqg-se\build\..\..\..\vardirs\10.1-2641\optim-crash-tests/current1_1
seed => 1472164579



 Comments   
Comment by Elena Stepanova [ 2017-09-01 ]

New occurrence:
http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/443/steps/crash_tests/logs/stdio

Comment by Elena Stepanova [ 2018-10-02 ]

10.1 649451ae0d4

2018-10-03  0:51:49 140435893877504 [Note] Event Scheduler: [rqg@localhost].[testdb_S.e1_2_S] event execution failed.
2018-10-03 00:52:13 7fb9c7917b00  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2018-10-03  0:52:13 140435893877504 [ERROR] InnoDB: Cannot rename file './testdb_N/t1_base1_N.ibd' to './testdb_S/t1_base1_N.ibd'
mysqld: /data/src/10.1/sql/sql_error.cc:378: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `! is_set()' failed.
181003  0:52:14 [ERROR] mysqld got signal 6 ;
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.37-MariaDB-debug
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=8
max_threads=153
thread_count=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467250 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fb9a535a070
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 = 0x7fb9c7917280 thread_stack 0x48400
/data/bld/10.1/bin/mysqld(my_print_stacktrace+0x38)[0x55649b140c4e]
/data/bld/10.1/bin/mysqld(handle_fatal_signal+0x394)[0x55649aadc683]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fb9ca9b70c0]
linux/raise.c:51(__GI_raise)[0x7fb9c8cb0fcf]
stdlib/abort.c:91(__GI_abort)[0x7fb9c8cb23fa]
assert/assert.c:92(__assert_fail_base)[0x7fb9c8ca9e37]
/lib/x86_64-linux-gnu/libc.so.6(+0x2bee2)[0x7fb9c8ca9ee2]
sql/sql_error.cc:383(Diagnostics_area::set_ok_status(unsigned long long, unsigned long long, char const*))[0x55649a874892]
sql/sql_class.h:4184(my_ok(THD*, unsigned long long, unsigned long long, char const*))[0x55649a82d0d7]
sql/sql_table.cc:9420(mysql_alter_table(THD*, char*, char*, HA_CREATE_INFO*, TABLE_LIST*, Alter_info*, unsigned int, st_order*, bool))[0x55649a967ce0]
sql/sql_alter.cc:330(Sql_cmd_alter_table::execute(THD*))[0x55649a9d8185]
sql/sql_parse.cc:5699(mysql_execute_command(THD*))[0x55649a8a6e3f]
sql/sql_parse.cc:7465(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55649a8ab6e3]
sql/sql_parse.cc:1497(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x55649a899f55]
sql/sql_parse.cc:1124(do_command(THD*))[0x55649a898cda]
sql/sql_connect.cc:1330(do_handle_one_connection(THD*))[0x55649a9d36c1]
sql/sql_connect.cc:1243(handle_one_connection)[0x55649a9d3425]
nptl/pthread_create.c:333(start_thread)[0x7fb9ca9ad494]
x86_64/clone.S:99(clone)[0x7fb9c8d6693f]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fb998036088): ALTER TABLE t2 ADD CONSTRAINT CHECK (vcol5 NOT LIKE 6)  /* QNO 6840 CON_ID 14 */
Connection ID (thread ID): 112
Status: KILL_BAD_DATA

Generated at Thu Feb 08 07:44:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.