Now am able to see both nodes are registered... Node Sts Inc Joined Name 1 M 124 2013-09-17 22:05:31 test01.iopextech.com 2 M 132 2013-09-17 22:31:33 test02.iopextech.com
Is there any timeout option, where i can increase or decrease based on this? Thanks.. On Tue, Sep 17, 2013 at 4:53 PM, Gopalakrishnan N < gopalakrishnan...@gmail.com> wrote: > Even after giving FQDN in my /etc/hosts and /etc/sysconf/network also > updated in cluster.conf, propogated to other node as well, but still its > showing only one node. And muticast also enabled in my switch. > > > > > On Mon, Sep 16, 2013 at 11:52 PM, Gopalakrishnan N < > gopalakrishnan...@gmail.com> wrote: > >> My /etc/hosts is like this, >> cat /etc/hosts >> 127.0.0.1 localhost localhost.localdomain localhost4 >> localhost4.localdomain4 >> ::1 localhost localhost.localdomain localhost6 >> localhost6.localdomain6 >> 10.30.2.98 test01.iopextech.com test01 >> 10.30.2.99 test02.iopextech.com test02 >> >> >> and in my cluster.conf i have given the short name. So what you are >> saying better to use FQDN...! >> >> I will try to give FQDN in all my configuration files. >> >> And will try. Let's see. >> >> Thanks for your comments. >> >> >> >> On Mon, Sep 16, 2013 at 11:41 PM, Florian Crouzat < >> gen...@floriancrouzat.net> wrote: >> >>> Le 16/09/2013 17:30, Gopalakrishnan N a écrit : >>> >>>> Hey Guys, >>>> >>>> The OS am running is CentOS 6.4 (64bit) and I have disabled IPtables and >>>> SeLinux. >>>> >>>> My goal is to make Apache Tomcat as HA. As a first step thought of >>>> testing with Apache. >>>> >>>> My network setup is like this, >>>> Node1 is connected to switch >>>> Note2 is connected to switch. >>>> >>>> My cluster.conf file is as follows, >>>> [root@test01 ~]# cat /etc/cluster/cluster.conf >>>> <?xml version="1.0"?> >>>> <cluster config_version="1" name="mycluster1"> >>>> <logging debug="off"/> >>>> <clusternodes> >>>> <clusternode name="test01" nodeid="1"> >>>> <fence> >>>> <method name="pcmk-redirect"> >>>> <device name="pcmk" port="test01"/> >>>> </method> >>>> </fence> >>>> </clusternode> >>>> <clusternode name="test02" nodeid="2"> >>>> <fence> >>>> <method name="pcmk-redirect"> >>>> <device name="pcmk" port="test02"/> >>>> </method> >>>> </fence> >>>> </clusternode> >>>> </clusternodes> >>>> <fencedevices> >>>> <fencedevice name="pcmk" agent="fence_pcmk"/> >>>> </fencedevices> >>>> </cluster> >>>> >>>> >>>> And @some point of time am able to see both nodes are registered, >>>> [root@test01 ~]# cman_tool nodes >>>> Node Sts Inc Joined Name >>>> 1 M 104 2013-09-17 02:01:11 test01 >>>> 2 M 108 2013-09-17 02:15:07 test02 >>>> >>>> And @sometimes with crm_mon -1, I get the following >>>> >>>> [root@test01 ~]# crm_mon -1 >>>> Last updated: Tue Sep 17 02:47:27 2013 >>>> Last change: Tue Sep 17 00:42:43 2013 via crmd on test01 >>>> Stack: cman >>>> Current DC: NONE >>>> 4 Nodes configured, 2 expected votes >>>> 0 Resources configured. >>>> >>>> >>>> Node test01: UNCLEAN (offline) >>>> Node test01.iopextech.com <http://test01.iopextech.com>: UNCLEAN >>>> (offline) >>>> Node test02: UNCLEAN (offline) >>>> Node test02.iopextech.com <http://test02.iopextech.com>: UNCLEAN >>>> (offline) >>>> >>>> Thanks. >>>> >>>> >>> Ok, if you are still unhappy with CMAN check your switch for multicast. >>> >>> From there, I assume you are happy with cman otherwise there are no >>> reasons to start pacemaker, but you did, so you get my point ;) >>> >>> This kind of errors often indicates that your /etc/hosts or DNS is wrong >>> and pacemaker has a hard time to map hostnames and IPs, etc (not sure about >>> the internals there...) >>> Get rid of the invalid nodes by editing the configuration; stop >>> pacemaker; fix your resolutions and retry. >>> >>> In the entire process, I usually use FQDN in my cluster.conf file, and I >>> add them and the corresponding ring IP in my /etc/hosts file on all nodes. >>> I also use the same FQDN in my pacemaker configuration. >>> >>> Cheers >>> >>> >>> >>>> >>>> >>>> On Mon, Sep 16, 2013 at 8:40 PM, Florian Crouzat >>>> <gen...@floriancrouzat.net >>>> <mailto:gentoo@floriancrouzat.**net<gen...@floriancrouzat.net>>> >>>> wrote: >>>> >>>> Le 16/09/2013 14:18, Gopalakrishnan N a écrit : >>>> >>>> Do I need to have a cross over cable between each node? Is it >>>> mandatory? >>>> >>>> >>>> Nop it doesn't. >>>> In your case, I'd check the network architecture and/or firewalling >>>> regarding multicast. You probably either have wrong iptables and/or >>>> a switch dropping your multicast corosync ring(s). >>>> >>>> Also, please, as Andreas said: try to communicate with us in a more >>>> efficient way: more context, more informations and more output >>>> (pasted somewhere). >>>> >>>> We are happy to help people, but we don't have to waste our time >>>> trying to understand what these exact people doesn't tell us because >>>> they are lazy. >>>> >>>> ps: also use 'corosync-objctl' ; it's a good command to debug rings >>>> and configurations. >>>> >>>> Cheers, >>>> Florian. >>>> >>>> >>>> >>>> On Mon, Sep 16, 2013 at 8:01 PM, Gopalakrishnan N >>>> <gopalakrishnan...@gmail.com >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com> >>>> > >>>> <mailto:gopalakrishnan.an@__gm**ail.com <http://gmail.com> >>>> >>>> >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com>>>> >>>> wrote: >>>> >>>> Again the when i restarted the pacemaker and cman not the >>>> nodes are >>>> not in online, back to square 1. >>>> >>>> node1 shows only node1 online, and node2 says node2 online. >>>> I don't >>>> know what's happening in the background... >>>> >>>> Any advice would be appreciated.. >>>> >>>> Thanks. >>>> >>>> >>>> On Mon, Sep 16, 2013 at 6:47 PM, Gopalakrishnan N >>>> <gopalakrishnan...@gmail.com >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com> >>>> > >>>> <mailto:gopalakrishnan.an@__gm**ail.com <http://gmail.com> >>>> >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com> >>>> >>> >>>> >>>> wrote: >>>> >>>> Hi guys, >>>> >>>> I got it, basically it tool some time to propogate and >>>> now two >>>> nodes are showing online... >>>> >>>> Thanks. >>>> >>>> >>>> On Mon, Sep 16, 2013 at 6:39 PM, Gopalakrishnan N >>>> <gopalakrishnan...@gmail.com >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com> >>>> > >>>> <mailto:gopalakrishnan.an@__gm**ail.com<http://gmail.com> >>>> >>>> >>>> <mailto:gopalakrishnan.an@**gmail.com<gopalakrishnan...@gmail.com>>>> >>>> wrote: >>>> >>>> I have configured CMAN as per the link >>>> http://clusterlabs.org/doc/en-**__US/Pacemaker/1.1-plugin/** >>>> html-__single/Clusters_from_**Scratch/__index.html#_**configuring_cman<http://clusterlabs.org/doc/en-__US/Pacemaker/1.1-plugin/html-__single/Clusters_from_Scratch/__index.html#_configuring_cman> >>>> >>>> <http://clusterlabs.org/doc/**en-US/Pacemaker/1.1-plugin/** >>>> html-single/Clusters_from_**Scratch/index.html#_**configuring_cman<http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/index.html#_configuring_cman> >>>> > >>>> but >>>> when I type cman_tools nodes only one node is >>>> online even >>>> thought the cluster.conf is propogated in other >>>> node as well. >>>> >>>> what could be the reason, in node1, cman_tool nodes >>>> shows >>>> only node1 online, in node2 it shows only node2 is >>>> online. >>>> How to make two nodes as online, even thought CMAN >>>> service >>>> is running in both nodes. >>>> >>>> Thanks in advance. >>>> >>>> Regards, >>>> Gopal >>>> >>>> >>>> >>>> >>>> >>>> >>>> ______________________________**___________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> >>>> <mailto:Pacemaker@oss.**clusterlabs.org<Pacemaker@oss.clusterlabs.org> >>>> > >>>> >>>> http://oss.clusterlabs.org/__**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/__mailman/listinfo/pacemaker> >>>> >>>> >>>> <http://oss.clusterlabs.org/**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/mailman/listinfo/pacemaker> >>>> > >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: >>>> >>>> http://www.clusterlabs.org/__**doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/__doc/Cluster_from_Scratch.pdf> >>>> >>>> >>>> <http://www.clusterlabs.org/**doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf> >>>> > >>>> Bugs: http://bugs.clusterlabs.org >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Florian Crouzat >>>> >>>> ______________________________**___________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> <mailto:Pacemaker@oss.**clusterlabs.org<Pacemaker@oss.clusterlabs.org> >>>> > >>>> >>>> http://oss.clusterlabs.org/__**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/__mailman/listinfo/pacemaker> >>>> >>>> >>>> <http://oss.clusterlabs.org/**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/mailman/listinfo/pacemaker> >>>> > >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: >>>> >>>> http://www.clusterlabs.org/__**doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/__doc/Cluster_from_Scratch.pdf> >>>> >>>> >>>> <http://www.clusterlabs.org/**doc/Cluster_from_Scratch.pdf<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<http://oss.clusterlabs.org/mailman/listinfo/pacemaker> >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: http://www.clusterlabs.org/** >>>> doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf> >>>> Bugs: http://bugs.clusterlabs.org >>>> >>>> >>> >>> -- >>> Cheers, >>> Florian Crouzat >>> >>> ______________________________**_________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/mailman/listinfo/pacemaker> >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/** >>> doc/Cluster_from_Scratch.pdf<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