[Linux-cluster] Error in Cluster.conf

[Digimer]

On 24/06/14 08:55 AM, Jan Pokorný wrote:
> On 24/06/14 13:56 +0200, Fabio M. Di Nitto wrote:
>> On 6/24/2014 12:32 PM, Amjad Syed wrote:
>>> Hello
>>>
>>> I am getting the following error when i run ccs_config_Validate
>>>
>>> ccs_config_validate
>>> Relax-NG validity error : Extra element clusternodes in interleave
>>
>> You defined <clusternodes.. twice.
>
> That + the are more issues discoverable by more powerful validator
> jing (packaged in Fedora and RHEL 7, for instance, admittedly not
> for RHEL 6/EPEL):
>
> $ jing cluster.rng cluster.conf
>> cluster.conf:13:47: error:
>>    element "fencedvice" not allowed anywhere; expected the element
>>    end-tag or element "fencedevice"
>> cluster.conf:15:23: error:
>>    element "clusternodes" not allowed here; expected the element
>>    end-tag or element "clvmd", "dlm", "fence_daemon", "fence_xvmd",
>>    "gfs_controld", "group", "logging", "quorumd", "rm", "totem" or
>>    "uidgid"
>> cluster.conf:26:76: error:
>>    IDREF "fence_node2" without matching ID
>> cluster.conf:19:77: error:
>>    IDREF "fence_node1" without matching ID
>
> So it spotted also:
> - a typo in "fencedvice"
> - broken referential integrity; it is prescribed "name" attribute
>    of "device" tag should match a "name" of a defined "fencedevice"
>
> Hope this helps.
>
> -- Jan

Also, without fence methods defined for the nodes, rgmanager will block 
the first time there is an issue.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?