[Pacemaker] target: 7 vs. rc: 0 error

[Florian Crouzat]

Le 06/06/2013 11:40, ESWAR RAO a écrit :
> Hi All,
>
> Can someone help me in my below setup:
>
> I am trying to monitor RA on a 2 node cluster setup.
> The resources are already running before start of HB+pacemaker.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> #crm configure primitive oc_d1 lsb::testd1 meta allow-migrate="true"
> migration-threshold="1" failure-timeout="30s" op monitor interval="3s"
> #crm configure clone oc_d1_clone oc_d1
>
> #crm configure primitive oc_d2 lsb::testd2 meta allow-migrate="true"
> migration-threshold="3" failure-timeout="30s" op monitor interval="5s"
> #crm configure clone oc_d2_clone oc_d2
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> But the resources are getting stopped on one node with below errors:
>
>   [11519]: WARN: status_from_rc: Action 9 (oc_d1:0_monitor_0) on
> ubuntu191 failed (target: 7 vs. rc: 0): Error
> Jun 06 14:45:22 ubuntu191 pengine: [11712]: notice: LogActions: Stop
> oc_d1:0  (ubuntu191)
>
>   Clone Set: oc_d1_clone [oc_d1]
>       Started: [ ubuntu190 ]
>       Stopped: [ oc_d1:1 ]
>   Clone Set: oc_d2_clone [oc_d2]
>       Started: [ ubuntu190 ]
>       Stopped: [ oc_d2:1 ]
>
> Thanks
> Eswar
>

1/ There is no question in your email.
2/ You should not start your HA resources in the runlevels if you intend 
to have them clusterized: pacemaker (aka: the resource manager) should 
start them.
3/ Eventually, if you persist against point 2, check what does 
return-code 7 means, and eventually read the sources from your RA to 
fine what could possibly returns 7.

-- 
Cheers,
Florian Crouzat