[Date Prev][Date Next]
Re: DB_KEYEXIST: Key/data pair already exists
Thanks a lot for your answer.
Would you please let me know what do I need in order to use uid for
example as the RDN value as I'm a little bit confused where to
Thanks a lot
2008/9/26 Quanah Gibson-Mount <email@example.com>:
> --On September 26, 2008 10:23:28 PM +0300 "Stelios A." <firstname.lastname@example.org>
>> Hello all,
>> I have 2 users with identical Full Name and their ldif change on mail,
>> uid, username and home directory in order to avoid ldap constraints.
>> However, even though I have no other constraints apart from
>> unique_attributes uid mail uidNumber homeDirectory I'm getting the
>> following error and cannot add the 2nd user.
>> root@masterldap:~# slapadd -l debug.ldif -f /etc/ldap/slapd.conf
>> => hdb_tool_entry_put: id2entry_add failed: DB_KEYEXIST: Key/data pair
>> already exists (-30996)
>> => hdb_tool_entry_put: txn_aborted! DB_KEYEXIST: Key/data pair already
>> exists (-30996)
>> slapadd: could not add entry dn="cn=Full
>> Name,ou=Users,dc=mydomain,dc=com" (line=1): txn_aborted! DB_KEYEXIST:
>> Key/data pair already exists (-30996)
>> Any ideas how I can see which attribute is causing the problem?
> The problem attribute is "cn". Since you are using cn (and not uid, which I
> would advise) as the RDN value, they must be different. This is why using
> cn for an RDN value is a bad idea.
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> Zimbra :: the leader in open source messaging and collaboration