Issue #521 has been updated by Joel Foote. File lsc.xml added
Sure no problem. Results are the same: Aug 24 08:45:06 - DEBUG - Loading XML configuration from: /usr/src/lsc-2.0/etc/lsc.xml Aug 24 08:45:07 - INFO - Reflections took 210 ms to scan 2 urls, producing 64 keys and 249 values Aug 24 08:45:07 - DEBUG - Importing XML schema file: schemas/lsc-core-2.0.xsd Aug 24 08:45:07 - DEBUG - Importing XML schema file: schemas/lsc-nis-plugin-1.0.xsd Aug 24 08:45:07 - INFO - Logging configuration successfully loaded from /usr/src/lsc-2.0/etc/logback.xml Aug 24 08:45:07 - INFO - LSC configuration successfully loaded from /usr/src/lsc-2.0/etc/ Aug 24 08:45:07 - INFO - Connecting to LDAP server ldap://10.68.0.50/dc=example,dc=com as cn=manager,dc=example,dc=com Aug 24 08:45:07 - INFO - Connecting to LDAP server ldap://10.101.252.60/dc=itlab,dc=example,dc=com as jfoote@itlab Aug 24 08:45:07 - INFO - Starting sync for adGroup Aug 24 08:45:07 - DEBUG - Using pagedResults control for 1000 entries at a time Aug 24 08:45:07 - DEBUG - Synchronizing adGroup for {cn=role.ldap.acme-dev} Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": List of attributes considered for writing in destination: [cn, memberUid, gidNumber, objectClass] Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "cn" is in FORCE status Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "cn" with values [acme-dev] Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "memberUid" is in FORCE status Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "memberUid" with values [newtest] Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "gidNumber" is in FORCE status Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "gidNumber" with values [10001] Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "objectClass" is in FORCE status Aug 24 08:45:07 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "objectClass" with values [posixGroup, top] Aug 24 08:45:07 - ERROR - Error while adding entry cn=acme-dev,ou=group,dc=example,dc=com in directory :javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Entry Already Exists]; remaining name 'cn=acme-dev,ou=group' Aug 24 08:45:07 - ERROR - Error while synchronizing ID cn=acme-dev,ou=group,dc=example,dc=com: java.lang.Exception: Technical problem while applying modifications to the destination Aug 24 08:45:07 - DEBUG - java.lang.Exception: Technical problem while applying modifications to the destination java.lang.Exception: Technical problem while applying modifications to the destination at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:764) [lsc-core-2.0.jar:na] at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:663) [lsc-core-2.0.jar:na] at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:633) [lsc-core-2.0.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.7.0_05] at java.lang.Thread.run(Unknown Source) [na:1.7.0_05] Aug 24 08:45:07 - ERROR - Aug 24 08:45:07 - ERROR - All entries: 1, to modify entries: 1, successfully modified entries: 0, errors: 1 ---------------------------------------- Bug #521: Entries only being added, not updated on RDN change http://tools.lsc-project.org/issues/521 Author: Joel Foote Status: New Priority: Normal Assigned to: Category: Core Target version: Problem in version: 2.0 Attempting to take a source object, change it's name, and synchronize that into a destination directory. Everything appears to go as planned but the operation will only add, it does not update existing objects. LSC 2.0 Source directory looks like: cn=role.ldap.groupname,ou=LDAP,ou=Roles,ou=Groups,dc=itlab,dc=example,dc=com Destination directory looks like: cn=groupname,ou=group,dc=example,dc=com I have attached my full lsc.xml, but here is where I am doing the modification: <mainIdentifier>var sname = srcBean.getDatasetFirstValueById("cn"); var tmpname = sname.replaceAll("role.ldap.", ""); "cn=" + tmpname + ",ou=group,dc=example,dc=com"</mainIdentifier> The logs appear to show everything being processed right, up until the add completes. Is the task evaluating if this should be a create or update before the modification takes place? Here's an example of the log output I see: Aug 21 20:29:15 - DEBUG - Loading XML configuration from: /usr/src/lsc-2.0/etc/lsc.xml Aug 21 20:29:15 - INFO - Reflections took 215 ms to scan 2 urls, producing 64 keys and 249 values Aug 21 20:29:15 - DEBUG - Importing XML schema file: schemas/lsc-core-2.0.xsd Aug 21 20:29:15 - DEBUG - Importing XML schema file: schemas/lsc-nis-plugin-1.0.xsd Aug 21 20:29:15 - INFO - Logging configuration successfully loaded from /usr/src/lsc-2.0/etc/logback.xml Aug 21 20:29:15 - INFO - LSC configuration successfully loaded from /usr/src/lsc-2.0/etc/ Aug 21 20:29:15 - INFO - Connecting to LDAP server ldap://localhost/dc=example,dc=com as cn=manager,dc=example,dc=com Aug 21 20:29:15 - INFO - Connecting to LDAP server ldap://10.101.252.60/dc=itlab,dc=example,dc=com as jfoote@itlab Aug 21 20:29:15 - INFO - Starting async for adGroup Aug 21 20:29:15 - DEBUG - Asynchronous synchronize adGroup Aug 21 20:29:15 - DEBUG - Using pagedResults control for 1000 entries at a time Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": List of attributes considered for writing in destination: [cn, memberUid, gidNumber, objectClass] Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "cn" is in KEEP status Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "cn" with values [acme-dev] Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "memberUid" is in FORCE status Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "memberUid" with values [newtest] Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "gidNumber" is in FORCE status Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "gidNumber" with values [10001] Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Attribute "objectClass" is in FORCE status Aug 21 20:29:15 - DEBUG - In object "cn=acme-dev,ou=group,dc=example,dc=com": Adding attribute "objectClass" with values [posixGroup, top] Aug 21 20:29:15 - ERROR - Error while adding entry cn=acme-dev,ou=group,dc=example,dc=com in directory :javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Entry Already Exists]; remaining name 'cn=acme-dev,ou=group' -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
