# Keypath length is too small

**URL:** <https://dmap-community.ductus.global/t/keypath-length-is-too-small/1478>\
**Category:** YANG\
**Created:** [August 21, 2017, 9:11am UTC](https://dmap-community.ductus.global/t/keypath-length-is-too-small/1478 "2017-08-21T09:11:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![evyatar](https://avatars.discourse-cdn.com/v4/letter/e/958977/32.png) [@evyatar](https://dmap-community.ductus.global/u/evyatar)\
**Post date:** [August 21, 2017, 9:11am UTC](https://dmap-community.ductus.global/t/keypath-length-is-too-small/1478/1 "2017-08-21T09:11:21Z")

</div>

Hi,

When I running the Confd I am getting error that the keypath kength isn’t enough:  
DEBUG Library MAXDEPTH/MAXKEYLEN 20/9 for confd\_hkeypath\_t are too small, ConfD needs 22/4  
I know that I can increase it and need to compile again the libconfd but it looks to me unreasonable so I would like to investigate it and understand which module required so big key length and if I can know even what is the specific path that required it.  
Do you have any debug commands that can help with that?

Thanks,

---

<div class="post-metadata">

**Author:** ![jjohansson](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jjohansson](https://dmap-community.ductus.global/u/jjohansson)\
**Post date:** [August 21, 2017, 2:49pm UTC](https://dmap-community.ductus.global/t/keypath-length-is-too-small/1478/2 "2017-08-21T14:49:29Z")

</div>

I’m not aware of any debug-tools that directly can point to the length of the longest keypath.

I suppose you can use the pyang tool and export your data model to tree format to see where you have excessive indentation:

> $ pyang -f tree yang-file

pyang is documented in the UG