Fencing and Adding a Failover to Clustering – Part 3

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Thilina Uvindasiri

I'm a BSc Special (Hons) graduate in Information Technology and works as an Engineer-Systems. Love to work, explore and research Linux and play rugby as a hobby.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

33 Responses

  1. Rakesh Negi says:

    Hi Thilina,

    Do you have notes for fencing on Centos 7 for 2 Nodes Cluster

  2. Rakesh Negi says:

    Hi ,
    CMAN service started fine in Node1 and Node2 but while starting cman at Master server it is getting fail.
    saying Node name cannot found.But the tags for both nodes are present .
    Has anyone came across such error.

    • Rakesh,
      can you post the error? Did you check that CMS can resolve the node IPs?

      • Rakesh Negi says:

        Hi Thilina,

        Below is the error:

        [[email protected] cluster]# service cman start
        Starting cluster:
        Checking if cluster has been disabled at boot… [ OK ]
        Checking Network Manager… [ OK ]
        Global setup… [ OK ]
        Loading kernel modules… [ OK ]
        Mounting configfs… [ OK ]
        Starting cman… Cannot find node name in cluster.conf
        Unable to get the configuration
        Cannot find node name in cluster.conf
        cman_tool: corosync daemon didn’t start Check cluster logs for details
        [FAILED]
        Stopping cluster:
        Leaving fence domain… [ OK ]
        Stopping gfs_controld… [ OK ]
        Stopping dlm_controld… [ OK ]
        Stopping fenced… [ OK ]
        Stopping cman… [ OK ]
        Unloading kernel modules… [ OK ]
        Unmounting configfs… [ OK ]

        Server details:
        10.91.18.145 master.uic.com – Management node
        10.91.18.143 node1.uic.com
        10.91.18.144 node2.uic.com

        /etc/hosts (10.91.18.145):

        127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
        ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
        10.91.18.143 node1.uic.com node1.uic.com
        10.91.18.144 node2.uic.com node2.uic.com
        10.91.18.145 master.uic.com master.uic.com

        cluster.conf (10.91.18.145):

        All the nodes (management node i.e. master.uic.com, node1, node2 can ping each other.

        Please help.

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *