I'm trying to setup a supplier for single-master replication. I'm actually using Centos Directory Server v8.1 (which is probably equivalent to something like 389 dir serv v 1.2.4).
I created the changelog entry successfully. The next step, according to this doc: http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/8.1/html/Administration_Guide/Managing_Replication-Configuring-Replication-cmd.html#Configuring-Replication-Suppliers-cmd is to create the supplier replica entry. However, creation fails with error 32, and the message 'No such object'. If I run the slapd with debug level 3, I see the bind, and the fact that it is attempting an add, and then it says: [22/Mar/2011:10:08:31 -0500] - Calling plugin 'Legacy replication preoperation plugin' #3 type 407 [22/Mar/2011:10:08:31 -0500] - Calling plugin 'Multimaster replication preoperation plugin' #4 type 407 [22/Mar/2011:10:08:31 -0500] - => send_ldap_result 32:: [22/Mar/2011:10:08:31 -0500] - add_pb [22/Mar/2011:10:08:31 -0500] - <= send_ldap_result [22/Mar/2011:10:08:31 -0500] - get_pb [22/Mar/2011:10:08:31 -0500] - dse_add: parent does not exist [22/Mar/2011:10:08:31 -0500] - do_unbind What object doesn't exist? Evidently, a parent object. My assumption, based on the ldif data fed to ldapmodify, is either: a) I don't have the objectclass 'nsds5replica', or b) the dn: cn="dc=example,dc=com",cn=mapping tree,cn=config doesn't exist. However, if I query cn=mapping tree,cn=config for any/all objects, I see dn: cn="dc=example,dc=com",cn=mapping tree,cn=config. That suggests the problem isn't b). How do I determine if objectclass 'nsds5replica' exists? I see it is in a schema file named '00core.ldif', so why wouldn't it exist? Any other ideas? Thanks, Jon -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
