[MDEV-20960] rpl.rpl_cant_read_event_incident failed in buildbot with backtrace upon shutdown Created: 2019-11-03  Updated: 2019-11-03

Status: Open
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.4
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Strangely looking failure: it doesn't appear to be a hang on shutdown: according to timestamps normal shutdown started, immediately followed by SIGABRT, and then by "shutdown complete".

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-aarch64/builds/6001

10.4 b05be3ef8c8668ddbcbe8e1c08dcd4fc

pl.rpl_cant_read_event_incident 'mix'   w4 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2019-10-11 08:16:54
line
Attempting backtrace. You can use the following information to find out
^ Found warnings in /dev/shm/var/4/log/mysqld.1.err
ok

2019-10-11  8:16:50 0 [Note] /usr/sbin/mysqld (initiated by: root[root] @ localhost [127.0.0.1]): Normal shutdown
2019-10-11  8:16:50 0 [Note] Event Scheduler: Purging the queue. 0 events
191011  8:16:50 [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.4.9-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=6
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 = 63520 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 0x49000
2019-10-11  8:16:50 0 [Note] /usr/sbin/mysqld: Shutdown complete


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