A cluster service is started on a node outside of the restricted failoverdomain after logging "Failed to relocate service:<service>; restarting locally" in a RHEL 6 High Availability cluster with rgmanager

Solution Verified - Updated -

Issue

  • A service was started on a node which is not in the restricted failover domain.
  • After a service failed to start on the nodes in the failoverdomain, another node outside that domain started it, even though the domain is restricted
Oct  9 14:18:40 rhel6-node3 rgmanager[8721]: #70: Failed to relocate service:test; restarting locally
Oct  9 14:18:40 rhel6-node3 rgmanager[8721]: Recovering failed service service:test

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • Service using a restricted failover domain in /etc/cluster/cluster.conf

    <failoverdomain name="1then2" restricted="1" ordered="1">
    
    • At least one node in the cluster is not in the domain
    • An attempt to relocate the service in the domain is made with clusvcadm -r <service>

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content