Hi,
Thanks for you help so far Emmanuel. However, the last change did not
work, services are still kept on the NODE B, and are not migrating back
to NODE A.
On 12-05-01 3:07 PM, emmanuel segura wrote:
This it's wrong in your configuration
colocation fs_on_drbd inf: DRBD_fs DRBD_ms:Master
This it's wrong in your configuration
colocation fs_on_drbd inf: DRBD_fs DRBD_ms:Master
it must be
colocation fs_on_drbd inf: data_group DRBD_ms:Master
2012/5/1 Francois Gaudreault
> Hi Emmanuel,
>
> Thanks, that did resolve our split brain issue :)
>
> The only thing, is that the services a
Hi Emmanuel,
Thanks, that did resolve our split brain issue :)
The only thing, is that the services are not migrating back to the
primary node like expected
On 12-05-01 1:35 PM, emmanuel segura wrote:
try to change your constrain like this, if you
==
location
On Tuesday 01 May 2012 12:38:58 Francois Gaudreault wrote:
> From what we can see in the logs, it appears that the DRBD resource,
> for some reason, is not waiting for getting an established connection
> (to get initial sync) before changing its role to Primary. (I apologize
> for the length of t
try to change your constrain like this, if you
==
location DRBD_ms-master-on-pf1 data_group \
rule $id="DRBD_ms-master-on-pf1-rule" $role="master" inf: #uname eq npf1
==
if you look your order, when DRBD_FS:stop then DRBD_ms:demote and
Hi,
Here is the corosync.conf:
http://pastebin.com/xLKdURwA
Here is the cib.xml:
http://pastebin.com/g2pf0Dhy
Let me know if you also need the DRDB config.
Thanks!
On 12-05-01 12:51 PM, emmanuel segura wrote:
Hello Francois
can you post your cluster configuration using pastebin?
Thanks
20
Hello Francois
can you post your cluster configuration using pastebin?
Thanks
2012/5/1 Francois Gaudreault
> Hi,
>
> I am not sure if this is the right mailing list to post for our problems,
> let me know if this is more a Corosync issue.
>
> We are facing a weird behavior with Corosync/Pacema
