On 5/23/07, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote:
On Tue, May 22, 2007 at 04:43:49PM -0300, [EMAIL PROTECTED] wrote:
> Hi Everyone,
>
> I'm trying to add monitor operations for some resources I've configured in
> the cib.xml, but when I try to do it using the GUI, I'm getting some
> errors:
>
> mgmtd[7444]: 2007/05/22_15:14:02 info: xml:<group
> id="group_db2pr1"><primitive id="resource_db2_prod"><instance_attributes
> id="resource_db2_prod_instance_attrs"><attributes><nvpair
> id="resource_db2_prod_target_role" name="target_role"
> value="started"/></attributes></instance_attributes></primitive></group>
> cib[7439]: 2007/05/22_15:14:02 info: cib_diff_notify:notify.c Update
> (client: 7444, call:78): 0.50.2102 -> 0.50.2103 (ok)
> tengine[7566]: 2007/05/22_15:14:02 info: te_update_diff:callbacks.c
> Processing diff (cib_update): 0.50.2102 -> 0.50.2103
> cib[11932]: 2007/05/22_15:14:03 info: write_cib_contents:io.c Wrote
> version 0.50.2103 of the CIB to disk (digest:
> 789c15bbc0135d47631abb9f7cc0e4f6)
> mgmtd[7444]: 2007/05/22_15:14:03 info: xml:<group
> id="group_db2pr1"><primitive id="resource_db2_prod"><instance_attributes
> id="resource_db2_prod_instance_attrs"><attributes><nvpair
> id="94c70633-51d4-4cd8-90d2-4e691be4f44f" name="instance"
> value="db2admin"/></attributes></instance_attributes></primitive></group>
> cib[7439]: 2007/05/22_15:14:03 info: cib_diff_notify:notify.c Update
> (client: 7444, call:80): 0.50.2103 -> 0.50.2104 (ok)
> tengine[7566]: 2007/05/22_15:14:03 info: te_update_diff:callbacks.c
> Processing diff (cib_update): 0.50.2103 -> 0.50.2104
> cib[11933]: 2007/05/22_15:14:03 info: write_cib_contents:io.c Wrote
> version 0.50.2104 of the CIB to disk (digest:
> 374a5221c4e4f35156c5b8035a553971)
> cib[7439]: 2007/05/22_15:14:03 ERROR: Element primitive content does not
> follow the DTD, expecting (operations? , meta_attributes* ,
> instance_attributes*), got (instance_attributes operations )
Old story, I'm afraid. The CIB is actually OK, because the order
doesn't matter, but it doesn't verify against the DTD. I guess
that the only solution is for the cib to ignore this particular
error. No idea if that's possible. Andrew?
xml is order-sensitive and in some cases we just have to deal with
that - because in order to tell the DTD not to care, you end up
loosing any benefit of doing the DTD validation.
unfortunately the people that wrote the GUI didn't take much notice of
the interfaces of the thing it was supposed to configure and you end
up with these sorts of problems.
fyi: dtd validation _can_ be turned off by setting
<cib ignore_dtd="false" ...>
in your configuration.
BUT BE VERY CAREFUL!
There are good reasons we turn it on by default :-)
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
