Also found this :
sonicle@xstorage1:~# crm_verify -LV
xmlRelaxNGParseElement: element has no content
error: crm_abort:    validate_with_relaxng: Triggered assert at xml.c:5285 : 
ctx-rng != NULL
error: validate_with_relaxng:        Could not find/parse 
/usr/share/pacemaker/pacemaker-2.4.rng
error: unpack_resources:     Resource start-up disabled since no STONITH 
resources have been defined
error: unpack_resources:     Either configure some or disable STONITH with the 
stonith-enabled option
error: unpack_resources:     NOTE: Clusters with shared data need STONITH to 
ensure data integrity
Errors found during check: config not valid
while pacemaker-2.4.rng is there, containing:
and fencing-2.4.rng is there containing elements for stonith...
----------------------------------------------------------------------------------------
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Gabriele Bulfon
A:
Kristoffer Grönlund
Cluster Labs - All topics related to open-source clustering welcomed
Data:
25 agosto 2016 10.01.17 CEST
Oggetto:
Re: [ClusterLabs] converting configuration
Yes I'm packaging for our distro from sources, pacemaker 1.1.14, corosync 2.4.1 
and crm-shell 2.2.1
Our distro is an illumos distro, XStreamOS.
How can I check where it's looking for available primitives?
Here's the output from crm -dR:
sonicle@xstorage1:~# crm -dR
.EXT /usr/libexec/pacemaker/crmd version
DEBUG: pacemaker version: [err: ][out: CRM Version: 1.1.14 (70404b0)]
DEBUG: found pacemaker version: 1.1.14
crm(live)# configure
.INP: configure
.EXT cibadmin -Ql
crm(live)configure# show
.INP: show
node 1: xstorage1
node 2: xstorage2
property cib-bootstrap-options: \
have-watchdog=false \
dc-version=1.1.14-70404b0 \
cluster-infrastructure=corosync
crm(live)configure# primitive xstorage1-stonith stonith:external/ssh-sonicle \
.INP: primitive xstorage1-stonith stonith:external/ssh-sonicle \
op monitor interval="25" timeout="25" start-delay="25" \
.INP: op monitor interval="25" timeout="25" start-delay="25" \
params hostlist="xstorage1"
.INP: params hostlist="xstorage1"
ERROR: primitive not supported by the RNG schema
crm(live)configure#
----------------------------------------------------------------------------------------
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
----------------------------------------------------------------------------------
Da: Kristoffer Grönlund
A: gbul...@sonicle.com Cluster Labs - All topics related to open-source 
clustering welcomed
Cluster Labs - All topics related to open-source clustering welcomed
Data: 24 agosto 2016 20.40.08 CEST
Oggetto: Re: [ClusterLabs] converting configuration
Gabriele Bulfon
writes:
Hi,
In my previous tests I used a prebuilt older pacemaker/heartbeat package with a 
configuration like:
primitive xstor2-stonith stonith:external/ssh-sonicle \        op monitor 
interval="25" timeout="25" start-delay="25" \        params 
hostlist="xstor2"primitive xstor3-stonith stonith:external/ssh-sonicle \        
op monitor interval="25" timeout="25" start-delay="25" \        params 
hostlist="xstor3"location xstor2-stonith-pref xstor2-stonith -inf: 
xstor2location xstor3-stonith-pref xstor3-stonith -inf: xstor3property 
stonith-action=poweroffcommit
Now that I upgraded everything from sources and moved over to corosync 2, these 
commands are not recognized, refused
with "primitive not supported by the RNG schema".
Is there any way I can easily convert my old commands into the new ones?
Gabriele
Hmm, that is a misleading error message. It sounds like crmsh isn't
finding the Pacemaker schema correctly. Try running it with -dR
arguments and see if you get any strange errors.
Did you build from source yourself? What distribution are you running?
You may need some different arguments to configure for it to locate
everything correctly.
Cheers,
Kristoffer
--
// Kristoffer Grönlund
// kgronl...@suse.com
_______________________________________________Users mailing list: 
Users@clusterlabs.orghttp://clusterlabs.org/mailman/listinfo/usersProject Home: 
http://www.clusterlabs.orgGetting started: 
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdfBugs: 
http://bugs.clusterlabs.org
_______________________________________________
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to