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.
Previously, Pacemaker's Local Resource Management Daemon (lrmd) used an invalid format string when logging certain rare systemd errors. As a consequence, lrmd could terminate unexpectedly with a segmentation fault. A patch has been applied to fix the format string. As a result, lrmd no longer crashes and logs the aforementioned rare error messages as intended.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0216.html
lrmd still crashes quite consistently in pacemaker-1.1.13-10.el7_2.4.x86_64. Here are just two examples:
/opt/unisys_ccg_gid/cluster_scripts #abrt-cli list --since 1478651531
id b10052d2f8f15628c3343c336a446ed40078a16b
reason: lrmd killed by SIGSEGV
time: Tue 08 Nov 2016 09:33:42 PM PST
cmdline: /usr/libexec/pacemaker/lrmd
package: pacemaker-1.1.13-10.el7_2.4
uid: 0 (root)
count: 1
Directory: /var/spool/abrt/ccpp-2016-11-08-21:33:42-1563
/var/log/cluster #abrt-cli list
id b01b01d4708d3664f696ae9bea577f5c73dab35d
reason: lrmd killed by SIGSEGV
time: Tue 08 Nov 2016 09:36:28 PM PST
cmdline: /usr/libexec/pacemaker/lrmd
package: pacemaker-1.1.13-10.el7_2.4
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/ccpp-2016-11-08-21:36:28-1714
The content of /var/spool/abrt/ccpp-2016-11-08-21:36:28-1714 will be uploaded if the upload works.
(In reply to vlad.socaciu from comment #8)
> lrmd still crashes quite consistently in pacemaker-1.1.13-10.el7_2.4.x86_64.
The core backtrace in the abrt instance shows this is a separate issue, so I have opened Bug 1394068 for it.