Le 25/03/2014 15:13, Clément OUDOT a écrit :
2014-03-25 15:05 GMT+01:00 Nicolas Moulonguet
<[email protected] <mailto:[email protected]>>:
Le 25/03/2014 14:26, Clément OUDOT a écrit :
2014-03-25 10:59 GMT+01:00 Nicolas Moulonguet
<[email protected] <mailto:[email protected]>>:
Le 25/03/2014 10:29, Clément OUDOT a écrit :
2014-03-25 10:26 GMT+01:00 Nicolas Moulonguet
<[email protected]
<mailto:[email protected]>>:
Hello !
i do not know what to do with this error :
____________________________________
mars 25 10:06:15 - ERROR - Error while modifying entry
uid=xxxx.xxxx,ou=people,dc=yyyy,dc=zzzz,dc=fr in
directory
:javax.naming.directory.SchemaViolationException: [LDAP:
error code 65 - attribute 'supannAutreMail' not
allowed]; remaining name 'uid=xxxx.xxxx'
mars 25 10:06:15 - ERROR - Error while synchronizing ID
uid=xxxx.xxxx,ou=people,dc=yyyy,dc=zzzz,dc=fr:
java.lang.Exception: Technical problem while applying
modifications to the destination
# Tue Mar 25 10:06:15 CET 2014
dn: uid=xxxx.xxxx,ou=people,dc=yyyy,dc=zzzz,dc=fr
changetype: modify
replace: supannAutreMail
supannAutreMail: [email protected]
<mailto:[email protected]>
mars 25 10:06:15 - ERROR - All entries: 180, to modify
entries: 68, successfully modified entries: 0, errors: 68
mars 25 10:06:15 - INFO - Starting clean for ldap2ldapTask
mars 25 10:06:15 - INFO - All entries: 180, to modify
entries: 0, successfully modified entries: 0, errors: 0
root@max4:/etc/ldap/schema#
You are trying to add an attribute (supannAutreMail) in an
entry without objectClass allowing this attribute.
Clément.
And though it seems to exist according to the phpLDAPadmin
view bellow
Can you check that supannPerson objectClass is present in
uid=xxxx.xxxx,ou=people,dc=yyyy,dc=zzzz,dc=fr ?
Clément
It is there in uid in some uids and it is not in other uids , but
result is the same if it is or if it is not : LDAP: error code 65
- attribute 'supannAutreMail' not allowed
If objectClass is not present in an entry, you will always have this
error for this entry.
This is an LDAP error, not a LSC error. Fix your data or configure LSC
to force objectClass values in your entries.
Clément.
Adding in LSC configuration (lsc.xml) :
<dataset>
<name>supannAutreMail</name>
<policy>FORCE</policy>
<defaultValues><string>js:srcBean.getDatasetFirstValueById("supannAutreMail")</string></defaultValues>
<forceValues><string>js:srcBean.getDatasetFirstValueById("supannAutreMail")</string></forceValues>
<createValues><string>js:srcBean.getDatasetFirstValueById("supannAutreMail")</string></createValues>
</dataset>
i have exactly the same error message :
mars 25 16:20:29 - ERROR - Error while modifying entry
uid=aaaa.bbbb,ou=people,dc=zzzz,dc=wwww,dc=fr in directory
:javax.naming.directory.SchemaViolationException: [LDAP: error code 65 -
attribute 'supannAutreMail' not allowed]; remaining name 'uid=aaaa.bbbb'
mars 25 16:20:29 - ERROR - Error while synchronizing ID
uid=aaaa.bbbb,ou=people,dc=zzzz,dc=wwww,dc=fr: java.lang.Exception:
Technical problem while applying modifications to the destination
# Tue Mar 25 16:20:29 CET 2014
dn: uid=aaaa.bbbb,ou=people,dc=zzzz,dc=wwww,dc=fr
changetype: modify
replace: supannAutreMail
supannAutreMail: [email protected]
mars 25 16:20:29 - ERROR - All entries: 180, to modify entries: 68,
successfully modified entries: 0, errors: 68
mars 25 16:20:29 - INFO - Starting clean for ldap2ldapTask
mars 25 16:20:30 - INFO - All entries: 180, to modify entries: 0,
successfully modified entries: 0, errors: 0
This appears to be not normal to me again. Why same error ???
Nicolas
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users