Rich,

Here's the information you requested.

389-ds-base-1.2.11.15-12.el6_4.x86_64 is the version, from the EPEL 6 repositories.

To be more specific, the indexes for that particular database (
ou=Organizations,dc=test,dc=net) are exactly at 1000, but the database has 1017 entries. There are 953 users (inetOrgPerson's) in the tree (ou=Organizations,dc=test,dc=net) that also have the employeeNumber attribute that are managed by DNA.

The database for
ou=Organizations,dc=test,dc=net is actually comprised of 4 databases. It's set-up like this:

1. Company 1: o=Company1,ou=Organizations,dc=test,dc=net has it's own database
2.
Company 2: o=Company2,ou=Organizations,dc=test,dc=net has it's own database
3. Company 3:
o=Company3,ou=Organizations,dc=test,dc=net has it's own database
4. All other companies fall within the
ou=Organizations,dc=test,dc=net database.

The database mentioned above that has 1017 entries is just the
ou=Organizations,dc=test,dc=net one.

If you want I can provide exact numbers for the others.
Untitled Document

 

Best Regards

Scott Crooks
Systems Engineer

Logo
Member of mcon group: Australia • Austria • China • Czech Republic • Germany • India • Japan • Malaysia • Russia • South Korea • Switzerland • USA


On 03/22/2013 11:57 PM, Rich Megginson wrote:
On 03/22/2013 03:24 AM, Scott Crooks wrote:
Greetings,

We're using 389-ds on CentOS 6.4

What  version of 389-ds-base? rpm -q 389-ds-base

with 3 master LDAP servers in different locations. All three master servers have a problem adding new users in our organization database using the DNA plugin.

We receive the following (unhelpful) error message in the log files:

[22/Mar/2013:09:54:37 +0800] NSUniqueAttr - ADD begin
[22/Mar/2013:09:54:37 +0800] NSUniqueAttr - ADD parameter untagged: uid
[22/Mar/2013:09:54:37 +0800] NSUniqueAttr - ADD target=cn=testuser01,ou=Organizations,dc=test,dc=net
[22/Mar/2013:09:54:37 +0800] dna-plugin - dna_pre_op: failed to allocate a new ID!!
[22/Mar/2013:09:54:37 +0800] dna-plugin - dna_pre_op: operation failure [1]
[22/Mar/2013:09:54:37 +0800] roles-plugin - --> roles_post_op
[22/Mar/2013:09:54:37 +0800] roles-plugin - --> roles_cache_change_notify
[22/Mar/2013:09:54:37 +0800] roles-plugin - <-- roles_post_op

We've tried indexing the uidNumber and employeeNumber attributes as described here: http://www.spinics.net/linux/fedora/389-users/msg10796.html

One curious fact: there are exactly 1000 users in our database for
ou=Organizations,dc=test,dc=net. When following the instructions for the above link, the log outputs the following

organizations: Indexing attribute: employeenumber
organizations: Indexed 1000 entries (97%).
organizations: Finished indexing.

Our organization uses employeenumber rather than uidNumber, but they're the same in the end. We find it strange that the user creation fails at exactly 1000 entries.

What do you mean "
user creation fails at exactly 1000 entries"?  Do you mean "after adding the 1000th user entry"?  The error above is from attempting to add cn=testuser01 - was that the 1000th user entry?


Any ideas on where the configuration is wrong? We assume it's a configuration problem.
 
Untitled Document

 

Best Regards

Scott Crooks
Systems Engineer

Logo
Member of mcon group: Australia • Austria • China • Czech Republic • Germany • India • Japan • Malaysia • Russia • South Korea • Switzerland • USA




--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users