Mailing List Archive: crmsh and monitor for lsb primitives not existing

crmsh and monitor for lsb primitives not existing

Dec 16, 2014, 2:19 PM

Post #1 of 4 (2197 views)

Hi.

crmsh 2.1 on rhel6.6/64 .

Looks like crmsh no longer allows one to set up a monitor on an "lsb"
primitive?

Eg:

crm(cups)# configure primitive lsb:cups \
> op monitor interval=120
ERROR: syntax in primitive: Unknown arguments: monitor interval=120 near
<monitor> parsing 'primitive lsb:cups op monitor interval=120'

which is bad, since, according to pacemaker docs:

By default, the cluster will not ensure your resources are still
healthy. To instruct the cluster to do this, you need to add a
monitor operation to the resource's definition

Does development or something fix this?

Thanks.

ps this is clearly a change, since I have previously successfully set up
monitor intervals on lsb resources... eg:

primitive Coral lsb:opencoral \
op monitor interval=120 \
meta target-role=Started

--
********************************
David William Botsch
Programmer/Analyst
@CNFComputing
botsch@cnf.cornell.edu
********************************
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: crmsh and monitor for lsb primitives not existing [ In reply to ]

emi2fast at gmail

Dec 16, 2014, 2:32 PM

Post #2 of 4 (2132 views)

Permalink

you are missing the resource name, try something like this:

configure primitive myresource lsb:cups \
> op monitor interval=120

2014-12-16 23:19 GMT+01:00 Dave Botsch <botsch@cnf.cornell.edu>:
> Hi.
>
> crmsh 2.1 on rhel6.6/64 .
>
> Looks like crmsh no longer allows one to set up a monitor on an "lsb"
> primitive?
>
> Eg:
>
> crm(cups)# configure primitive lsb:cups \
> > op monitor interval=120
> ERROR: syntax in primitive: Unknown arguments: monitor interval=120 near
> <monitor> parsing 'primitive lsb:cups op monitor interval=120'
>
>
> which is bad, since, according to pacemaker docs:
>
> By default, the cluster will not ensure your resources are still
> healthy. To instruct the cluster to do this, you need to add a
> monitor operation to the resource's definition
>
> Does development or something fix this?
>
> Thanks.
>
> ps this is clearly a change, since I have previously successfully set up
> monitor intervals on lsb resources... eg:
>
> primitive Coral lsb:opencoral \
> op monitor interval=120 \
> meta target-role=Started
>
>
>
>
>
> --
> ********************************
> David William Botsch
> Programmer/Analyst
> @CNFComputing
> botsch@cnf.cornell.edu
> ********************************
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

--
esta es mi vida e me la vivo hasta que dios quiera
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: crmsh and monitor for lsb primitives not existing [ In reply to ]

botsch at cnf

Dec 16, 2014, 2:32 PM

Post #3 of 4 (2136 views)

Permalink

Ah ha... I was missing the name of the resource. Since crmsh was telling
me the error was down at the "monitor", I was looking there instead of
up at the top.

Problem solved :)

On Tue, Dec 16, 2014 at 05:19:13PM -0500, Dave Botsch wrote:
> Hi.
>
> crmsh 2.1 on rhel6.6/64 .
>
> Looks like crmsh no longer allows one to set up a monitor on an "lsb"
> primitive?
>
> Eg:
>
> crm(cups)# configure primitive lsb:cups \
> > op monitor interval=120
> ERROR: syntax in primitive: Unknown arguments: monitor interval=120 near
> <monitor> parsing 'primitive lsb:cups op monitor interval=120'
>
>
> which is bad, since, according to pacemaker docs:
>
> By default, the cluster will not ensure your resources are still
> healthy. To instruct the cluster to do this, you need to add a
> monitor operation to the resource's definition
>
> Does development or something fix this?
>
> Thanks.
>
> ps this is clearly a change, since I have previously successfully set up
> monitor intervals on lsb resources... eg:
>
> primitive Coral lsb:opencoral \
> op monitor interval=120 \
> meta target-role=Started
>
>
>
>
>
> --
> ********************************
> David William Botsch
> Programmer/Analyst
> @CNFComputing
> botsch@cnf.cornell.edu
> ********************************
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

--
********************************
David William Botsch
Programmer/Analyst
@CNFComputing
botsch@cnf.cornell.edu
********************************
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: crmsh and monitor for lsb primitives not existing [ In reply to ]

botsch at cnf

Dec 16, 2014, 2:33 PM

Post #4 of 4 (2135 views)

Permalink

Yep... just figured that out 5 seconds ago when I decided to try the
same thing with pcs. Sometimes it's the simple things... :)

On Tue, Dec 16, 2014 at 11:32:18PM +0100, emmanuel segura wrote:
> you are missing the resource name, try something like this:
>
> configure primitive myresource lsb:cups \
> > op monitor interval=120
>
> 2014-12-16 23:19 GMT+01:00 Dave Botsch <botsch@cnf.cornell.edu>:
> > Hi.
> >
> > crmsh 2.1 on rhel6.6/64 .
> >
> > Looks like crmsh no longer allows one to set up a monitor on an "lsb"
> > primitive?
> >
> > Eg:
> >
> > crm(cups)# configure primitive lsb:cups \
> > > op monitor interval=120
> > ERROR: syntax in primitive: Unknown arguments: monitor interval=120 near
> > <monitor> parsing 'primitive lsb:cups op monitor interval=120'
> >
> >
> > which is bad, since, according to pacemaker docs:
> >
> > By default, the cluster will not ensure your resources are still
> > healthy. To instruct the cluster to do this, you need to add a
> > monitor operation to the resource's definition
> >
> > Does development or something fix this?
> >
> > Thanks.
> >
> > ps this is clearly a change, since I have previously successfully set up
> > monitor intervals on lsb resources... eg:
> >
> > primitive Coral lsb:opencoral \
> > op monitor interval=120 \
> > meta target-role=Started
> >
> >
> >
> >
> >
> > --
> > ********************************
> > David William Botsch
> > Programmer/Analyst
> > @CNFComputing
> > botsch@cnf.cornell.edu
> > ********************************
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA@lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

--
********************************
David William Botsch
Programmer/Analyst
@CNFComputing
botsch@cnf.cornell.edu
********************************
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems