<div dir="ltr">Hi Emmanuel,<div><br></div><div>Thanks for the response! I thought cman is a newer version of corosync itself, w.r.t the plugin that is used between corosync (cluster membership) and pacemaker (resource group management) - is that not the case? I installed the pacemaker and cman packages on ubuntu 12.04, and no package like "corosync", and yet I see /etc/corosync/corosync.conf get created post cman installation - so what is the difference between these two? If running cman is not the same as running corosync, what am I doing here and what am I not understanding correctly?</div>
<div><br></div><div>Thanks,</div><div>Regards,</div><div>Vijay</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 26, 2014 at 5:47 PM, emmanuel segura <span dir="ltr"><<a href="mailto:emi2fast@gmail.com" target="_blank">emi2fast@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">{I'm trying to set up a three node cluster using pacemaker+corosync} =<br>
but you trying to use cman, depending on your distro you can use<br>
different cluster es: cman + pacemaker or corosync+pacemaker<br>
<br>
2014-06-27 2:22 GMT+02:00 Vijay B <<a href="mailto:os.vbvs@gmail.com">os.vbvs@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Hi,<br>
><br>
> I'm trying to set up a three node cluster using pacemaker+corosync, and I<br>
> installed the required packages on each node, checked for their network<br>
> connectivity so they can see each other, added the required startup scripts<br>
> and edited the cluster.conf file as well so it includes all three nodes.<br>
><br>
> Now, when on the first node, I attempt to start up cman using service cman<br>
> start, it times out thus:<br>
><br>
> vagrant@precise64-pmk1:~$ sudo service cman start<br>
><br>
> Starting cluster:<br>
><br>
> Checking if cluster has been disabled at boot... [ OK ]<br>
><br>
> Checking Network Manager... [ OK ]<br>
><br>
> Global setup... [ OK ]<br>
><br>
> Loading kernel modules... [ OK ]<br>
><br>
> Mounting configfs... [ OK ]<br>
><br>
> Starting cman... [ OK ]<br>
><br>
> Waiting for quorum... Timed-out waiting for cluster<br>
><br>
> [FAILED]<br>
><br>
> vagrant@precise64-pmk1:~$<br>
><br>
><br>
> Why is this? Is it because I have three nodes to begin with in my<br>
> /etc/cluster/cluster.conf, and so this node expects that the cluster quorum<br>
> is 2, and so it should be able to talk to at least one other node? At this<br>
> point, I haven't started the cman or pacemaker services on the other nodes.<br>
><br>
> If this is the case, what will happen when two nodes of the three die? In<br>
> case cluster.conf changes accordingly to reflect the new cluster membership,<br>
> what if all three nodes are simply powered off and one rebooted? The cluster<br>
> will be down, won't it?<br>
><br>
> What is the best way to get around this? I don't want to set<br>
> CMAN_QUORUM_TIMEOUT=0, since as I understand it, the node would then go<br>
> ahead and start itself as a cluster without waiting for the other nodes, and<br>
> if this causes my service to start up and it is already started/running on<br>
> another node, it could cause issues.<br>
><br>
> Now, I don't know how to configure quorum disks for pacemaker - is it<br>
> possible to do this with pacemaker? How does it work? What are the<br>
> recommended ways to address the above problem? I infer that if this disk is<br>
> configured, the node that grabs the disk first becomes the president of the<br>
> pacemaker cluster. In this context, I have another question - does corosync<br>
> have its own cluster membership state distributed across all cluster nodes?<br>
> If so, I guess quorum is configured at the corosync level rather than at the<br>
> pacemaker level?<br>
><br>
> Apologies in advance if my queries above are addressed in the documentation<br>
> already - I felt it would be quicker and more accurate to ask the community<br>
> for reliable info.<br>
><br>
> Thanks!<br>
> Regards,<br>
> Vijay<br>
><br>
><br>
><br>
</div></div><div class="im HOEnZb">> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
<br>
<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<br>
esta es mi vida e me la vivo hasta que dios quiera<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br></div>