Mailing List Archive: Linux-HA: Pacemaker

ocf:heartbeat:pingd receives wrong value in $__ACTION

Index | Next | Previous | View Threaded

kerdosa at gmail

Nov 11, 2009, 3:42 PM

Post #1 of 9 (584 views)
Permalink

ocf:heartbeat:pingd receives wrong value in $__ACTION

Hi,

I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack. I set
up ocf:hearbeat:pingd as a clone and enabled monitor operation. The monitor
operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__ACTION variable in
pingd RA, surprisingly that variable is set to pingd-monitor-op, not
monitor! Doesn't any body have the same issue?

Thanks
hj

kerdosa at gmail

Nov 11, 2009, 3:48 PM

Post #2 of 9 (556 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

One correction: The variable name $__ACTION in my previous mail was wrong,
the correct name is $__OCF_ACTION.

Here rewriting again with correct name:

I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack. I set
up ocf:hearbeat:pingd as a clone and enabled monitor operation. The monitor
operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__OCF_ACTION variable
in pingd RA, surprisingly that variable is set to pingd-monitor-op, not
monitor! Doesn't any body have the same issue?

andrew at beekhof

Nov 16, 2009, 6:34 AM

Post #3 of 9 (540 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

On Thu, Nov 12, 2009 at 9:02 PM, hj lee <kerdosa [at] gmail> wrote:
>
>
> On Thu, Nov 12, 2009 at 3:58 AM, Lars Marowsky-Bree <lmb [at] suse> wrote:
>>
>> On 2009-11-11T16:48:36, hj lee <kerdosa [at] gmail> wrote:
>>
>> > Here rewriting again with correct name:
>> >
>> > I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack. I
>> > set
>> > up ocf:hearbeat:pingd as a clone and enabled monitor operation. The
>> > monitor
>> > operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__OCF_ACTION
>> > variable
>> > in pingd RA, surprisingly that variable is set to pingd-monitor-op, not
>> > monitor! Doesn't any body have the same issue?
>>
>> That is certainly very weird. Does this only affect the pingd RA for
>> you?
>
> Yes, this is the only one.

what does your configuration look like?

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

kerdosa at gmail

Nov 18, 2009, 2:04 PM

Post #4 of 9 (526 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

Hi,

Sorry for long delay. This is my pingd configuration.

primitive pingd-res ocf:heartbeat:pingd \
params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
op pingd-monitor-op interval="1s" timeout="10s" \
meta target-role="started"
clone pingd-clone pingd-res \
meta target-role="Started"

The print from pingd rsc:
Nov 18 15:02:20 silverthorne2 pingd[13186]: INFO: __OCF_ACTION
pingd-monitor-op

So I added the following code to pingd rsc to make it work:

if echo "$__OCF_ACTION" | grep monitor > /dev/null; then
__OCF_ACTION=monitor
fi

Thanks

On Mon, Nov 16, 2009 at 7:34 AM, Andrew Beekhof <andrew [at] beekhof> wrote:

> On Thu, Nov 12, 2009 at 9:02 PM, hj lee <kerdosa [at] gmail> wrote:
> >
> >
> > On Thu, Nov 12, 2009 at 3:58 AM, Lars Marowsky-Bree <lmb [at] suse> wrote:
> >>
> >> On 2009-11-11T16:48:36, hj lee <kerdosa [at] gmail> wrote:
> >>
> >> > Here rewriting again with correct name:
> >> >
> >> > I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack. I
> >> > set
> >> > up ocf:hearbeat:pingd as a clone and enabled monitor operation. The
> >> > monitor
> >> > operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__OCF_ACTION
> >> > variable
> >> > in pingd RA, surprisingly that variable is set to pingd-monitor-op,
> not
> >> > monitor! Doesn't any body have the same issue?
> >>
> >> That is certainly very weird. Does this only affect the pingd RA for
> >> you?
> >
> > Yes, this is the only one.
>
> what does your configuration look like?
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker [at] oss
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>

--
Dream with longterm vision!
kerdosa

kerdosa at gmail

Nov 18, 2009, 2:11 PM

Post #5 of 9 (538 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

Hi again,

