[MDEV-24475] galera.MDEV-24063 MTR failed: inline_mysql_socket_recv: Assertion `mysql_socket.fd != -1' failed Created: 2020-12-22  Updated: 2023-04-11

Status: Open
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.4.18, 10.5.9, 10.6.0
Fix Version/s: 10.4, 10.5

Type: Bug Priority: Major
Reporter: Stepan Patryshev (Inactive) Assignee: Julius Goryavsky
Resolution: Unresolved Votes: 0
Labels: None
Environment:

kvm-rpm-centos74-amd64-debug


Attachments: Zip Archive MDEV-24475_104_logs_201215.zip    
Issue Links:
Blocks
blocks MDEV-22122 Galera test failures on 10.5 Open
Relates
relates to MDEV-23609 galera_sr.galera_sr_cc_master MTR fai... Closed
relates to MDEV-24063 Assertion during graceful shutdown wi... Closed

 Description   

galera.MDEV-24063 failed on BB 10.4 CS, BB 10.5 CS and BB 10.6 CS: "inline_mysql_socket_recv: Assertion `mysql_socket.fd != -1' failed".

stdio.log:

10.4.18, d4c35fb21b11f05b317d2e98de42f9a2cab46c27, kvm-rpm-centos74-amd64-debug

galera.MDEV-24063 'innodb'               w2 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2020-12-15 06:34:24
line
mysqld: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.18/include/mysql/psi/mysql_socket.h:785: inline_mysql_socket_recv: Assertion `mysql_socket.fd != -1' failed.
Attempting backtrace. You can use the following information to find out
^ Found warnings in /dev/shm/var/2/log/mysqld.2.err
ok
 
 - found 'core.3508' (0/0)
 
Trying 'dbx' to get a backtrace
gdb not found, cannot get the stack trace
 
Trying 'lldb' to get a backtrace from coredump /dev/shm/var/2/log/galera.MDEV-24063-innodb/mysqld.2/data/core.3508
 - deleting it, already saved 0
 - saving '/dev/shm/var/2/log/galera.MDEV-24063-innodb/' to '/dev/shm/var/log/galera.MDEV-24063-innodb/'
 
Retrying test galera.MDEV-24063, attempt(2/3)...
 
worker[2] > Restart  - not started
worker[2] > Restart  - not started

Note: It is reproduced only on kvm-rpm-centos74-amd64-debug.

Server logs.


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