Hi everyone,

I just wanted to create a new CIB..but got stuck at the very first
resource....


crm_verify -V  -x drbd_1_master_slave.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[10289]: 2008/07/15_15:30:07 ERROR: main: CIB did not pass DTD
validation
crm_verify[10289]: 2008/07/15_15:30:07 WARN: cluster_status: We do not
have quorum - fencing and resource management disabled
Errors found during check: config not valid



cat drbd_1_master_slave.xml
 <master_slave ordered="false" id="DRBD">
<meta_attributes id="DRBD_meta_attributes">
       <attributes>
         <nvpair id="DRBD_clone_max" name="clone_max" value="2"/>
         <nvpair id="DRBD_clone_node_max" name="clone_node_max"
value="1"/>
         <nvpair id="DRBD_master_max" name="master_max" value="1"/>
         <nvpair id="DRBD_master_node_max" name="master_node_max"
value="1"/>
         <nvpair id="DRBD_notify" name="notify" value="yes"/>
       </attributes>
     </meta_attributes>
       <primitive id="DRBD_saprouter" class="ocf" provider="heartbeat"
type="drbd">
       <operations>
         <op id="DRBD_saprouter_Monitoring_Default" interval="60s"
name="monitor" timeout="15s"/>
         <op id="DRBD_saprouter_Monitoring_Slave" interval="30s"
name="monitor" timeout="15s" role="Slave"/>
         <op id="DRBD_saprouter_Monitoring_Master" interval="20s"
name="monitor" timeout="15s" role="Master"/>
       </operations>
       <instance_attributes id="DRBD_saprouter_instance_attributes">
         <attributes>
           <nvpair id="DRBD_AFD_resource" name="drbd_resource"
value="drbd_saprouter"/>
         </attributes>
       </instance_attributes>
     </primitive>
   </master_slave>

There is no f*cking status in this snippet....so what does crm_verify
complain about?

I think I faced this error already some weeks ago but I forgot how to
solve it -.-

And one more short question:
Is this structure for a group embedded in a master/slave-resource fine
or do I need to change something?

<master_slave>
<group>
<meta_attributes/>
<primitive/>
<primitive/>
<primitive/>
</group>
</master_slave>

Thanks in advance

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

Reply via email to