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

Bug 444751

Summary: CMAN: Initiating transition, generation 18
Product: [Retired] Red Hat Cluster Suite Reporter: Shane Bradley <sbradley>
Component: cman-kernelAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4CC: cluster-maint, edamato, jplans, mceci, tao, tjaszowski
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: GSSApproved
Fixed In Version: RHBA-2008-0800 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-25 19:09:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 447955    
Attachments:
Description Flags
Patch
none
Program to send a message to all nodes none

Description Shane Bradley 2008-04-30 14:13:37 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080325 Fedora/2.0.0.13-1.fc8 Firefox/2.0.0.13

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):
cman cman-kernel

How reproducible:
Couldn't Reproduce


Steps to Reproduce:
The issue is random, have not found reproducer steps.

Actual Results:
cluster will hang until it is rebooted/restarted.

Expected Results:
That there should be at most 1 "transition restart" messages.

Additional info:
Comment 7 RHEL Program Management 2008-05-09 15:40:44 UTC 
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
release.
Comment 9 Christine Caulfield 2008-05-12 15:56:33 UTC 
Created attachment 305142 [details]
Patch

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.
Comment 10 Christine Caulfield 2008-05-13 10:38:54 UTC 
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
numbers up-to-date.

I do strongly recommend upgrading to 4.7 along with this though.
Comment 11 Christine Caulfield 2008-05-13 15:39:09 UTC 
Added to the RHEL4 branch:

commit 59ba19aa6b41cad189af153e27469056206e782d
Author: Christine Caulfield <ccaulfie>
Date:   Tue May 13 16:37:11 2008 +0100
Comment 12 Chris Feist 2008-05-22 16:18:45 UTC 
Requesting 4.6.z stream.
Comment 16 Christine Caulfield 2008-06-05 14:29:22 UTC 
*** Bug 449961 has been marked as a duplicate of this bug. ***
Comment 20 errata-xmlrpc 2008-07-25 19:09:55 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2008-0800.html