I found what is wrong. I should use "monitor" as an operation name in crm
command. I though it is id, realized today it becomes operation name
directly.

Thanks
hj

On Wed, Nov 18, 2009 at 3:04 PM, hj lee <kerdosa [at] gmail> wrote:

> Hi,
>
> Sorry for long delay. This is my pingd configuration.
>
> primitive pingd-res ocf:heartbeat:pingd \
> params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
> op pingd-monitor-op interval="1s" timeout="10s" \
> meta target-role="started"
> clone pingd-clone pingd-res \
> meta target-role="Started"
>
> The print from pingd rsc:
> Nov 18 15:02:20 silverthorne2 pingd[13186]: INFO: __OCF_ACTION
> pingd-monitor-op
>
> So I added the following code to pingd rsc to make it work:
>
> if echo "$__OCF_ACTION" | grep monitor > /dev/null; then
> __OCF_ACTION=monitor
> fi
>
> Thanks
>
>
> On Mon, Nov 16, 2009 at 7:34 AM, Andrew Beekhof <andrew [at] beekhof>wrote:
>
>> On Thu, Nov 12, 2009 at 9:02 PM, hj lee <kerdosa [at] gmail> wrote:
>> >
>> >
>> > On Thu, Nov 12, 2009 at 3:58 AM, Lars Marowsky-Bree <lmb [at] suse>
>> wrote:
>> >>
>> >> On 2009-11-11T16:48:36, hj lee <kerdosa [at] gmail> wrote:
>> >>
>> >> > Here rewriting again with correct name:
>> >> >
>> >> > I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack.
>> I
>> >> > set
>> >> > up ocf:hearbeat:pingd as a clone and enabled monitor operation. The
>> >> > monitor
>> >> > operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__OCF_ACTION
>> >> > variable
>> >> > in pingd RA, surprisingly that variable is set to pingd-monitor-op,
>> not
>> >> > monitor! Doesn't any body have the same issue?
>> >>
>> >> That is certainly very weird. Does this only affect the pingd RA for
>> >> you?
>> >
>> > Yes, this is the only one.
>>
>> what does your configuration look like?
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker [at] oss
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>
>
>
> --
> Dream with longterm vision!
> kerdosa
>

--
Dream with longterm vision!
kerdosa

andrew at beekhof

Nov 19, 2009, 12:05 AM

Post #6 of 9 (538 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

On Wed, Nov 18, 2009 at 11:04 PM, hj lee <kerdosa [at] gmail> wrote:
> Hi,
>
> Sorry for long delay. This is my pingd configuration.
>
> primitive pingd-res ocf:heartbeat:pingd \
> �� params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
> �� op pingd-monitor-op interval="1s" timeout="10s" \

this is your problem. you should have this instead:
op monitor interval="1s" timeout="10s"

> �� meta target-role="started"
> clone pingd-clone pingd-res \
> �� meta target-role="Started"
>
> The print from pingd rsc:
> Nov 18 15:02:20 silverthorne2 pingd[13186]: INFO: __OCF_ACTION
> pingd-monitor-op
>
> So I added the following code to pingd rsc to make it work:
>
> if echo "$__OCF_ACTION" | grep monitor > /dev/null; then
> � __OCF_ACTION=monitor
> fi
>
> Thanks
>
> On Mon, Nov 16, 2009 at 7:34 AM, Andrew Beekhof <andrew [at] beekhof> wrote:
>>
>> On Thu, Nov 12, 2009 at 9:02 PM, hj lee <kerdosa [at] gmail> wrote:
>> >
>> >
>> > On Thu, Nov 12, 2009 at 3:58 AM, Lars Marowsky-Bree <lmb [at] suse> wrote:
>> >>
>> >> On 2009-11-11T16:48:36, hj lee <kerdosa [at] gmail> wrote:
>> >>
>> >> > Here rewriting again with correct name:
>> >> >
>> >> > I am using pacemaker-1.0.5 on CentOS 5.3 with openais cluster stack.
>> >> > I
>> >> > set
>> >> > up ocf:hearbeat:pingd as a clone and enabled monitor operation. The
>> >> > monitor
>> >> > operation returns $OCF_ERR_UNIMPLEMENTED. I printed $__OCF_ACTION
>> >> > variable
>> >> > in pingd RA, surprisingly that variable is set to pingd-monitor-op,
>> >> > not
>> >> > monitor! Doesn't any body have the same issue?
>> >>
>> >> That is certainly very weird. Does this only affect the pingd RA for
>> >> you?
>> >
>> > Yes, this is the only one.
>>
>> what does your configuration look like?
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker [at] oss
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>
>
> --
> Dream with longterm vision!
> kerdosa
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker [at] oss
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

