Re: [Pacemaker] crmd does abort if a stopped node is specified

On Thu, 8 May 2014 09:58:41 +1000 Andrew Beekhof and...@beekhof.net wrote: node $id=131 vm01 node $id=132 vm02 (snip) Is the method of setting up ID of the node which has not participated in a cluster using a corosync stack like this? I don;t know how crmsh works, sorry $id=

Re: [Pacemaker] crmd does abort if a stopped node is specified

Hi, Andrew I read the code. In the present processing, a setup of startup-fencing is read only once after starting. https://github.com/ClusterLabs/pacemaker/blob/master/lib/pengine/unpack.c#L455 In Pacemaker-1.0, whenever unpack_nodes() was called, a setup was read.

Re: [Pacemaker] [Question] About quorum-policy=freeze and promote.

Why are you using ssh as stonith? i don't think the fencing is working because your nodes are in unclean state 2014-05-08 5:37 GMT+02:00 renayama19661...@ybb.ne.jp: Hi All, I composed Master/Slave resource of three nodes that set quorum-policy=freeze. (I use Stateful in Master/Slave

Re: [Pacemaker] [Question] About quorum-policy=freeze and promote.

Hi Emmanuel, Why are you using ssh as stonith? i don't think the fencing is working because your nodes are in unclean state No, STONITH is not carried out because all nodes lose quorum. This is right movement of Pacemaker. It is an example to use STONITH of ssh. Best Regards, Hideo

[Pacemaker] Require pointers on how to build an rpm for a specific Pacemaker Release.

Hi , I was able to build an rpm from current sources of Pacemaker on Cent OS 6.5 . I followed steps mentioned at http://blog.clusterlabs.org/blog/2013/Pacemaker-1-dot-1-10-final/ . I wanted to know how to make change to a specific Pacemaker release, then compile, and build rpm. i.e is there

[Pacemaker] [Problem][pacemaker1.0] The probe may not be carried out by difference in cib information of probe.

Hi All, We confirmed a problem when we performed clean up of the Master/Slave resource in Pacemaker1.0. When this problem occurs, probe processing is not carried out. I registered the problem with Bugzilla. * http://bugs.clusterlabs.org/show_bug.cgi?id=5211 In addition, I wrote the method of

[Pacemaker] Question about Pacemaker resource configuration troubleshooting

Hi, I created Pacemaker resource configuration file, but it does not accepts it. It complanes: /home/jnikom/Kiva/dev/Prod/flvr/pace loadConstraintsXML clu_con_init_2014_05_08_001.xml error: unpack_rsc_op:No further recovery can be attempted for mysqlres: stop action failed with 'not

Re: [Pacemaker] Question about Pacemaker resource configuration troubleshooting

On 9 May 2014, at 11:59 am, Jacob Nikom jni...@kivasystems.com wrote: Hi, I created Pacemaker resource configuration file, but it does not accepts it. It complanes: /home/jnikom/Kiva/dev/Prod/flvr/pace loadConstraintsXML clu_con_init_2014_05_08_001.xml error: unpack_rsc_op:No

Re: [Pacemaker] Require pointers on how to build an rpm for a specific Pacemaker Release.

On 9 May 2014, at 2:32 am, Monali Porob monali.po...@huawei.com wrote: Hi , I was able to build an rpm from current sources of Pacemaker on Cent OS 6.5 . I followed steps mentioned at http://blog.clusterlabs.org/blog/2013/Pacemaker-1-dot-1-10-final/ . I wanted to know how to make

Re: [Pacemaker] [Question] About quorum-policy=freeze and promote.

On 8 May 2014, at 1:37 pm, renayama19661...@ybb.ne.jp wrote: Hi All, I composed Master/Slave resource of three nodes that set quorum-policy=freeze. (I use Stateful in Master/Slave resource.) - Current DC: srv01 (3232238280) - partition with quorum

Re: [Pacemaker] [Question] About quorum-policy=freeze and promote.

On 9 May 2014, at 2:05 pm, renayama19661...@ybb.ne.jp wrote: Hi Andrew, Thank you for comment. Is it responsibility of the resource agent side to prevent a state of these plural Master? No. In this scenario, no nodes have quorum and therefor no additional instances should have