[Pacemaker] monitor operation is not resumed
David Vossel
dvossel at redhat.com
Mon May 7 14:45:52 UTC 2012
----- Original Message -----
> From: "Kazunori INOUE" <inouekazu at intellilink.co.jp>
> To: "pacemaker at oss" <pacemaker at oss.clusterlabs.org>
> Sent: Monday, May 7, 2012 4:52:58 AM
> Subject: [Pacemaker] monitor operation is not resumed
>
> Hi,
>
> I am using Pacemaker-1.1.
> - pacemaker : db5e16736cc2682fbf37f81cd47be7d17d5a2364
> - glue : 2686:66d5f0c135c9
>
> A monitor is not resumed even if I changed enabled="false" into
> enabled="true".
>
>
> * 0. monitor is performed periodically.
>
> # crm configure show
> node $id="1" vm1
> node $id="2" vm2
> primitive prmDummy ocf:pacemaker:Dummy \
> op start interval="0s" timeout="60s" on-fail="restart" \
> op monitor interval="10s" timeout="60s" on-fail="restart" \
> op stop interval="0s" timeout="60s" on-fail="stop"
> property $id="cib-bootstrap-options" \
> dc-version="1.1.7-db5e167" \
> cluster-infrastructure="corosync" \
> no-quorum-policy="ignore" \
> stonith-enabled="false" \
> startup-fencing="false"
>
>
> * 1. enabled="false" was added. As a result, monitor stopped.
>
> # crm configure edit
> # crm configure show | grep monitor
> op monitor interval="10s" enabled="false" timeout="60s"
> on-fail="restart" \
>
>
> * 2. Then, monitor is NOT resumed although changed into
> enabled="true".
That sounds like a bug. Please report this on the issue tracker under the policy engine component. http://bugs.clusterlabs.org/
-- Vossel
> # crm configure edit
> # crm configure show | grep monitor
> op monitor interval="10s" enabled="true" timeout="60s"
> on-fail="restart" \
>
> ----
> Best regards,
> Kazunori INOUE
More information about the Pacemaker
mailing list