I'm currently making use of the DNA plugin to assign unique values for the 'uidNumber' attribute for new POSIX users, which (from what I understand) is the 'ideal' configuration in a large, corporate environment.
I decided to run a stress test by adding about twenty thousand users via the ldapadd command. After about the 3995th user, the server returned the following error for the 3996th:
adding new entry "uid=test3996,ou=People,dc=example,dc=com
ldapadd: Operation error (1)
additional info: Allocation of a new value for uidNumber failed! Unable to proceed.
I attempted to add the 3996th user myself through the 389 DS Management Console, and it returned the following error:
Cannot save to directory server:
netscape.ldap.LDAPException: error result (1); Allocation of a new value for uidNumber failed! Unable to proceed.; Operations error
These are my current DNA settings:
dn: cn=Account UIDs,cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config
cn: Account UIDs
dnafilter: (objectClass=posixAccount)
dnamagicregen: 0
dnamaxvalue: -1
dnanextvalue: 13003
dnarangerequesttimeout: 60
dnascope: dc=nsn,dc=com,dc=sg
dnasharedcfgdn: cn=Account UIDs,ou=Ranges,dc=nsn,dc=com,dc=sg
dnathreshold: 1
dnatype: uidNumber
objectClass: top
objectClass: extensibleObject
I find that if I delete the 3995th user, and set the 'dnanextvalue' attribute of the DNA configuration entry to '13002', the plugin doesn't throw the above exception. It just doesn't seem to be able to assign the 13003th uidNumber.
I've also tried restarting the server, as well as updating the libraries from the repositories, with the same results.
I'm running 389 DS on CentOS, kernel version 2.6.18-164.6.1.el5, if it helps.
Regards,
Fazli
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
