[MDEV-22455] Server crashes in Table_map_log_event, binlog.binlog_invalid_read_in_rotate failed in buildbot Created: 2020-05-04  Updated: 2020-10-06  Resolved: 2020-09-17

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.1.48, 10.2.35, 10.3.26, 10.4.16, 10.5.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sujatha Sivakumar (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Attachments: Text File stdio.txt    

 Description   

binlog.binlog_invalid_read_in_rotate 'disable_checksum,innodb,stmt' w3 [ fail ]
        Test ended at 2020-02-10 20:10:04
 
CURRENT_TEST: binlog.binlog_invalid_read_in_rotate
mysqltest: At line 47: query 'SHOW BINLOG EVENTS FROM $pos' failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 0...
 
The result from queries just before the failure was:
RESET MASTER;
call mtr.add_suppression("Error in Log_event::read_log_event*");
call mtr.add_suppression("Replication event checksum verification failed while reading from a log file*");
DROP TABLE /*! IF EXISTS*/ t1;
Warnings:
Note	1051	Unknown table 'test.t1'
CREATE TABLE `t1` (
`col_int` int,
pk integer auto_increment,
`col_char_12_key` char(12),
`col_int_key` int,
`col_char_12` char(12),
primary key (pk),
key (`col_char_12_key` ),
key (`col_int_key` )) ENGINE=InnoDB;
INSERT /*! IGNORE */ INTO t1 VALUES  (183173120, NULL, 'abcd', 1, 'efghijk'),  (1, NULL, 'lmno', 2, 'p');
ALTER TABLE `t1` ENABLE KEYS;

10.2 f6663bfbd3f1dd321cd7d53291e3fa08

200210 20:10:02 [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.2.32-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
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 = 61894 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0xb0005f28
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 = 0xac7bd21c thread_stack 0x49000
/mnt/buildbot/build/mariadb-10.2.32/sql/mysqld(my_print_stacktrace+0x33)[0x80d3c4c5]
/mnt/buildbot/build/mariadb-10.2.32/sql/mysqld(handle_fatal_signal+0x388)[0x80634560]
addr2line: '': No such file
[0xb77cfc14]
/lib/i386-linux-gnu/libc.so.6(+0x127031)[0xb71a9031]
sql/log_event.cc:12057(Table_map_log_event::Table_map_log_event(char const*, unsigned int, Format_description_log_event const*))[0x807614e3]
sql/log_event.cc:2205(Log_event::read_log_event(char const*, unsigned int, char const**, Format_description_log_event const*, char))[0x8074cae7]
sql/log_event.cc:1929(Log_event::read_log_event(st_io_cache*, st_mysql_mutex*, Format_description_log_event const*, char))[0x8074c04d]
sql/sql_repl.cc:4003(mysql_show_binlog_events(THD*))[0x80407750]
sql/sql_parse.cc:3643(mysql_execute_command(THD*))[0x803cf2e8]
sql/sql_parse.cc:7739(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x803dc969]
sql/sql_parse.cc:1831(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x803ca0eb]
sql/sql_parse.cc:1385(do_command(THD*))[0x803c88f4]
sql/sql_connect.cc:1336(do_handle_one_connection(CONNECT*))[0x8050aead]
sql/sql_connect.cc:1241(handle_one_connection)[0x8050ac0d]
perfschema/pfs.cc:1869(pfs_spawn_thread)[0x80836012]
/lib/i386-linux-gnu/libpthread.so.0(+0x62b5)[0xb74282b5]
/lib/i386-linux-gnu/libc.so.6(clone+0x6e)[0xb716916e]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xb0014678): SHOW BINLOG EVENTS FROM 251
Connection ID (thread ID): 10
Status: NOT_KILLED

All threads and the rest of the test output is attached.

According to the cross-reference, the failure was observed several times on 10.1 and 10.2 main trees, as well as 10.3- and 10.4-based development trees, the most recent occurrence as of this moment was on April 25.



 Comments   
Comment by Sujatha Sivakumar (Inactive) [ 2020-09-17 ]

The test issue is addressed as part of MDEV-21839.

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