I am working on a move from CentOS Directory (8.2.8) on CentOS 5 to 389-ds 1.2.11 on CentOS 6. I’m using a combination of the CentOS repositories and epel as suggested here. I'm finding ldif2db rejects entries while if I add them via ldapmodify they go in with no errors. This is a problem as db2ldif does not give sufficient debugging to identify the problem. Below are examples. Is there a way to get more debugging out of ldif2db that I am missing? Perhaps an error log level I’m missing? Has anyone else seen this behavior? I'm importing into a database other than userRoot if that makes a difference. thanks, -morgan [root@devldapm03 ~]# /usr/lib64/dirsrv/slapd-devldapm03/ldif2db -n studentRoot -i /var/tmp/students_fixed.ldif importing data ... [19/May/2014:15:53:48 -0400] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database [19/May/2014:15:53:48 -0400] - check_and_set_import_cache: pagesize: 4096, pages: 2015405, procpages: 52243 [19/May/2014:15:53:48 -0400] - Import allocates 3224648KB import cache. [19/May/2014:15:53:49 -0400] - import studentRoot: Beginning import job... [19/May/2014:15:53:49 -0400] - import studentRoot: Index buffering enabled with bucket size 100 [19/May/2014:15:53:49 -0400] - import studentRoot: Processing file "/var/tmp/students_fixed.ldif" ... [19/May/2014:15:55:04 -0400] - import studentRoot: WARNING: skipping entry "uid=xxxx,ou=students,dc=domain,dc=org" which violates attribute syntax, ending line 5457262 of file "/var/tmp/students_fixed.ldif" ... # # ldapmodify -x -a -h devldapm03.domain.net -D cn=directory\ manager -w pass <paste entry> adding new entry "uid=xxxx,ou=students,dc=domain,dc=org" -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
