Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.5.8
-
None
-
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]