So Document examples for redhat 6 made it with Redhat 7 :) 2014-06-16 19:58 GMT+02:00 Thanachit Wichianchai <thanachi...@googlemail.com>: > Hi, It is EL 6.5. For Version: 1.1.10-5.el7-9abe687 it is the output posted > in redhat document. -- >>>>> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/ap-configfile-HAAR.html > > Thank you very much. > > Thanachit > > > Sent from my iPad > >> On 16 มิ.ย. 2557, at 23:24, Digimer <li...@alteeve.ca> wrote: >> >> The subject says 6.5, so we need Thanachit to clarify. >> >> If EL7, then no, there is no cman. You can use pcsd to form the cluster >> initially, but also, that version should not attempt to start cman at all, >> so I am still thinking it is RHEL/CentOS 6. >> >>> On 16/06/14 12:20 PM, emmanuel segura wrote: >>> From the previous output i seen this "Version: 1.1.10-5.el7-9abe687", >>> so my question is "cman is used on redhat7?" >>> >>> 2014-06-16 18:10 GMT+02:00 Digimer <li...@alteeve.ca>: >>>> You need to setup a skeleton cluster.conf file. You can use the 'ccs' tool, >>>> here is an example (I use for my cluster, adjust the names to suit): >>>> >>>> ccs -f /etc/cluster/cluster.conf --createcluster an-anvil-04 >>>> ccs -f /etc/cluster/cluster.conf --setcman two_node="1" expected_votes="1" >>>> ccs -f /etc/cluster/cluster.conf --addnode an-a04n01.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --addnode an-a04n02.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --addfencedev pcmk agent=fence_pcmk >>>> ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect >>>> an-a04n01.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect >>>> an-a04n02.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk an-a04n01.alteeve.ca >>>> pcmk-redirect port=an-a04n01.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk an-a04n02.alteeve.ca >>>> pcmk-redirect port=an-a04n02.alteeve.ca >>>> ccs -f /etc/cluster/cluster.conf --setfencedaemon post_join_delay="30" >>>> >>>> hth >>>> >>>> >>>>> On 16/06/14 07:13 AM, Thanachit Wichianchai wrote: >>>>> >>>>> Hello Pacemaker guys, >>>>> >>>>> I am doing a proof of concept of active/passive HA cluster on RHEL 6.5 >>>>> Since the customer who I am working for will finally get support from >>>>> Red Hat. Therefore, I am trying to comply with Red Hat Documentation. >>>>> as stated in several places that on RHEL 6.5 - pacemaker is now >>>>> supported with CMAN stack. >>>>> >>>>> I started configuring things by following steps describe in >>>>> >>>>> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/ap-configfile-HAAR.html >>>>> document. This document provides configuration steps by using pcs >>>>> command. no ccs or crmsh commands at all. >>>>> >>>>> After I have created cluster. I can start cluster services on node1 but >>>>> cannot start it on node2 - there error is /etc/cluster/cluster.conf is >>>>> not there on node2 >>>>> >>>>> pcs cluster start >>>>> Starting Cluster... >>>>> 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... xmlconfig cannot find /etc/cluster/cluster.conf >>>>> [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 ] >>>>> >>>>> Error: unable to start cman >>>>> >>>>> pcs cluster status command output on node1 shows "cman" stack >>>>> >>>>> pcs cluster status >>>>> Cluster Status: >>>>> Last updated: Mon Jun 16 15:31:53 2014 >>>>> Last change: Mon Jun 16 14:23:04 2014 via crmd on rhcs1.localdomain >>>>> Stack: cman >>>>> Current DC: rhcs1.localdomain - partition with quorum >>>>> Version: 1.1.10-14.el6-368c726 >>>>> 2 Nodes configured >>>>> 0 Resources configured >>>>> >>>>> PCSD Status: >>>>> Error: no nodes found in corosync.conf >>>>> >>>>> >>>>> but from the aforementioned document from Red Hat. the stack is corosync. >>>>> >>>>> [root@z1 ~]#*|pcs cluster status|* >>>>> >>>>> Cluster Status: >>>>> Last updated: Thu Jul 25 13:01:26 2013 >>>>> Last change: Thu Jul 25 13:04:45 2013 via crmd onz2.example.com >>>>> <http://z2.example.com> >>>>> Stack: corosync >>>>> Current DC:z2.example.com <http://z2.example.com> (2) - partition with >>>>> quorum >>>>> >>>>> Version: 1.1.10-5.el7-9abe687 >>>>> 2 Nodes configured >>>>> 0 Resources configured >>>>> >>>>> >>>>> from the 2 incidents above, I am not sure whether I am on the right path. >>>>> >>>>> My PoC objectives are to >>>>> >>>>> >>>>> 1. configure Active/Passive HA cluster on RHEL 6.5 >>>>> >>>>> 2. Get Full Support from Red Hat on both OS and High Availability Add-on >>>>> >>>>> >>>>> 3. choose HA Cluster software and stacks which has a future. I expect to >>>>> have more than 5 years support from Red Hat and Community. >>>>> >>>>> >>>>> I found this quick start guide for redhat on cluster >>>>> labshttp://clusterlabs.org/quickstart-redhat.html >>>>> >>>>> >>>>> >>>>> I am not sure whether I should use ccs command to create cluster first and >>>>> use pcs to manage resource. >>>>> >>>>> on more question, I see corosync will be supported in RHEL7. Can I use >>>>> only corosync with pacemaker in RHEL 6.5? Will I get support from Red Hat >>>>> ? >>>>> >>>>> >>>>> Could you guys please help advise? Thanks a lot. >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Thanachit Wichianchai / IT Specialist - RHCSA, RHCE >>>>> +66 87 696 5522/ thanachit [at] acm.org >>>>> <mailto:thanachit%20[at]%20acm.org> >>>>> >>>>> http://hi.im/thanachit >>>>> >>>>> Google Plus <https://plus.google.com/u/0/102459307371925233265/posts> >>>>> Linkedin <http://th.linkedin.com/in/thanachit> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>>> >>>>> Project Home: http://www.clusterlabs.org >>>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>>> Bugs: http://bugs.clusterlabs.org >>>> >>>> >>>> -- >>>> Digimer >>>> Papers and Projects: https://alteeve.ca/w/ >>>> What if the cure for cancer is trapped in the mind of a person without >>>> access to education? >>>> >>>> >>>> _______________________________________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>> Bugs: http://bugs.clusterlabs.org >> >> >> -- >> Digimer >> Papers and Projects: https://alteeve.ca/w/ >> What if the cure for cancer is trapped in the mind of a person without >> access to education? >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org
-- esta es mi vida e me la vivo hasta que dios quiera _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
