Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1837130 [details]
Excerpt from /var/log/mariadb/mariadb.log

Description of problem:
I noticed this morning that one of the nodes of my MariaDB Galera cluster had crashed. Systemd automatically restarted the service after five seconds. This might have happened before, but I only set up monitoring for these events around two weeks back.

Version-Release number of selected component (if applicable):
mariadb 3:10.3.28-1.module+el8.3.0+10472+7adc332a

How reproducible:
I haven't been able to reproduce this issue.

Actual results:
mysqld crashed with [ERROR] WSREP: invalid state ROLLED_BACK (FATAL) at galera/src/replicator_smm.cpp:abort_trx():735

Additional info:
The upstream bug report is here: https://jira.mariadb.org/browse/MDEV-25114

Imre, thanks for the report. The upstream report looks like it is now fixed with 10.3.32, so it will eventually get to the RHEL, together with the next update to the newer upstream version. Did you have chance to test the upstream version by any chance whether it fixes your issue?

Hi Honza, that's good to know. Any idea when the update will arrive in RHEL repositories? Will it be with the 8.6 release?
I haven't tested the upstream version and will probably just update whenever it gets to RHEL. So far this has mostly been a theoretical issue for us (we've found no evidence of data loss, the crash only occurred once or twice since, and customers are still happy). I can't reproduce the issue so I wouldn't be able to tell you if 10.3.32 "fixed" the issue for us or anything.