[Linux-cluster] Antwort: Re: Antwort: Unable to start cman on FC12 VM's Cluster3

[brem belguebli]

Hi Bernd,

As you can see, the cluster.conf is quite simple, not yet any service
defined.

When launching service cman start (with this very simple config), corosync
is started (corosync -f) and cman_tool keeps on looping (every 0.2 seconds)
trying to join the cluster and then times out (after 1 minute looping).
Nothing more. This is what I mean by cman doesn't want to start.

The two_node key is set to 1, which means I do not need a qdisk.

There are no subpoints/subservices involved yet , no gfs, no clvm.....

I may have to try to disable FENCE_JOIN from /etc/init.d/cman as no fence
device is yet configured....

Brem

2010/3/8 Bernd Giese <bernd.giese at warburg-invest.com>

>
> OK what do you mean with did not want to start.
>
> If cman starts there are subpoints.
>
> Which of these subpoints/subservices failed to start ?
>
> A two node cluster is of course the most difficult setup.
>
> From my experience, try to use a quorum disk too.
>
> In any case you have to use a fence device!!!!
>
>
>
>
>   *brem belguebli <brem.belguebli at gmail.com>*
> Gesendet von: linux-cluster-bounces at redhat.com
>
> 08.03.2010 09:51
>   Bitte antworten zu
> linux clustering <linux-cluster at redhat.com>
>
>    An
>  linux clustering <linux-cluster at redhat.com>
>  Kopie
>   Thema
> Re: [Linux-cluster] Antwort: Unable to start cman on FC12 VM's
>  Cluster3
>
>
>
>
> Hi Bernd,
>
> Even with fence devices it did not want to start.
>
> Yes, things are well defined in each node's /etc/hosts, I have an entry for
> each node (FQDN and hostname).
>
> Brem
>
> 2010/3/8 Bernd Giese <*bernd.giese at warburg-invest.com*<bernd.giese at warburg-invest.com>
> >
>
> Hi,
>
> first of all you should define a fence device.
>
> And did you check dns or host file for your clusternode-names ?
>
>
>   *brem belguebli <**brem.belguebli at gmail.com* <brem.belguebli at gmail.com>*
> >*
> Gesendet von: *linux-cluster-bounces at redhat.com*<linux-cluster-bounces at redhat.com>
>
> 07.03.2010 15:26
>   Bitte antworten zu
> linux clustering <*linux-cluster at redhat.com* <linux-cluster at redhat.com>>
>
>
>   An
> *linux-cluster at redhat.com* <linux-cluster at redhat.com>
> Kopie
>   Thema
> [Linux-cluster] Unable to start cman on FC12 VM's Cluster3
>
>
>
>
>
> Hi,
>
> I'm fighting with cman on 2 FC12 VM's (KVM).
>
> I'm unable to start cman.
>
> Below my cluster.conf
> ------------------------------------------------------------
> <?xml version="1.0"?>
> <cluster name="fccl1" config_version="3">
>
>  <clusternodes>
>                 <clusternode name="node1.localdomain" votes="1"
> nodeid="1"/>
>                 <clusternode name="node2.localdomain" votes="1"
> nodeid="2"/>
>  </clusternodes>
>                 <cman expected_votes="2" two_node="1"/>
>  <fencedevices>
>  </fencedevices>
>
>  <rm>
>    <failoverdomains/>
>    <resources/>
>  </rm>
> </cluster>
> --------------------------------------------------------------
>
> when running service cman start, it times out and complains that it
> cannot join the cluster (timeout waiting for cluster), despite that
> corosync is started.
> Disabled selinux, nodes are referenced in each node's /etc/hosts.
>
> Any idea ?
>
>
> --
> Linux-cluster mailing list*
> **Linux-cluster at redhat.com* <Linux-cluster at redhat.com>*
> **https://www.redhat.com/mailman/listinfo/linux-cluster*<https://www.redhat.com/mailman/listinfo/linux-cluster>
>
>
> ***********************************************************************************
>
> Diese E-Mail einschließlich Ihrer Anhänge enthält vertrauliche oder
> rechtlich geschützte
>
> Informationen. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren
> Sie bitte sofort
>
> den Absender und löschen Sie diese E-Mail. Das unbefugte Kopieren dieser
> E-Mail oder die
>
> unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet.
>
>
>
> The information incl. attachments contained in this message is confidential
> or protected by
>
> law. If you are not the intended recipient, please contact the sender and
> delete this message.
>
> Any unauthorised copying of this message or unauthorised distribution of
> the information
>
> contained herein is prohibited.
>
>
> ***********************************************************************************
>
>
>
>
> --
> Linux-cluster mailing list*
> **Linux-cluster at redhat.com* <Linux-cluster at redhat.com>*
> **https://www.redhat.com/mailman/listinfo/linux-cluster*<https://www.redhat.com/mailman/listinfo/linux-cluster>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20100308/941443d2/attachment.htm>