[MDEV-14364] parts.partition_alter2_2_maria fails in buildbot, Lost connection to MySQL server during query Created: 2017-11-10  Updated: 2023-11-29  Resolved: 2023-11-29

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

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2-big/builds/1245/steps/test_1/logs/stdio

parts.partition_alter2_2_maria           w1 [ fail ]
        Test ended at 2017-09-28 04:46:23
 
CURRENT_TEST: parts.partition_alter2_2_maria
mysqltest: In included file "./suite/parts/inc/partition_check.inc": 
included from ./suite/parts/inc/partition_alter_1.inc at line 71:
included from ./suite/parts/inc/partition_alter_13.inc at line 125:
included from ./suite/parts/inc/partition_alter2_2.inc at line 144:
included from /mnt/buildbot/build/mariadb-10.1.28/mysql-test/suite/parts/t/partition_alter2_2_maria.test at line 80:
At line 825: query 'INSERT INTO t1 (f_int1, f_int2, f_char1, f_char2, f_charbig)
SELECT f_int1, f_int1, '', '', 'was inserted'
FROM t0_template source_tab
WHERE f_int1 BETWEEN @max_row_div4 AND @max_row_div2 + @max_row_div4' failed: 2013: Lost connection to MySQL server during query
 
The result from queries just before the failure was:
< snip >
SELECT f_int1, f_int1, '', '', 'was inserted'
FROM t0_template source_tab
WHERE f_int1 BETWEEN @max_row_div4 AND @max_row_div2 + @max_row_div4;
	
# check transactions-1 success: 	1
COMMIT WORK;
	
# check transactions-2 success: 	1
ROLLBACK WORK;
	
# check transactions-3 success: 	1
DELETE FROM t1 WHERE f_charbig = 'was inserted';
COMMIT WORK;
ROLLBACK WORK;
	
# check transactions-4 success: 	1
INSERT INTO t1 (f_int1, f_int2, f_char1, f_char2, f_charbig)
SELECT f_int1, f_int1, '', '', 'was inserted'
FROM t0_template source_tab
WHERE f_int1 BETWEEN @max_row_div4 AND @max_row_div2 + @max_row_div4;
 
More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.1.28/mysql-test/var/1/log/partition_alter2_2_maria.log
 
 
Server [mysqld.1 - pid: 26977, winpid: 26977, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
mysqld: /home/buildbot/buildbot/build/mariadb-10.1.28/storage/maria/ma_bitmap.c:2933: flush_log_for_bitmap: Assertion `share->now_transactional' failed.
170928  4:46:18 [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.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
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 = 61836 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0
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 = 0x0 thread_stack 0x48400
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld(my_print_stacktrace+0x32)[0x8b343b1]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld(handle_fatal_signal+0x3b0)[0x84dc12c]
[0xe62400]
[0xe62416]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0x4e41ef]
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0x4e7835]
/lib/i386-linux-gnu/libc.so.6(+0x27095)[0x4dd095]
/lib/i386-linux-gnu/libc.so.6(+0x27147)[0x4dd147]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x87447f6]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86f3c05]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86fd5ff]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86fde21]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86fe193]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x873f78a]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x8700a13]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86ff22b]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86ff026]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86ffd53]
/mnt/buildbot/build/mariadb-10.1.28/sql/mysqld[0x86ae228]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xd7ed4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x5a0ace]
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.
Writing a core file
----------SERVER LOG END-------------
 
 
 - skipping '/mnt/buildbot/build/mariadb-10.1.28/mysql-test/var/1/log/parts.partition_alter2_2_maria/'
 
Retrying test parts.partition_alter2_2_maria, attempt(2/3)...
 
worker[1] > Restart  - not started


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