[Pacemaker] ocf:heartbeat:pingd receives wrong value in $__ACTION

[hj lee]

On Thu, Nov 19, 2009 at 7:34 AM, Dejan Muhamedagic <dejanmm at fastmail.fm>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.fm>
> 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.com> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091119/010c25f7/attachment-0001.htm>