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

"updatedn" problems

Hi all,

I'm trying to set up replication, and seem to have made it work on my master 
server.  But slapd will not start on my slave server.  I get the following 

Oct 15 14:12:06 baa slapd[9270]: /etc/openldap/slapd.conf: line 105: updatedn 
DN is invalid

Here is the line from the slave server's slapd.conf:
updatedn "cn-replica,dc=borkholder,dc=com"

Here is the LDIF for that cn:
dn: cn=replica,dc=borkholder,dc=com
cn: replica
objectClass: organizationalRole
objectClass: simpleSecurityObject
objectClass: top
structuralObjectClass: organizationalRole
entryUUID: badf1252-b31b-1028-9bdc-df2e3972f30e
creatorsName: cn=Manager,dc=borkholder,dc=com
createTimestamp: 20041015173102Z
userPassword:: e1NTSEF9ejljTXhLbVhJTXliOGh4K0crMmlvbXRvYmUvaUs0M1Q=
entryCSN: 20041015173128Z#000001#00#000000
modifiersName: cn=Manager,dc=borkholder,dc=com
modifyTimestamp: 20041015173128Z

Now that password looks really wrong to me, but that is how they all look when 
I use slapcat, so I won't worry about that.

Is there something wrong with the cn=replica entry, or is this some sort of 
ACL problem?  I have been trying to follow along with the "LDAP System 
Administration" book, but I think it is a little out of date.