Unable to Configure a 2-Node Fault Resistant Cluster in RHEL 6
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problem-1
The main problem is that whenever I am starting the service by giving the command " service cman restart", I am getting the following error:
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 ]
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... [ OK ]
Waiting for quorum... [ OK ]
Starting fenced... [ OK ]
Starting dlm_controld... [ OK ]
Tuning DLM kernel config... [ OK ]
Starting gfs_controld... [ OK ]
Unfencing self... unfence rhcs1.systec.local failed
[FAILED]
Stopping cluster:
Leaving fence domain... [ OK ]
Stopping gfs_controld... [ OK ]
Stopping dlm_controld... [ OK ]
Stopping fenced... [ OK ]
Stopping cman... [ OK ]
Waiting for corosync to shutdown: [ OK ]
Unloading kernel modules... [ OK ]
Unmounting configfs... [ OK ]
Problem-2
Also Node-1 goes offline from the cluster by giving the message "Not a cluster member".
Problem-3
I am not able to add other instances to my fence device.
Could anyone please tell me the solution for the above issues.
Since your problem is with fencing (jugding from when the first error message appears), try to disable it temporarily and see if the cluster starts normally without it. It's worth mentioning that you have only one fencing device, whereas in a cluster with N nodes you would normally have N fencing devices. In your case you would need two.
Yes, after disabling the fence device from the cluster the cluster is able to start normally without it.
But as per my requirement, I can use only one fence device(Brocade Switch). And the moment I add one of the port of this fence device as Instance to the Fence method, it does not allow me to add the other port of the Fence device.
I have attahced an architecture diagram of my setup for your reference.
Also the status of the Service Group is displayed as "disabled", and when ever I try to start I am not able to do so.
Kinldy look into the above issue and help me in resolving it.
The the error " Unfencing self... unfence rhcs1.systec.local failed " shows that there is something wrong with your fence/unfence configuration. Is the name "rhcs1.systec.local" correct? Are the credentials correct? Is the fencing agent for Brocade sending the proper commands?
You need to check for errors that appear in files /var/log/cluster/*.log and /var/log/messages, and experiment with settings until you get it right. Keep in mind that setting up a cluster is not a simple task, you need to experiment a lot and break the system many times before you succeed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.