[MDEV-31012] rpl.rpl_domain_id_filter_restart sometimes fails in BB ASAN build Created: 2023-04-05  Updated: 2023-11-28

Status: Open
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0
Fix Version/s: 10.4, 10.5, 10.6, 10.11, 11.0

Type: Bug Priority: Major
Reporter: Angelique Sklavounos (Inactive) Assignee: Brandon Nesterenko
Resolution: Unresolved Votes: 0
Labels: None

Attachments: File core.gz     File mysqld.1.err.13     File mysqld.2.err.13    

 Description   

https://buildbot.mariadb.org/#/builders/168/builds/20243

10.5 3261a78ea

rpl.rpl_domain_id_filter_restart 'row'   w13 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2023-04-04 05:56:10
line
Attempting backtrace. You can use the following information to find out
^ Found warnings in /buildbot/amd64-ubuntu-1804-clang10-asan/build/mysql-test/var/13/log/mysqld.2.err
ok
 - found 'core' (0/1)
Core generated by '/buildbot/amd64-ubuntu-1804-clang10-asan/build/sql/mariadbd'
Output from gdb follows. The first stack trace is from the failing thread.
The following stack traces are from all threads (so the failing one is
duplicated).
--------------------------
BFD: warning: /buildbot/amd64-ubuntu-1804-clang10-asan/build/mysql-test/var/13/log/rpl.rpl_domain_id_filter_restart-row/mysqld.2/data/core is truncated: expected core file size >= 590745600, found: 38400000
[New LWP 66210]
[New LWP 66259]
[New LWP 66337]
Cannot access memory at address 0x7fce9ad24148
Cannot access memory at address 0x7fce9ad24140
Failed to read a valid object file image from memory.
Core was generated by `/buildbot/amd64-ubuntu-1804-clang10-asan/build/sql/mariadbd --defaults-group-su'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fce997f83b1 in ?? ()
[Current thread is 1 (LWP 66210)]
#0  0x00007fce997f83b1 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffcb9df70e0
 
Thread 3 (LWP 66337):
#0  0x00007fce98a8b38c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fce8a1f1e90
 
Thread 2 (LWP 66259):
#0  0x00007fce997f7065 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fce9531f8f0
 
Thread 1 (LWP 66210):
#0  0x00007fce997f83b1 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffcb9df70e0
 
Compressed file /buildbot/amd64-ubuntu-1804-clang10-asan/build/mysql-test/var/13/log/rpl.rpl_domain_id_filter_restart-row/mysqld.2/data/core
 - saving '/buildbot/amd64-ubuntu-1804-clang10-asan/build/mysql-test/var/13/log/rpl.rpl_domain_id_filter_restart-row/' to '/buildbot/amd64-ubuntu-1804-clang10-asan/build/mysql-test/var/log/rpl.rpl_domain_id_filter_restart-row/'

Core file and error logs attached. The replica error log shows:

230404  5:52:35 [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.5.20-MariaDB-debug-log source revision: 3261a78ea172a77fec113107ef35f218b9228b66
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=4
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63762 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 0x100000
mysys/my_addr_resolve.c:300(my_addr_resolve)[0x7c0e6b]
include/buf0types.h:159(buf_pool_t::insert_into_flush_list(buf_block_t*, unsigned long))[0x278929e]
/buildbot/amd64-ubuntu-1804-clang10-asan/build/sql/mariadbd(handle_fatal_signal+0x662)[0x125d802]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7fce997fb980]
mysys/hash.c:801(my_hash_iterate)[0x2719d55]
mysys/thr_mutex.c:663(safe_mutex_free_deadlock_data)[0x2798a59]
mysys/thr_mutex.c:610(safe_mutex_destroy)[0x279881a]
/buildbot/amd64-ubuntu-1804-clang10-asan/build/sql/mariadbd(lf_alloc_destroy+0xad)[0x27a256d]
mysys/lf_hash.cc:395(lf_hash_destroy)[0x27a39c2]
psi/mysql_thread.h:717(inline_mysql_mutex_destroy(st_mysql_mutex*, char const*, unsigned int))[0x10cb185]
sql/mysqld.cc:2002(clean_up(bool))[0x836a6c]
sql/mysqld.cc:5731(mysqld_main(int, char**))[0x83d89f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fce98a6cbf7]
/buildbot/amd64-ubuntu-1804-clang10-asan/build/sql/mariadbd(_start+0x2a)[0x789e4a]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /dev/shm/var_auto_W4J1/13/mysqld.2/data
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        unlimited            unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             unlimited            unlimited            processes 
Max open files            1024                 1024                 files     
Max locked memory         51200000             51200000             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       63857                63857                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: core
 
Kernel version: Linux version 5.8.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.8.10-1~bpo10+1 (2020-09-26)


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