Red Hat Bugzilla – Bug 444751
CMAN: Initiating transition, generation 18
Last modified: 2010-10-22 20:37:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20080325 Fedora/22.214.171.124-1.fc8 Firefox/126.96.36.199
Description of problem:
RHEL4u6 cluster suite with clvmd/gfs will randomly get messages like this below
over and over:
Mar 29 13:04:37 su010033 kernel: CMAN: Initiating transition, generation 18
I have seen this issue in two cases. In both cases they say the network is fine.
They have verified their network infustructure.
It appears that CMAN cannot talk with any of the other nodes.
The issue is random and I have not found reproducer steps.
I will attach sosreports from a case that is in dev enviroment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The issue is random, have not found reproducer steps.
cluster will hang until it is rebooted/restarted.
That there should be at most 1 "transition restart" messages.
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
Created attachment 305142 [details]
Here's the patch I'm testing. Do NOT apply this to the RHEL4.6 code as it will
break things even more. It should be applied to the RHEL4 or RHEL47 branches.
Created attachment 305228 [details]
Program to send a message to all nodes
It occurs to me that there is an obvious workaround for those people who don't
want to wait for a patched kernel or a reboot, and that is to initiate some
CMAN message activity every so often. GFS mount/umount requests do this, as do
several clvmd requests. Here is a small program that could be run from crontab
that will send a single message to all nodes in a cluster to keep the ack
I do strongly recommend upgrading to 4.7 along with this though.
Added to the RHEL4 branch:
Author: Christine Caulfield <email@example.com>
Date: Tue May 13 16:37:11 2008 +0100
Requesting 4.6.z stream.
*** Bug 449961 has been marked as a duplicate of this bug. ***
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.