[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Subtree delete not supported: HDB bug?

What is the value of the hasSubordinates attribute is for some entries
that you can't delete?  For some reason, most (but not all!) of my
ou=people entries report hasSubordinates=TRUE, though of course none of
them actually do have subordinates.

I notice the wording of one of the x500 specs as saying that
hasSubordinates=TRUE means that an entry "may" have subordinates.  I don't
know whether that means the entry is allowed to have subordinates (but
doesn't LDAP allow all entries to have subordinates?) or whether it is
possible that the entry has subordinates and so further checks should be
performed to be sure?  I don't know enough about how LDAP schema work to
be able to contribute meaningfully in this area...

On Fri, 25 Mar 2005, James F. Hranicky wrote:

>On Fri, 25 Mar 2005 17:06:35 -0600 (CST)
>Eric Irrgang <erici@motown.cc.utexas.edu> wrote:
>> > I found that when I set up the database using HDB, I wasn't able to delete
>> > some of my contacts:
>> >
>> > 	ldapdelete -r -H ldaps://server.cise.ufl.edu \
>> > 	-D uid=jfh,ou=Users,dc=cise,dc=ufl,dc=edu -Y GSSAPI
>> > 	'cn=Someone There,ou=userabook,uid=jfh,ou=Users,dc=cise,dc=ufl,dc=edu'
>> >
>> > 	SASL/GSSAPI authentication started
>> > 	SASL username: jfh@CISE.UFL.EDU
>> > 	SASL SSF: 56
>> > 	SASL installing layers
>> > 	Delete Result: Operation not allowed on non-leaf (66)
>> > 	Additional info: subtree delete not supported
>> Did you get this sorted out?  I'm seeing something similar, but sporadically.
>> Do all deletes for uid=*,ou=Users,dc=cise,dc=ufl,dc=edu fail or just random ones?
>Honestly, I'm still in the testing phase of setting up our LDAP directory,
>so I didn't do much more testing than that.
>> One of my two replicas rejected three of four deletes I sent last night
>> for similar objects in the same subtree and continues to reject the
>> deletes with the same error.  The deletes worked fine on the other
>> directory.
>> I was approaching the problem as a database corruption issue, but you're
>> saying that you reloaded your data into an empty database and had the same
>> problem?  Did you actually remove the old database and journal files or
>> just slapadd your ldif in again?
>I removed everything, slapadded the ldif, and the same problem occurred.
>I did the same thing after changing the definition bdb and the deletes
>worked as expected.
>I've just upgraded to 2.3.2beta, though, I can see if I see the same
>behavior with that.

Eric Irrgang - UT Austin ITS Unix Systems - (512)475-9342