Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Users

R: crm configure primitive syntax, please HELP!!!

 

 

Linux-HA users RSS feed   Index | Next | Previous | View Threaded


g.abbruzzese at resi

Mar 30, 2012, 5:34 AM

Post #1 of 2 (581 views)
Permalink
R: crm configure primitive syntax, please HELP!!!

It doesn't seem to be working.

[root [at] NODE_ resources]# crm configure primitive resource_vrt_ip
ocf:heartbeat:IPaddr2 params ip="192.168.15.73" nic="bond0" meta
target-role="Stopped" multiple-active="stop_start" migration-treshold="3"
failure-timeout="0" op name="monitor" interval="180" timeout="60"

> WARNING: name=monitor: operation not recognized
> WARNING: name=monitor: operation not recognized
> Relax-NG validity error : Element op failed to validate attributes
> element op: Relax-NG validity error : Expecting an element
meta_attributes, got nothing
> element op: Relax-NG validity error : Invalid attribute id for element op
> element op: Relax-NG validity error : Element operations has extra
content: op
> Relax-NG validity error : Extra element operations in interleave
> element cib: Relax-NG validity error : Element cib failed to validate
content
> crm_verify[14761]: 2012/03/30_14:28:38 ERROR: main: CIB did not pass
DTD/schema validation
> Errors found during check: config not valid
> ERROR: resource_vrt_ip: attribute migration-treshold does not exist
> WARNING: resource_vrt_ip: action name=monitor not advertised in meta-data,
it may not be supported by the RA
> Do you still want to commit?

Any clue about the meaning of the id_spec parameter?
Tks


-----Messaggio originale-----
Da: linux-ha-bounces [at] lists
[mailto:linux-ha-bounces [at] lists] Per conto di Andreas Kurz
Inviato: venerdý 30 marzo 2012 13:46
A: linux-ha [at] lists
Oggetto: Re: [Linux-HA] crm configure primitive syntax, please HELP!!!

On 03/30/2012 01:14 PM, Guglielmo Abbruzzese wrote:
> Hi everybody,
> I've got a question probably very easy for someone I cant' find a proper
answer in the official doc.
> In details, if I refer to the official pacemaker documentation related to
the command "crm configure primitive" I find what follows:
>
> usage: primitive <rsc> [<class>:[<provider>:]]<type>
> [params <param>=<value> [<param>=<value>...]]
> [meta <attribute>=<value> [<attribute>=<value>...]]
> [utilization <attribute>=<value> [<attribute>=<value>...]]
> [operations id_spec
> [op op_type [<attribute>=<value>...] ...]]
>
> If I launch the following command by CLI:
>
> crm configure primitive resource_vrt_ip ocf:heartbeat:IPaddr2 params
ip="192.168.15.73" nic="bond0" meta target-role="Stopped"
multiple-active="stop_start" migration-treshold="3" failure-timeout="0"
operations XXXXXXXXX op name="monitor" interval="180" timeout="60"
>
> I get the following answer: "ERROR: operations: only single $id or $id-ref
attribute is allowed"
>
> Now, I can't get the meaning of the parameter "id_spec" mentioned in the
usage output. Could someone help me, or tell me what shell I write instead
of XXXXXXXX in order to get the following output in the cib??
>

you can omit that "operations XXXXXXXXX" part

Regards,
Andreas

--
Need help with Pacemaker?
http://www.hastexo.com/now


> <primitive class="ocf" id="resource_vrt_ip" provider="heartbeat"
type="IPaddr2">
> <instance_attributes id="resource_vrt_ip-instance_attributes">
> <nvpair id="resource_vrt_ip-instance_attributes-ip" name="ip"
value="192.168.15.73"/>
> <nvpair id="resource_vrt_ip-instance_attributes-nic" name="nic"
value="bond0"/>
> </instance_attributes>
> <meta_attributes id="resource_vrt_ip-meta_attributes">
> <nvpair id="resource_vrt_ip-meta_attributes-target-role"
name="target-role" value="Stopped"/>
> <nvpair id="resource_vrt_ip-meta_attributes-multiple-active"
name="multiple-active" value="stop_start"/>
> <nvpair id="resource_vrt_ip-meta_attributes-migration-threshold"
name="migration-threshold" value="3"/>
> <nvpair id="resource_vrt_ip-meta_attributes-failure-timeout"
name="failure-timeout" value="0"/>
> </meta_attributes>
> <operations>
> <op id="resource_vrt_ip-startup" interval="180" name="monitor"
timeout="60s"/>
> </operations>
> </primitive>
>
> P.S. I'd prefer not to load a XML file, I already tried it and it works
but it is not the purpose of my help request
>
> Thanks in advance
>
>
> Guglielmo Abbruzzese
> Project Leader
>
> RESI Informatica S.p.A.
> Via Pontina Km 44,044
> 04011 Aprilia (LT) - Italy
> Tel: +39 0692710 369
> Fax: +39 0692710 208
> Email: g.abbruzzese [at] resi
> Web: www.resi.it
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems




_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


florian at hastexo

Mar 30, 2012, 5:42 AM

Post #2 of 2 (545 views)
Permalink
Re: R: crm configure primitive syntax, please HELP!!! [In reply to]

On Fri, Mar 30, 2012 at 2:34 PM, Guglielmo Abbruzzese
<g.abbruzzese [at] resi> wrote:
> It doesn't seem to be working.
>
> [root [at] NODE_ resources]# crm configure primitive resource_vrt_ip
> ocf:heartbeat:IPaddr2  params ip="192.168.15.73" nic="bond0" meta
> target-role="Stopped" multiple-active="stop_start" migration-treshold="3"
> failure-timeout="0" op name="monitor" interval="180" timeout="60"

The correct syntax is just "op monitor interval=180 timeout=60".

Also, it's "migration-threshold", not "migration-treshold".

And of course, with "target-role=Stopped", the resource won't start,
but I'm sure you know this already.

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Linux-HA users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.