[email protected] wrote: > [email protected] wrote: >> [...] >> When adding, modifying and deleting an entry it can happend I do >> get a positive >> return from delete, but a subsequent "add" fails with "code=68: >> Already >> exists". > > Can you check whether the entry actually exist, although in "glue" > state? You can do this by searching (e.g. with ldapsearch) as the > rootdn, to bypass access checking, and using the manageDSAit control > (-MM).
I modified my test perl script to exit if adding the entry failed, albeit a preceding delete should have removed it. Then I manually ran ldapsearch -D "rootdn" ... -b "TestBaseDN" -MM "cn=TestEntry" I got ==== 8>< ========================== [...] # with manageDSAit critical control [...] dn: cn=TestEntry,TestBaseDN objectClass: inetOrgPerson description: oldValue [...] # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ==== 8>< ========================== I do see attributes reflecting state after "modify" (which changes "sn" attribute). Where exactly should I expect to see a note about "glue state"? Is output from "-d Any" helpful to figure what's going on (or wrong)? -- Regards, Peter
