On Fri, Feb 15, 2008 at 3:01 PM, Schmidt, Florian <[EMAIL PROTECTED]> wrote: > Hi folks, > > First I still have to say, that it's really hard for me to configure > Heartbeat-v2. > > I checked my xml code with crm_verify and always get nearly the same > error > > This is my snippet: > > <master_slave id="drbd_master_slave" ordered="false"> > <meta_attributes id="37a63ee4-90f7-48d1-a1f0-d814a22369a7"> > <attributes> > <nvpair id="clone_max" name="clone_max" > value="2"/> > <nvpair id="clone_node_max" > name="clone_node_max" value="1"/> > <nvpair id="master_max" name="master_max" > value="1"/> > <nvpair id="master_node_max" > name="master_node_max" value="1"/> > <nvpair id="notify" name="notify" value="yes"/> > </attributes> > </meta_attributes> > <primitive id="drbd_r0" class="ocf" provider="heartbeat" > type="drbd"> > <operations> > <op id="drbd_Monitoring" interval="30s" > name="monitor" timeout="15s"/> > </operations> > <instance_attributes id="instance_attributes_drbd_r0"> > <attributes> > <nvpair id="drbd_resource" > name="drbd_resource" value="r0"/> > </attributes> > </instance_attributes> > </primitive> > </master_slave> > > > (sorry for text-breaks) > > If I check this via crm_verify -V -x tmp.xml this is the output: > > > [EMAIL PROTECTED] ~]# crm_verify -V -x tmp.xml > element master_slave: validity error : Element master_slave content does > not follow the DTD, expecting (meta_attributes | instance_attributes | > primitive | group)*, got (meta_attributes primitive status ) > crm_verify[4344]: 2008/02/15_14:53:30 ERROR: main: CIB did not pass DTD > validation > crm_verify[4344]: 2008/02/15_14:53:30 WARN: cluster_status: We do not > have quorum - fencing and resource management disabled > Errors found during check: config not valid > > Same error occurs with <resources> and </resources> around it. > I understand, that I only may have meta_attributes OR > instance_attributes OR primitive OR group in the <master_slave>-tag and > he found "status", which may not be contained. > But why does he find this? There is NO status tag in the snippet -.- > > With different snippets, this is the same....no "status in them, but > found "status".
As Andreas mentioned crm_verify is intended to work with complete configurations. We automatically add the status tag (if its not present) to avoid displaying errors when people use crm_verify on the cluster's cib.xml file. > > Slowly I think I'm to dumb for v2-configuration -*grml* > > :/me is going to drink some beer now > > Have a nice weekend.. > > Florian > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
