Why does a cluster node fence other nodes that haven't started cman yet when it initially joins the cluster in RHEL 4, 5, or 6?

Solution Unverified - Updated -

Issue

  • When starting cman on node 1, it fences node 2 (which has not yet started cman).
  • Nodes that are not in the cluster are rebooted when other nodes join the cluster for the first time.
  • Two nodes in cluster got rebooted. Both nodes in same cluster and both nodes in the cluster sent a reboot signal to each other, one fencing the other first then the other when it was coming back up.
  • Why is my cluster node powering off a node that isn't in the cluster when it is booted up?

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
  • Red Hat Cluster Suite (RHCS) 4
  • fencedevices defined in /etc/cluster/cluster.conf, and fenced enabled for use by the cluster (FENCE_JOIN="yes" or left unset in /etc/sysconfig/cman)
  • <fence_daemon clean_start="0"> or left unset in /etc/cluster/cluster.conf

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.