[Pacemaker] Two node KVM cluster

[Oriol Mula-Valls]

Hi,

I have modified the previous configuration to use sbd fencing. I have 
also fixed several other issues with the configuration and now when the 
node reboots seems not to be able to rejoin the cluster.

I attach the debug log I have just generated. Node was rebooted around 
11:51:41 and came back at 12:52:47.

The boot order of the services is:
1. sbd
2. corosync
3. pacemaker

Could someone help me, please?

Thanks,
Oriol

On 16/04/13 06:10, Andrew Beekhof wrote:
>
> On 10/04/2013, at 3:20 PM, Oriol Mula-Valls<oriol.mula-valls at ic3.cat>  wrote:
>
>> On 10/04/13 02:10, Andrew Beekhof wrote:
>>>
>>> On 09/04/2013, at 7:31 PM, Oriol Mula-Valls<oriol.mula-valls at ic3.cat>   wrote:
>>>
>>>> Thanks Andrew I've managed to set up the system and currently I have it working but still on testing.
>>>>
>>>> I have configure external/ipmi as fencing device and then I force a reboot doing a echo b>   /proc/sysrq-trigger. The fencing is working properly as the node is shut off and the VM migrated. However, as soon as I turn on the fenced now and the OS has started the surviving is shut down. Is it normal or am I doing something wrong?
>>>
>>> Can you clarify "turn on the fenced"?
>>>
>>
>> To restart the fenced node I do either a power on with ipmitool or I power it on using the iRMC web interface.
>
> Oh, "fenced now" was meant to be "fenced node".  That makes more sense now :)
>
> To answer your question, I would not expect the surviving node to be fenced when the previous node returns.
> The network between the two is still functional?
>


-- 
Oriol Mula Valls
Institut Català de Ciències del Clima (IC3)
Doctor Trueta 203 - 08005 Barcelona
Tel:+34 93 567 99 77
-------------- next part --------------
A non-text attachment was scrubbed...
Name: corosync.log.gz
Type: application/x-gzip
Size: 104331 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130428/8c0765ce/attachment-0002.bin>