[Pacemaker] Openais OCF Script Question
Tim Serong
tserong at novell.com
Mon May 31 10:54:39 UTC 2010
On 5/31/2010 at 02:49 PM, Emil Popov <epopov at postpath.com> wrote:
> Oops.. I had used different config in my example below:
>
> The config should be:
>
> primitive ppsd-6 ocf:custom:ppsd \
> > params externalip="192.168.0.50" \
> > op monitor interval="10s" timeout="90s" \
> > op start interval="0" timeout="1800s" \
> > op stop interval="0" timeout="180s" \
> > meta target-role="Started" is-managed="true"
> >
>
> No LSB Primitive named ppsd-6. It was LSB but I had changed it to ocf
> recently and somehow still tried to execute the former LSB script.
That sounds like bad behaviour. Can you please open a bug and include
an hb_report for a time period which shows the errant run of the LSB
script?
Thanks,
Tim
> -----Original Message-----
> From: Tim Serong [mailto:tserong at novell.com]
> Sent: Sunday, May 30, 2010 6:21 PM
> To: pacemaker at oss.clusterlabs.org
> Subject: Re: [Pacemaker] Openais OCF Script Question
>
> On 5/30/2010 at 11:13 AM, Emil Popov <epopov at postpath.com> wrote:
> > Hi
> > I'm trying to use a OCF script in my Openais Cluster.
> > For the most part it works. From time to time though , the Pacemaker
> > executes the original resource LSB script instead of the correct OCF
> one....
> > Therefore not passing correct parameters to the resource.
> >
> >
> > When I stop the resource and start it again it executes the correct ocf
> > script the second time around.
> >
> > This usually happened when the resource fails over to another node and
> > initially runs LSB script instead the OCF one. Very strange.
> >
> > Any advise is greatly appreciated.
> >
> > Below is the error in the /var/log/messages It insists on using the LSB in
>
> > /etc/init.d directory. I had renamed the /etc/init.d/ppsd script but that
> > causes the below error and Stonith reboots the node.
> >
> >
> >
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: info: do_lrm_rsc_op:
> Performing
> > key=186:20891:0:977e982d-1345-4d4f-b69f-9bf0de010aa3 op=ppsd-6_start_0 )
> > May 29 05:01:40 gpp0099pun018 lrmd: [10924]: info: rsc:ppsd-6: start
> > May 29 05:01:40 gpp0099pun018 lrmd: [7387]: WARN: For LSB init script, no
> > additional parameters are needed.
> > May 29 05:01:40 gpp0099pun018 lrmd: [7387]: ERROR: (raexeclsb.c:execra:266)
>
> > execv failed for /etc/init.d/ppsd: No such file or directory
> > May 29 05:01:40 gpp0099pun018 lrmd: [10924]: ERROR: Failed to open lsb RA
> > ppsd. No meta-data gotten.
> > May 29 05:01:40 gpp0099pun018 lrmd: [10924]: WARN: on_msg_get_metadata:
> > empty metadata for lsb::heartbeat::ppsd.
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: ERROR:
> > lrm_get_rsc_type_metadata(575): got a return code HA_FAIL from a reply
> > message of rmetadata with function g
> > et_ret_from_msg.
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: WARN: get_rsc_metadata: No
> > metadata found for ppsd::lsb:heartbeat
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: ERROR: string2xml: Can't parse
>
> > NULL input
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: ERROR: get_rsc_restart_list:
> > Metadata for (null)::lsb:ppsd is not valid XML
> > May 29 05:01:40 gpp0099pun018 crmd: [10927]: info: process_lrm_event: LRM
> > operation ppsd-6_start_0 (call=103, rc=254, cib-update=239, confirmed=true)
> > complete
> > <unknown>
> >
> >
> > Here is the resource configuration that I have in the Pacemaker. It's is
> > supposed to use OCF script named ppsd in directory
> > /usr/lib/ocf/resource.d/custom/ppsd
> >
> >
> > primitive ppsd-0 ocf:custom:ppsd \
> > params externalip="192.168.0.50" \
> > op monitor interval="10s" timeout="90s" \
> > op start interval="0" timeout="1800s" \
> > op stop interval="0" timeout="180s" \
> > meta target-role="Started" is-managed="true"
> >
> > Using Openais 0.80.5
> > Pacemaker 1.0.4
>
> Do you also have an LSB primitive defined called "ppsd-6"? Because that's
> what those logs say LRMD is trying to start...
>
> Regards,
>
> Tim
--
Tim Serong <tserong at novell.com>
Senior Clustering Engineer, OPS Engineering, Novell Inc.
More information about the Pacemaker
mailing list