Bug 698992 - cluster/cman not starting up. "[TOTEM ] The consensus timeout expired."
Summary: cluster/cman not starting up. "[TOTEM ] The consensus timeout expired."
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.1
Assignee: Fabio Massimo Di Nitto
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-22 15:00 UTC by Christian Horn
Modified: 2011-04-25 07:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-25 07:35:32 UTC
Target Upstream Version:


Attachments (Terms of Use)
cluster.conf two used for testing (812 bytes, application/octet-stream)
2011-04-22 15:00 UTC, Christian Horn
no flags Details
cluster.conf with configured qdisk, produces same result (812 bytes, application/octet-stream)
2011-04-22 15:02 UTC, Christian Horn
no flags Details
corosync.log of one of the 2 nodes (42.30 KB, text/x-log)
2011-04-22 15:03 UTC, Christian Horn
no flags Details

Description Christian Horn 2011-04-22 15:00:21 UTC
Created attachment 494247 [details]
cluster.conf two used for testing

Description of problem: 
  Starting cman... [FAILED], cluster not starting

Version-Release number of selected component (if applicable):
  rhel6.1 beta snapshot 4

How reproducible:
  always

Steps to Reproduce:
1. setup 2 nodes, virtualized fine
2. yum -y install cman rgmanager
3. deploy cluster.conf_twonode as /etc/cluster/cluster.conf on both nodes
4. service cman start
  
Actual results:
  Starting cman... [FAILED]

Expected results:
  Starting cman... [OK]

Additional info:
  Using a config with qdisk brings up the same problem, qdisk via
  iscsi initiator was used here, cluster.conf_qdisk is attached.

Comment 2 Christian Horn 2011-04-22 15:02:13 UTC
Created attachment 494248 [details]
cluster.conf with configured qdisk, produces same result

Comment 3 Christian Horn 2011-04-22 15:03:46 UTC
Created attachment 494249 [details]
corosync.log of one of the 2 nodes

Comment 5 RHEL Program Management 2011-04-23 06:00:34 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Steven Dake 2011-04-25 02:16:36 UTC
Christian,

It looks to me like your firewall is enabled.

Is it configured properly?

Regards
-steve

Comment 7 Christian Horn 2011-04-25 07:28:47 UTC
Steven,

sorry for the noise - true, the firwall was established.
Did multiple installations to verify the behaviour, all with the new
virt-install setup here that deployed a firewall..
The cluster comes up now in both configurations, two_node as well as qdisk.

Sorry again, Christian


Note You need to log in before you can comment on or make changes to this bug.