[MDEV-23832] Crash at startup in Log_event::read_log_event() Created: 2020-09-28  Updated: 2021-04-19  Resolved: 2020-10-07

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.3.18
Fix Version/s: 10.1.48, 10.2.35, 10.3.26, 10.4.16, 10.5.7

Type: Bug Priority: Major
Reporter: Valerii Kravchuk Assignee: Andrei Elkin
Resolution: Fixed Votes: 0
Labels: checksum, recovery


 Description   

Server crashes with the following backtrace at startuip:

...
2020-09-28 18:37:47 0 [Note] Starting ack receiver thread
200928 18:37:48 [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.3.18-MariaDB-log
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=0
max_threads=1002
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2268426 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55d2563f106e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55d255e8e11f]
/lib64/libpthread.so.0(+0xf680)[0x7f6522495680]
/usr/sbin/mysqld(_ZN9Log_event14read_log_eventEPKcjPS1_PK28Format_description_log_eventc+0xfc)[0x55d255f9381c]
/usr/sbin/mysqld(_ZN9Log_event14read_log_eventEP11st_io_cachePK28Format_description_log_eventc+0xcf)[0x55d255f9433f]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG7recoverEP11st_log_infoPKcP11st_io_cacheP28Format_description_log_eventb+0x17a)[0x55d255f7693a]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG18do_binlog_recoveryEPKcb+0x2ea)[0x55d255f771ba]
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc+0x3a)[0x55d255f7acda]
/usr/sbin/mysqld(+0x4f93ae)[0x55d255bf83ae]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4ae)[0x55d255bfe0be]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f65207553d5]
/usr/sbin/mysqld(+0x4f2add)[0x55d255bf1add]
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 [ 2020-09-30 ]

Howdy, Sujatha!

The patch is pretty short and its logics follows 7332af49e4ce ideas, in a way
the latter commit did not cover the current issue of THD object unavailable.

Cheers,

Andrei

Comment by Sujatha Sivakumar (Inactive) [ 2020-10-01 ]

Code changes look good to my knowledge.

Please replace S/inproper/improper in the commit message.

Comment by Andrei Elkin [ 2020-10-07 ]

At merging to 10.4 the new test result file needs
+# restart: --master_verify_checksum=ON --debug_dbug=+d,corrupt_read_log_event_char
that mtr run will hint on.

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