[MDEV-26295] Instance Crash got signal 11 segfault at 55 error 4 Created: 2021-08-02  Updated: 2023-04-17  Resolved: 2023-04-17

Status: Closed
Project: MariaDB Server
Component/s: Galera, Server
Affects Version/s: 10.5.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: William Wong Assignee: Jan Lindström
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

Redhat 7 on VMware


 Description   

one of our Galera DB node got instance crash twice with signal 11 last week

Both case got signal 11.
From /var/log/messages, got segfault at 55 error 4 errors
segfault at 55 ip 00007f57ca8e60f8 sp 00007f55a3c2e5e0 error 4 in libgcc_s-4.8.5-20150702.so.1[7f57ca8d7000+15000]

In both cases, Galera used IST to recovery the DB node automatically.

2021-07-27 case:
DB error
210727 19:21:23 [ERROR] mysqld got signal 11 ;

/var/log/message
Jul 27 19:21:23 t1vdbs-bdeshub-sitdb1-1-01 kernel: mariadbd[90957]: segfault at 55 ip 00007f57ca8e60f8 sp 00007f55a3c2e5e0 error 4 in libgcc_s-4.8.5-20150702.so.1[7f57ca8d7000+15000]

2021-07-30 case:
DB error
210730 20:11:23 [ERROR] mysqld got signal 11 ;

/var/log/messages:
Jul 30 20:11:23 t1vdbs-bdeshub-sitdb1-1-01 kernel: mariadbd[51024]: segfault at 55 ip 00007f53788830f8 sp 00007f515d0b85e0 error 4 in libgcc_s-4.8.5-20150702.so.1[7f5378874000+15000]

 Comments   
Comment by Jan Lindström [ 2023-04-11 ]

frelist Can you try with more recent version of MariaDB server and Galera library. If this issue reproduces please provide full unedited error log, opened stack trace and node configuration.

Comment by William Wong [ 2023-04-16 ]

@janlindstrom we upgrade all DB to MariaDB 10.6.10 Dec-2022. This problem only happened twice but no more afterward. If no idea of the reason, it is ok to close it.

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