[Pacemaker] Pacemaker not starting in 2nd node of a 2 node cluster

[Enric Muñoz]

Hi,

It seems that the nodes don't see each other:

# corosync-objctl | grep members
runtime.totem.pg.mrp.srp.members.1275439296.ip=r(0) ip(192.168.5.204)
runtime.totem.pg.mrp.srp.members.1275439296.join_count=1
runtime.totem.pg.mrp.srp.members.1275439296.status=joined

I can ping from one node to the other succesfully. How can I join them??

About the STONITH, I disabled it in the LCMC but it seems that it applied the changes only to the first node. I don't have any command crm available ( i read it's something about this version of pacemaker), so how can I disable it??

Sorry, I'm totally new on pacemaker/corosync.

Thanks

De: Michael Schwartzkopff [mailto:misch at clusterbau.com]
Enviado el: lunes, 29 de julio de 2013 11:15
Para: The Pacemaker cluster resource manager
Asunto: Re: [Pacemaker] Pacemaker not starting in 2nd node of a 2 node cluster


Am Montag, 29. Juli 2013, 09:01:01 schrieb Enric Muñoz:

> Hi all,

>

> I am trying to build a 2 node iSCSI HA storage cluster with Pacemaker,

> Corosync and DRBD on CentOS 6.4. I have problems while Building the

> cluster. The problem is that pacemaker is not starting in the second node.

> When doing corosync-cfgtool -s both nodes are active with no faults



Do the nodes see each other? Please check with



# corosync-objctl



In the section "members" at the end of the output there should be the names of both nodes and status should be "joined"



the other error message is self-explaining: The cluster does STONITH by default. Since you have no STONITH resources defined, it refuses to start resources. Please configure STONITH resources or disable the STONITH feature for testing by:



# crm configure property stonith-enabled="false"



But DO configure STONITH/fencing for a productive cluster that uses shared storage!



--

Dr. Michael Schwartzkopff

Guardinistr. 63

81375 München



Tel: (0163) 172 50 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130729/4f3ba468/attachment-0003.html>