https://bugs.openldap.org/show_bug.cgi?id=10088
--- Comment #11 from git@zifbang.com --- (In reply to Quanah Gibson-Mount from comment #10)
If you read issue 8461 as I suggested, it clearly notes that the issue is related to the length of the value being over 512 characters. If you change the cn value to be fewer than 512 characters, it should work.
This comes from the following hard coded limit in LMDB 0.9:
mdb.c:#define MDB_MAXKEYSIZE ((MDB_DEVEL) ? 0 : 511)
The full DN string is 301 characters:
``` cn=a292979f2c86d513d48bbb9786b564b3c5228146e5ba46f404724e322544a7304a2b1049168803a5485e2d57a544c6a0d860af91330acb77e5907a9e601ad1227e80e0dc50abe963b47a004f2c90f570450d0e920d15436fdc771e3bdac0487a9735473ed3a79361d1778d7e53a7fb0e5f01f97a75ef05837d1d5496fc86968ff47fcb64,ou=people,dc=planetexpress,dc=com ```
The CN value string is 264 characters. You can verify this is true by inspecting the data in the original content of this issue. So I'm confused how this is the same issue if the issue is supposed to be triggered by attribute values exceeding 512 characters in length.