Re: [Pacemaker] colocation rule not obeyed

On Mon, Nov 29, 2010 at 6:55 AM, Patrick H. wrote: > I've got a replicated mysql with vip setup i've been trying to create, and > it doesnt seem to be obeying my colocation rule much. > > Situation: > I had shut down corosync on all (3) nodes and verified all associated > services were off. > I th

[Pacemaker] colocation rule not obeyed

I've got a replicated /mysql with vip/ setup i've been trying to create, and it doesnt seem to be obeying my colocation rule much. Situation: I had shut down corosync on all (3) nodes and verified all associated services were off. I then started it up an all 3 nodes. When it came back up, the

Re: [Pacemaker] [Problem]The movement of the resource is not possible.

Hi Andrew, Sorry My response was late. > I think the smartest thing to do here is drop the cib_scope_local flag from -f if(do_force) { crm_debug("Forcing..."); /* cib_options |= cib_scope_local|cib_quorum_override; */ cib_options |= cib_qu

[Pacemaker] Transition-graph of pengine does a loop when configuration set order of stonith.

Hi, We constituted two simple nodes of the clone resource of one clone resource and stonith. But we set order of a stonith resource and the clone resource. We generated a problem in the next procedure. Step1)Start two nodes and send trac1386.clone.crm. [r...@srv01 ~]# crm_mon -1 L

[Pacemaker] It affects it that the update of the attribute by attrd is late, and a resource starts with a standby node.

Hi, We constituted a cluster by two node constitution. It is constitution complicated slightly that included two pingd in constitution. We confirmed a phenomenon in the next procedure. Step1) 192.168.40.3 addresses invalidate the understanding of ping. Step2) Start two nodes and send trac1383.cr