[MDEV-21235] multi_source.load_data failed in buildbot with SIGABRT Created: 2019-12-05  Updated: 2023-11-29  Resolved: 2023-11-29

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

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


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-aarch64/builds/6229/steps/mtr/logs/stdio

10.3 5d3bd2b7

multi_source.load_data                   w2 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2019-11-06 00:05:41
line
Attempting backtrace. You can use the following information to find out
^ Found warnings in /dev/shm/var/2/log/mysqld.3.err
ok

2019-11-06  0:05:41 7 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16040',replication started in log 'FIRST' at position 4
2019-11-06  0:05:41 8 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './mysqld-relay-bin.000001' position: 4
2019-11-06  0:05:41 6 [Note] Master 'master2': Error reading relay log event: slave SQL thread was killed
2019-11-06  0:05:41 6 [Note] Master 'master2': Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 921
2019-11-06  0:05:41 5 [Note] Master 'master2': Slave I/O thread exiting, read up to log 'master-bin.000001', position 921
191106  0:05:41 [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.3.20-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=4
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63204 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...
2019-11-06  0:05:41 8 [Note] Error reading relay log event: slave SQL thread was killed
2019-11-06  0:05:41 8 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 921
2019-11-06  0:05:41 7 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 921
stack_bottom = 0x0 thread_stack 0x49000
2019-11-06  0:05:41 4 [Note] Deleted Master_info file '/dev/shm/var/2/mysqld.3/data/master.info'.
2019-11-06  0:05:41 4 [Note] Deleted Master_info file '/dev/shm/var/2/mysqld.3/data/relay-log.info'.
2019-11-06  0:05:41 4 [Note] Deleted Master_info file '/dev/shm/var/2/mysqld.3/data/master-master2.info'.
2019-11-06  0:05:41 4 [Note] Deleted Master_info file '/dev/shm/var/2/mysqld.3/data/relay-log-master2.info'.
/usr/sbin/mysqld(my_print_stacktrace+0x3c)[0xaaaac6ae9c60]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0xaaaac65c385c]
CURRENT_TEST: multi_source.load_data


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