Hi,
With the new python 3 installer and tools I'm hitting an issue adding
backends.
{william@ldapkdc 12:04} ~/development/389ds I0> dsconf -D 'cn=Directory
Manager' -H ldap://localhost backend create
Enter password for cn=Directory Manager on ldap://localhost :
Enter value for nsslapd-suffix : dc=newexample,dc=com
Enter value for cn : newexample
INFO:dsconf.backend_create:Sucessfully created newexample
{william@ldapkdc 12:04} ~/development/389ds I0> ldapsearch -H
ldap://localhost -b 'dc=newexample,dc=com' -s base
-x
# extended LDIF
#
# LDAPv3
# base <dc=newexample,dc=com> with scope baseObject
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
{william@ldapkdc 12:06} ~/development/389ds I0> cat newexample-com.ldif
dn: dc=newexample,dc=com
changetype: add
objectClass: top
objectClass: domain
dc: newexample
{william@ldapkdc 12:06} ~/development/389ds I0> ldapmodify -f
newexample-com.ldif -H ldap://localhost -D 'cn=Directory Manager' -W
Enter LDAP Password:
adding new entry "dc=newexample,dc=com"
ldap_add: No such object (32)
Now, I can create the objectClass: domain with ldif2db for the backend.
But the goal is to do this live. I think I'm getting the no_such_object,
because DS doesn't know *what* backend this entry should be put into,
because there is no parent, so the NO_SUCH_OBJECT comes from the rootdse
code.
Right now, I don't really have a great solution here. My thought is that
when we create the backend in ldbm_instance_create we create the
objectClass domain type that is correct as the first entry into the
database. This way we avoid the problem.
Alternately, because this operation has a specific DN, we should be able
to select the right backend because nsslapd-suffix should match the
entry I'm trying to add. But this seems more complicated as a fix (but
likely more correct).
Does this seem like a reasonable solution? Does anyone else have any
better ideas?
Thanks,
--
Sincerely,
William Brown
Software Engineer
Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
