Mailing List Archive: Linux-HA: Pacemaker

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION

Index | Next | Previous | View Threaded

lmb at suse

Nov 12, 2009, 2:58 AM

Post #1 of 6 (485 views)
Permalink

Re: ocf:heartbeat:pingd receives wrong value in $__ACTION

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?

Regards,
Lars

--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

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

kerdosa at gmail

Nov 12, 2009, 12:02 PM

Post #2 of 6 (456 views)
Permalink

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

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.

Thanks

dejanmm at fastmail

Nov 19, 2009, 6:34 AM

Post #3 of 6 (450 views)
Permalink

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

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? BTW, the list of allowed
operations is:

["monitor", "start", "stop", "migrate_to", "migrate_from"]

Thanks,

Dejan

> _______________________________________________
> 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

kerdosa at gmail

Nov 19, 2009, 8:35 AM

Post #4 of 6 (450 views)
Permalink

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

On Thu, Nov 19, 2009 at 7:34 AM, 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? BTW, the list of allowed
> operations is:
>
> ["monitor", "start", "stop", "migrate_to", "migrate_from"]
>

I used the following crm command to configure the pingd, it does not
complain anything. The wrongly configured pingd is running very well except
passing pingd-monitor-op to $__OCF_ACTION. I am using pacemaker-1.0.5 and
openais-0.80.5 on CentOS 5.3.

# configure pingd
crm configure primitive pingd-res ocf:heartbeat:pingd \
params dampen=5s multiplixer=20000 host_list=$defaultgw \
op pingd-monitor-op interval=1s timeout=10s

Thanks

andrew at beekhof

Nov 19, 2009, 9:49 AM

Post #5 of 6 (444 views)
Permalink

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

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.

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

lmb at suse

Nov 19, 2009, 5:53 PM

Post #6 of 6 (466 views)
Permalink

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

On 2009-11-19T18:49:53, Andrew Beekhof <andrew [at] beekhof> wrote:

> > 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.

Agreed. It should be a warning.

Possibly an error at higher "strict" levels, or if there'd be a way to
query the PE about the actions it actually knows about.

Regards,
Lars

--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________
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