Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Pacemaker

Custom RA is not starting

 

 

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded


mohamed.s at alcatel-lucent

May 18, 2012, 8:02 AM

Post #1 of 2 (369 views)
Permalink
Custom RA is not starting

Hi,

I am trying pacemaker 1.1.6 + Corosync 1.4.2 to plan a migration from pacemaker1.0 + heartbeat3.0.0

I have a custom resource agent "QIPdAgent" which register with id as "qipd"
When I add that as a primitive resource, it does not start; instead it goes to unmanaged state.

But, I can manually execute the operations on the resource agent
# export OCF_ROOT=/usr/lib/ocf
# ./QIPdAgent monitor
# echo $?
7
# ./QIPdAgent start
# echo $?
0
# ./QIPdAgent monitor
# echo $?
0
------------------------
OCF_NOT_RUNNING - 7
OCF_SUCCESS - 0
------------------------
The meta-data of my RA is mentioned below:

<?xml version="1.0"?>
<!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
<resource-agent name="qipd">
<version>1.0</version>

<longdesc lang="en">
OCF Resource Agent for qipd
</longdesc>
<shortdesc lang="en">OCF Resource Agent for qipd</shortdesc>

<actions>
<action name="start" timeout="60s"/>
<action name="stop" timeout="60s"/>
<action name="monitor" timeout="60s" depth="0" interval="90s" start-delay="90s"/>
<action name="meta-data" timeout="15s"/>
</actions>
</resource-agent>

In /var/log/cluster/corosync.log, I get the error within a second.
----------------------------------------------------------------------
May 18 13:59:57 AMM1200-01 pengine: [31317]: notice: LogActions: Start qipd (AMM1200-01)
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=handle_response ]
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: unpack_graph: Unpacked transition 3: 5 actions in 5 synapses
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_te_invoke: Processing graph 3 (ref=pe_calc-dc-1337349597-26) derived from /var/lib/pengine/pe-input-3.bz2
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: te_rsc_command: Initiating action 4: monitor qipd_monitor_0 on AMM1200-01 (local)
May 18 13:59:57 AMM1200-01 pengine: [31317]: notice: process_pe_message: Transition 3: PEngine Input stored in: /var/lib/pengine/pe-input-3.bz2
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_lrm_rsc_op: Performing key=4:3:7:913c7226-b93b-412f-af28-194e9d24277a op=qipd_monitor_0 )
May 18 13:59:57 AMM1200-01 lrmd: [31315]: info: rsc:qipd probe[2] (pid 32583)
May 18 13:59:57 AMM1200-01 lrmd: [31315]: WARN: mapped the invalid return code 254.
May 18 13:59:57 AMM1200-01 lrmd: [31315]: info: operation monitor[2] on qipd for client 31318: pid 32583 exited with return code 1 (mapped from 254)
May 18 13:59:57 AMM1200-01 crmd: [31318]: info: process_lrm_event: LRM operation qipd_monitor_0 (call=2, rc=1, cib-update=107, confirmed=true) unknown error
May 18 13:59:57 AMM1200-01 crmd: [31318]: WARN: status_from_rc: Action 4 (qipd_monitor_0) on AMM1200-01 failed (target: 7 vs. rc: 1): Error
------------------------------------------------------------------------
I can add another custom RA as a primitive and that I working fine.
Can you please give some clues on what I should investigate more for this RA?

Thanks,
Raffi

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


dejanmm at fastmail

May 18, 2012, 8:41 AM

Post #2 of 2 (335 views)
Permalink
Re: Custom RA is not starting [In reply to]

Hi,

On Fri, May 18, 2012 at 08:32:23PM +0530, S, MOHAMED (MOHAMED)** CTR ** wrote:
> Hi,
>
> I am trying pacemaker 1.1.6 + Corosync 1.4.2 to plan a migration from pacemaker1.0 + heartbeat3.0.0
>
> I have a custom resource agent "QIPdAgent" which register with id as "qipd"
> When I add that as a primitive resource, it does not start; instead it goes to unmanaged state.
>
> But, I can manually execute the operations on the resource agent
> # export OCF_ROOT=/usr/lib/ocf
> # ./QIPdAgent monitor
> # echo $?
> 7
> # ./QIPdAgent start
> # echo $?
> 0
> # ./QIPdAgent monitor
> # echo $?
> 0
> ------------------------
> OCF_NOT_RUNNING - 7
> OCF_SUCCESS - 0
> ------------------------
> The meta-data of my RA is mentioned below:
>
> <?xml version="1.0"?>
> <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
> <resource-agent name="qipd">
> <version>1.0</version>
>
> <longdesc lang="en">
> OCF Resource Agent for qipd
> </longdesc>
> <shortdesc lang="en">OCF Resource Agent for qipd</shortdesc>
>
> <actions>
> <action name="start" timeout="60s"/>
> <action name="stop" timeout="60s"/>
> <action name="monitor" timeout="60s" depth="0" interval="90s" start-delay="90s"/>
> <action name="meta-data" timeout="15s"/>
> </actions>
> </resource-agent>
>
> In /var/log/cluster/corosync.log, I get the error within a second.
> ----------------------------------------------------------------------
> May 18 13:59:57 AMM1200-01 pengine: [31317]: notice: LogActions: Start qipd (AMM1200-01)
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=handle_response ]
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: unpack_graph: Unpacked transition 3: 5 actions in 5 synapses
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_te_invoke: Processing graph 3 (ref=pe_calc-dc-1337349597-26) derived from /var/lib/pengine/pe-input-3.bz2
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: te_rsc_command: Initiating action 4: monitor qipd_monitor_0 on AMM1200-01 (local)
> May 18 13:59:57 AMM1200-01 pengine: [31317]: notice: process_pe_message: Transition 3: PEngine Input stored in: /var/lib/pengine/pe-input-3.bz2
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: do_lrm_rsc_op: Performing key=4:3:7:913c7226-b93b-412f-af28-194e9d24277a op=qipd_monitor_0 )
> May 18 13:59:57 AMM1200-01 lrmd: [31315]: info: rsc:qipd probe[2] (pid 32583)
> May 18 13:59:57 AMM1200-01 lrmd: [31315]: WARN: mapped the invalid return code 254.
> May 18 13:59:57 AMM1200-01 lrmd: [31315]: info: operation monitor[2] on qipd for client 31318: pid 32583 exited with return code 1 (mapped from 254)
> May 18 13:59:57 AMM1200-01 crmd: [31318]: info: process_lrm_event: LRM operation qipd_monitor_0 (call=2, rc=1, cib-update=107, confirmed=true) unknown error
> May 18 13:59:57 AMM1200-01 crmd: [31318]: WARN: status_from_rc: Action 4 (qipd_monitor_0) on AMM1200-01 failed (target: 7 vs. rc: 1): Error
> ------------------------------------------------------------------------
> I can add another custom RA as a primitive and that I working fine.
> Can you please give some clues on what I should investigate more for this RA?

Read the OCF developer's guide to implement the RA. Use
ocf-tester to test it.

Thanks,

Dejan

> Thanks,
> Raffi
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
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

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.