[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 Quanah Gibson-Mount changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 Quanah Gibson-Mount changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Keywords|needs_review| --- Comment #13 from Quanah Gibson-Mount --- This is a duplicate of 8461 as I initially marked it. The limit for an RDN with a normalizer is half of the usual 511 byte limit. *** This issue has been marked as a duplicate of issue 8461 *** -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 Quanah Gibson-Mount changed: What|Removed |Added Resolution|DUPLICATE |--- Status|VERIFIED|UNCONFIRMED Keywords||needs_review --- Comment #12 from Quanah Gibson-Mount --- Needs further review -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #11 from g...@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. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #10 from Quanah Gibson-Mount --- 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) -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #9 from Quanah Gibson-Mount --- (In reply to git from comment #7) > Given that this worked in prior versions, and does not in recent versions, > it is clearly a regression that should be addressed. No one disputes it is a regression. It is scheduled to be addressed in OpenLDAP 2.7. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #8 from Quanah Gibson-Mount --- (In reply to git from comment #6) > (In reply to Quanah Gibson-Mount from comment #4) > > (In reply to git from comment #3) > > > I suppose that the closure of this issue without any response means that > > > the > > > solution is to figure out how to revert back to HDB? > > > > It was marked as a duplicate of an existing issue since that's what it is. > > See that ITS for further details. > > That issue does not detail the same error, and none of my questions were > addressed in it. That's because it was hit via different paths. In the case I filed, it was using slapadd when slapd is offline. In your case, it was via a modrdn operation on a live server. The underlying problem is the same however. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #7 from g...@zifbang.com --- (In reply to Quanah Gibson-Mount from comment #5) > (In reply to Quanah Gibson-Mount from comment #4) > > (In reply to git from comment #3) > > > I suppose that the closure of this issue without any response means that > > > the > > > solution is to figure out how to revert back to HDB? > > > > It was marked as a duplicate of an existing issue since that's what it is. > > See that ITS for further details. > > As a side note, back-bdb/hdb no longer exist in any release past 2.4. I'd > suggest not making absurdly long name values. I don't get to make that decision. First, the test is to prove that `ldapjs` has no problem with such long attribute names (https://github.com/ldapjs/node-ldapjs/issues/480). Second, the spec does not impose any limit on attribute names (https://www.rfc-editor.org/rfc/rfc4514). Given that this worked in prior versions, and does not in recent versions, it is clearly a regression that should be addressed. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #6 from g...@zifbang.com --- (In reply to Quanah Gibson-Mount from comment #4) > (In reply to git from comment #3) > > I suppose that the closure of this issue without any response means that the > > solution is to figure out how to revert back to HDB? > > It was marked as a duplicate of an existing issue since that's what it is. > See that ITS for further details. That issue does not detail the same error, and none of my questions were addressed in it. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #5 from Quanah Gibson-Mount --- (In reply to Quanah Gibson-Mount from comment #4) > (In reply to git from comment #3) > > I suppose that the closure of this issue without any response means that the > > solution is to figure out how to revert back to HDB? > > It was marked as a duplicate of an existing issue since that's what it is. > See that ITS for further details. As a side note, back-bdb/hdb no longer exist in any release past 2.4. I'd suggest not making absurdly long name values. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #4 from Quanah Gibson-Mount --- (In reply to git from comment #3) > I suppose that the closure of this issue without any response means that the > solution is to figure out how to revert back to HDB? It was marked as a duplicate of an existing issue since that's what it is. See that ITS for further details. -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #3 from g...@zifbang.com --- I suppose that the closure of this issue without any response means that the solution is to figure out how to revert back to HDB? -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 Quanah Gibson-Mount changed: What|Removed |Added Status|RESOLVED|VERIFIED Keywords|needs_review| -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 Quanah Gibson-Mount changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Quanah Gibson-Mount --- *** This issue has been marked as a duplicate of issue 8461 *** -- You are receiving this mail because: You are on the CC list for the issue.
[Issue 10088] "DN index add failed" when renaming an entry
https://bugs.openldap.org/show_bug.cgi?id=10088 --- Comment #1 from g...@zifbang.com --- Created attachment 973 --> https://bugs.openldap.org/attachment.cgi?id=973&action=edit The test script as an attachment for easier usage. -- You are receiving this mail because: You are on the CC list for the issue.
