[MDEV-14497] rpl.rpl_gtid_reconnect failed in buildbot, lost connection to server Created: 2017-11-24  Updated: 2023-11-29  Resolved: 2023-11-29

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

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Andrei Elkin
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-12496 mtflush thread's hang cause mysqld crash Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10522/steps/mtr_ps/logs/stdio

rpl.rpl_gtid_reconnect 'innodb_plugin,mix' w1 [ fail ]
        Test ended at 2017-11-24 05:48:23
 
CURRENT_TEST: rpl.rpl_gtid_reconnect
mysqltest: In included file "./include/kill_binlog_dump_threads.inc": 
included from /mnt/buildbot/build/mariadb-10.1.30/mysql-test/suite/rpl/t/rpl_gtid_reconnect.test at line 165:
At line 52: query 'let $_tid= `SELECT id FROM information_schema.processlist WHERE command = 'Binlog Dump' LIMIT 1`' failed: 2013: Lost connection to MySQL server during query
 
The result from queries just before the failure was:
< snip >
INSERT INTO t1 VALUES (20);
include/start_slave.inc
SELECT * FROM t1 ORDER BY a;
a
1
2
3
11
12
13
20
*** Test when slave IO thread needs to reconnect in the middle of an event group. ***
include/stop_slave.inc
TRUNCATE t1;
RESET MASTER;
SET GLOBAL gtid_slave_pos= "";
SET GLOBAL debug_dbug= @old_debug;
TRUNCATE t1;
RESET MASTER;
include/kill_binlog_dump_threads.inc
 
More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/log/rpl_gtid_reconnect.log
 
 
Server [mysqld.1 - pid: 31380, winpid: 31380, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
171124  5:48:22 [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.30-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=153
thread_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61851 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.30/sql/mysqld(my_print_stacktrace+0x32)[0x8b3a111]
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(handle_fatal_signal+0x3b0)[0x84e1170]
[0xb7793400]
/lib/i386-linux-gnu/libc.so.6(+0x7b678)[0xb72bc678]
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld[0x8b58572]
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(_db_keyword_+0x79)[0x8b58a6e]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0x1faf5e)[0xb26a8f5e]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0x105d1b)[0xb25b3d1b]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0x113f64)[0xb25c1f64]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xa5d13)[0xb2553d13]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xa6264)[0xb2554264]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xa65be)[0xb25545be]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xace5d)[0xb255ae5d]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xad2f9)[0xb255b2f9]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xad9d2)[0xb255b9d2]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xadd05)[0xb255bd05]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xae62d)[0xb255c62d]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(_Z15buf_flush_batchP10buf_pool_t11buf_flush_tmyP16flush_counters_t+0x13c)[0xb255c9e2]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xaef91)[0xb255cf91]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xafabe)[0xb255dabe]
/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/plugins/ha_innodb.so(+0xb092a)[0xb255e92a]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb751bd4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb732bace]
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



 Comments   
Comment by Andrei Elkin [ 2017-12-18 ]

The stack indicates the immediate issue must be in Innodb, and
possibly in page flusher which is currently troublesome:

_Marko:
@andrei sorry, I have no idea. it is something in page flush. innodb_use_mtflush maybe?
@andrei we know that the 10.1 multi-threaded flushing is buggy.

I am relating, not duplicating though before I've tried by lack to reproduce, to the aforesaid one._

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