dejanmm at fastmail

Nov 19, 2009, 3:30 AM

Post #7 of 9 (535 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

Hi,

On Thu, Nov 19, 2009 at 09:05:18AM +0100, Andrew Beekhof wrote:
> On Wed, Nov 18, 2009 at 11:04 PM, hj lee <kerdosa [at] gmail> wrote:
> > Hi,
> >
> > Sorry for long delay. This is my pingd configuration.
> >
> > primitive pingd-res ocf:heartbeat:pingd \
> > �� params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
> > �� op pingd-monitor-op interval="1s" timeout="10s" \
>
> this is your problem. you should have this instead:
> op monitor interval="1s" timeout="10s"

crm will now check if the operation name really makes sense.

Thanks,

Dejan

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

andrew at beekhof

Nov 19, 2009, 4:17 AM

Post #8 of 9 (553 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

On Thu, Nov 19, 2009 at 12:30 PM, Dejan Muhamedagic <dejanmm [at] fastmail> wrote:
> Hi,
>
> On Thu, Nov 19, 2009 at 09:05:18AM +0100, Andrew Beekhof wrote:
>> On Wed, Nov 18, 2009 at 11:04 PM, hj lee <kerdosa [at] gmail> wrote:
>> > Hi,
>> >
>> > Sorry for long delay. This is my pingd configuration.
>> >
>> > primitive pingd-res ocf:heartbeat:pingd \
>> > �� params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
>> > �� op pingd-monitor-op interval="1s" timeout="10s" \
>>
>> this is your problem. �you should have this instead:
>> � �op monitor interval="1s" timeout="10s"
>
> crm will now check if the operation name really makes sense.

This is only a warning though right?

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

dejanmm at fastmail

Nov 20, 2009, 2:03 AM

Post #9 of 9 (509 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION [In reply to]

On Thu, Nov 19, 2009 at 06:49:53PM +0100, Andrew Beekhof wrote:
> On Thu, Nov 19, 2009 at 3:34 PM, Dejan Muhamedagic <dejanmm [at] fastmail> wrote:
> > Hi,
> >
> > On Thu, Nov 19, 2009 at 01:17:10PM +0100, Andrew Beekhof wrote:
> >> On Thu, Nov 19, 2009 at 12:30 PM, Dejan Muhamedagic <dejanmm [at] fastmail> wrote:
> >> > Hi,
> >> >
> >> > On Thu, Nov 19, 2009 at 09:05:18AM +0100, Andrew Beekhof wrote:
> >> >> On Wed, Nov 18, 2009 at 11:04 PM, hj lee <kerdosa [at] gmail> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > Sorry for long delay. This is my pingd configuration.
> >> >> >
> >> >> > primitive pingd-res ocf:heartbeat:pingd \
> >> >> > �� params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
> >> >> > �� op pingd-monitor-op interval="1s" timeout="10s" \
> >> >>
> >> >> this is your problem. �you should have this instead:
> >> >> � �op monitor interval="1s" timeout="10s"
> >> >
> >> > crm will now check if the operation name really makes sense.
> >>
> >> This is only a warning though right?
> >
> > No, it would be an error. Why's that a problem?
>
> Because OCF only specifies which actions an RA must support, it is
> allowed to support more.
>
> > BTW, the list of allowed
> > operations is:
> >
> > ["monitor", "start", "stop", "migrate_to", "migrate_from"]
>
> Well for a start you forgot demote and promote.
> We're also planning freeze,thaw, and backup.
>
> Seriously, do not make this an error.

I expected that one could update the list once new features are
implemented :)

Anyway, changed to warning.

Thanks,

Dejan

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads