Re: [Pacemaker] ERROR: te_graph_trigger: Transition failed: terminated pacemaker's problem or mine?

On Mon, Apr 30, 2012 at 10:44 PM, Lars Ellenberg wrote: > On Mon, Apr 30, 2012 at 01:00:11PM +1000, Andrew Beekhof wrote: >> On Sat, Apr 28, 2012 at 5:40 AM, Lars Ellenberg >> wrote: >> > On Fri, Apr 27, 2012 at 11:31:23AM +0100, Tim Small wrote: >> >> Hi, >> >> >> >> I'm trying to get to the bot

Re: [Pacemaker] Change in meta clone-max result in resource restart everywhere

On Mon, Apr 30, 2012 at 9:36 PM, Rainer Brestan wrote: > When updating the meta attribute clone-max all instances of the clone are > terminated and immediately restarted. > > Following configuration (not symmetric cluster): > primitive resMux_gw ocf:heartbeat:Dummy op start interval="0" timeout="

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

[Pacemaker] RES: [Openais] Help on mysql-proxy resource

Tanks for the answer. I´m very sorry for the delay, I was on a trip. >> On 03/30/2012 12:52 PM, Carlos xavier wrote: >>> Hi. >>> >>> I have mysql-proxy running on my system and I want to agregate it to >>> the cluster configuration. >>> When it is started by the system I got this as result of ps

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

Re: [Pacemaker] DRBD and Pacemaker/Corosync

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

[Pacemaker] DRBD and Pacemaker/Corosync

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/Pacemaker/DRBD, and I expect to have some inputs and help to troubleshoot what is going on. Let me try to explain the best

Re: [Pacemaker] HAproxy resource not moving

Thank you all for your help, I have isolated the issue and it seems that its working correctly, it was miss configuration from my end, with the help of "crm configure property no-quorum-policy="ignore" We are nearly working as expected, however could someone confirm if the following assumption is