[lsc-users] ERROR - Error while looking for .....

[Vincent LEPETIT]

Hi,

I had some same error with some user account.

For example :

anv. 31 09:17:44 - ERROR - Error while looking for (&(objectClass=user)(sAMAccountName=amuller)) in ou=Etudiants,dc=PSL,dc=local: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'
janv. 31 09:17:44 - ERROR - Error while synchronizing ID {uid=amuller}: org.lsc.exception.LscServiceException: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'

This user is in source ldap but not in destination ad.

My destination basdn focus on this ou=Etudiants and i don’t have this error message for lot of other users account in this ou.

How can i explain this ?

Regards,
--
Pour toute demande de support informatique :
***@univ-psl.fr<mailto:***@univ-psl.fr>

Pour une assistance à distance : cliquez ici<http://get.teamviewer.com/ak6yycv>
---
Vincent Lepetit
Administrateur SystÚmes, Réseaux et Télécom
Tel : [phone]
Mob : [phone]
Paris Sciences et Lettres
60 rue mazarine
Paris, 75006
http://www.univ-psl.fr

[Soisik Froger]

Post by Vincent LEPETIT
I had some same error with some user account.
anv. 31 09:17:44 - ERROR - Error while looking for (&(objectClass=user)(sAMAccountName=amuller)) in ou=Etudiants,dc=PSL,dc=local: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'
janv. 31 09:17:44 - ERROR - Error while synchronizing ID {uid=amuller}: org.lsc.exception.LscServiceException: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'
This user is in source ldap but not in destination ad.
My destination basdn focus on this ou=Etudiants and i don’t have this error message for lot of other users account in this ou.
How can i explain this ?

Hi,

We see that LSC gets an error when requesting information for these records from your AD. Depending on how you have configured LSC, it will try and figure out what action is needed (adding the record, updating its attributes ...).

Could you share your LSC configuration?

[Vincent LEPETIT]

Hi Soisik,

In fact this problÚme seem to be the same problem than my other post about "Process during time".

If i use the option :
***@ldap:/etc/lsc/supann2ad# /usr/bin/lsc -f /etc/lsc/supann2ad -t1 -s all -c all -n

I do not have any problem


So i think the destination ad refused more connection and done the ldap ressearch session in error


With just one thread this probleme don’t occur.

Regards,
--
Pour toute demande de support informatique :
***@univ-psl.fr<mailto:***@univ-psl.fr>

Pour une assistance à distance : cliquez ici<http://get.teamviewer.com/ak6yycv>
---
Vincent Lepetit
Administrateur SystÚmes, Réseaux et Télécom
Tel : [phone]
Mob : [phone]
Paris Sciences et Lettres
60 rue mazarine
Paris, 75006
http://www.univ-psl.fr

Le 31 janv. 2018 à 11:19, Soisik Froger <***@savoirfairelinux.com<mailto:***@savoirfairelinux.com>> a écrit :

On 31/01/2018 09:48, Vincent LEPETIT wrote:
I had some same error with some user account.
For example :
anv. 31 09:17:44 - ERROR - Error while looking for (&(objectClass=user)(sAMAccountName=amuller)) in ou=Etudiants,dc=PSL,dc=local: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'
janv. 31 09:17:44 - ERROR - Error while synchronizing ID {uid=amuller}: org.lsc.exception.LscServiceException: javax.naming.CommunicationException: Request: 3 cancelled; remaining name 'ou=Etudiants'
This user is in source ldap but not in destination ad.
My destination basdn focus on this ou=Etudiants and i don’t have this error message for lot of other users account in this ou.
How can i explain this ?

Hi,

We see that LSC gets an error when requesting information for these records from your AD. Depending on how you have configured LSC, it will try and figure out what action is needed (adding the record, updating its attributes ...).

Could you share your LSC configuration?