Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Stop cluster via Luci
2. Start cluster via Luci
clurgmgr segfaults on one of my two nodes (the same node each time).
Running 5.1 Beta 1 of all software. The node that crashes appears differently
when the cluster is viewed in Luci. It is grayed out and the listed operations
one can perform is fence or force deletion of node, whereas the other node has
all available options listed in the drop-down.
Which node (node ID 1 or 2) ?
Actually - the easiest thing to do is create /etc/sysconfig/cluster w/ the
This will cause clurgmgrd to produce a core file in the root directory -- could
you attach the core and your cluster configuration?
Created attachment 204601 [details]
core dump of rgmanager
core dump of clurgmgr on cluster startup
(In reply to comment #1)
> Which node (node ID 1 or 2) ?
Wow... thanks for the core. :)
We received a VF_VIEW_FORMED message during for a transaction we did not have
recorded. The transaction was allegedly from node 1, transaction ID 1, and came
immediately after node 2 had received the PORTOPENED status from node 1.
What normally happens is nodes request current states of distributed data when
they access it. This means that it's safe to just throw away messages for
pieces of data we don't have.
This bug is restricted to RHEL5 because RHEL4 doesn't use CMAN's excellent
multicast capabilities. This means that in the same situation on RHEL4, the
socket with the unwanted data would not have been opened at this point.
This is rather easy to fix.
Created attachment 210861 [details]
All the other parts of vf_process_msg() seem to correctly ignore messages for
which there is no key node associated.
Patch in CVS:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.