[Pacemaker] "crm resource reprobe" behavior

Andrew Beekhof andrew at beekhof.net
Mon Apr 8 23:31:01 EDT 2013


On 09/04/2013, at 12:25 PM, Andrew Beekhof <andrew at beekhof.net> wrote:

> 
> On 08/04/2013, at 5:20 PM, Junko IKEDA <tsukishima.ha at gmail.com> wrote:
> 
>> Strangely, crm_resource --refresh also doesn't work.
>> It seemed that it worked well just one month before...
>> 
>> [root at GUEST03 ~]# crm_mon -1
>> Last updated: Mon Apr  8 16:17:30 2013
>> Last change: Mon Apr  8 16:16:53 2013 via cibadmin on GUEST03
>> Stack: corosync
>> Current DC: GUEST03 (3232242816) - partition with quorum
>> Version: 1.1.9-e8caee8
>> 2 Nodes configured, unknown expected votes
>> 1 Resources configured.
>> 
>> 
>> Online: [ GUEST03 GUEST04 ]
>> 
>> dummy  (ocf::pacemaker:Dummy): Started GUEST03
>> [root at GUEST03 ~]#
>> [root at GUEST03 ~]#
>> [root at GUEST03 ~]# crm_resource --refresh --resource dummy
>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
> 
> The good news is that the --refresh command is having the desired effect, the caller is "just" not getting the reply that tells it this.
> Still not ideal though.
> 
>> 
>> 
>> Thanks,
>> Junko
>> 
>> 
>> 2013/4/8 Junko IKEDA <tsukishima.ha at gmail.com>
>> Hi,
>> 
>> crm_resource -P showed the same.
>> 
>> [root at GUEST03 ~]# crm_resource -P -H 'GUEST03'
>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting

Same for this.  The -P command is working, the client just isn't being told of this.
Its not yet clear to me why.

>> 
>> [root at GUEST03 ~]# crm_resource -P -H 'GUEST04'
>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>> 
>> [root at GUEST03 ~]# crm_resource -P
>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>> 
>> Thanks,
>> Junko
>> 
>> 
>> 2013/4/8 Andrew Beekhof <andrew at beekhof.net>
>> 
>> On 04/04/2013, at 9:48 PM, Junko IKEDA <tsukishima.ha at gmail.com> wrote:
>> 
>>> Hi,
>>> 
>>> Is there any change in "crm resource reprobe"?
>> 
>> Not intentionally.
>> Does the underlying crm_resource command still work?
>> 
>>> It doesn't work with pacemaker + corosync.
>>> 
>>> 
>>> [root at GUEST03 ~]# crm_mon -1 -Af
>>> Last updated: Thu Apr  4 17:54:13 2013
>>> Last change: Thu Apr  4 17:12:30 2013 via crmd on GUEST04
>>> Stack: corosync
>>> Current DC: GUEST03 (3232242816) - partition with quorum
>>> Version: 1.1.9-e8caee8
>>> 2 Nodes configured, unknown expected votes
>>> 1 Resources configured.
>>> 
>>> 
>>> Online: [ GUEST03 GUEST04 ]
>>> 
>>> dummy  (ocf::pacemaker:Dummy): Started GUEST03
>>> 
>>> Node Attributes:
>>> * Node GUEST03:
>>> * Node GUEST04:
>>> 
>>> Migration summary:
>>> * Node GUEST03:
>>> * Node GUEST04:
>>> [root at GUEST03 ~]#
>>> 
>>> [root at GUEST03 ~]# crm resource reprobe GUEST03
>>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>>> 
>>> [root at GUEST03 ~]# crm resource reprobe guest03
>>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>>> 
>>> [root at GUEST03 ~]# crm resource reprobe
>>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>>> 
>>> [root at GUEST03 ~]# crm_resource -P -H 'GUEST03'
>>> Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
>>> 
>>> 
>>> 
>>> It worked well with heartbeat stack.
>>> 
>>> [root at guest01 ~]# crm_mon -1 -Af
>>> ============
>>> Last updated: Thu Apr  4 19:24:28 2013
>>> Stack: Heartbeat
>>> Current DC: guest02 (22222222-2222-2222-2222-222222222222) - partition with quorum
>>> Version: 1.0.13-30bb726
>>> 2 Nodes configured, unknown expected votes
>>> 1 Resources configured.
>>> ============
>>> 
>>> Online: [ guest01 guest02 ]
>>> 
>>> dummy  (ocf::pacemaker:Dummy): Started guest01
>>> 
>>> Node Attributes:
>>> * Node guest01:
>>> * Node guest02:
>>> 
>>> Migration summary:
>>> * Node guest01:
>>> * Node guest02:
>>> [root at guest01 ~]# crm resource reprobe guest01
>>> Waiting for 1 replies from the CRMd.
>>> 
>>> [root at guest01 ~]# crm resource reprobe GUEST01
>>> Waiting for 1 replies from the CRMd.
>>> 
>>> [root at guest01 ~]# crm resource reprobe guest02
>>> Waiting for 1 replies from the CRMd.
>>> 
>>> [root at guest01 ~]# crm resource reprobe GUEST02
>>> Waiting for 1 replies from the CRMd.
>>> 
>>> [root at guest01 ~]# crm resource reprobe
>>> Waiting for 1 replies from the CRMd.
>>> 
>>> 
>>> Regard,
>>> Junko IKEDA
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>> 
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>> 
>> 
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>> 
>> 
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
> 





More information about the Pacemaker mailing list