Internal Error , when load merge cfg in confd-state version 7.5.2.1

Thanks in Advance …

Hi ,

confd-state version 7.5.2.1.
when i trying to load merge the config, I see that internal error before commit. I don’t see any crash .
but when give the value from the cli instead of load merge ,its working fine.

I was using the “confd-7.5.2.1/examples.confd/intro/11-c_hooks”. I have modified the yang .

yang changes :

container static {
tailf:info “Static routes”;
container route {
list rti-static-route-list {
tailf:info “Static route”;
tailf:cli-no-keyword;
key “ip-prefix next-hop”;
leaf ip-prefix {
tailf:info “destination”;
type inet:ip-prefix;
}
leaf next-hop {
tailf:info “Next hop(s) to destination or name of next-routing-instance”;
type union {
type inet:ip-address;
type string {
pattern ‘[0-9a-zA-Z_-]+’;
length “1 … 63”;
}
}
}
leaf invalid-keys {
tailf:hidden “invalid-keys”;
type uint32;
default 0;
}
leaf metric {
tailf:info “Metric value”;
type uint32 {
range “0 … 4294967295”;
tailf:info “<0-4294967295>;;Metric”;
}
}
leaf preference {
type int32 {
tailf:info “<0-255>;;Preference for this route;;Default 1”;
range “0 … 255”;
}
}
leaf tag {
tailf:info “Tag value which can be used as a match in redistribution policy”;
type uint32;
}
}
}
}

Output : (working one)

admin@ubuntu% set static route ::/0 2001:192:168:23::1
[ok][2022-01-16 21:04:06]

[edit]
admin@ubuntu% commit
Commit complete.
[ok][2022-01-16 21:04:09]

[edit]
admin@ubuntu%

Output(internal error)
admin@ubuntu% load merge interal_error.cfg
Error: internal error
[error][2022-01-16 21:10:23]

[edit]
admin@ubuntu%

Internal_error.cfg (contents)
static {
route {
0.0.0.0/0 192.168.13.1 {
preference 1;
tag 0;
}
::/0 2001:192:168:13::1 {
preference 1;
tag 0;
}
}
}

Could help someone on the above issue ?

You can increase your chances of getting a reply by using the Mastering Markdown · GitHub Guides as a reference on how to format your text. Especially note the guide on Quoting code .

You mention hooks example - that implies that there’s external app (example’s hook demon in this case) included in the pipeline.
This means that here should be some hints on failure in ConfD’s developer log - see developerLogLevel setting in confd.conf and check that you have it enabled for more debugging details…