LDAP nightly sync changes no records in RTC 2.0
Dieter Paul (103●1●16●20)
| asked Sep 23 '09, 4:50 a.m.
edited May 27 '14, 3:55 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
We are using LDPA for RTC 2.0 and (now) everything is working fine.
Except the nightly sync. We enabled it in the configuration, but as far as we can see nothing is done. There is an entry in the logfile (runs 0ms?), but nothing else. Any ideas how we can check, where the error is? Dieter In the log file we see the following entry: 2009-09-23 10:40:28,759 INFO .internal.userregistry.ldap.LDAPNightlySyncService - LDAP Nightly Sync Task ran for 0 ms. Starting the following URl show nothing no error message, only: User records changed by LDAP nightly sync task https://server:1200/jazz/service/com.ibm.team.repository.common.internal.IFeedService?provider=ldapnightlysync |
4 answers
same here, LDAP lookup via Import Users works, Enable LDAP Nightly Sync is set to "true", but no sign of any nightly sync activity. No info in any of the logs.
Using 2.0.0.1, WAS, RHEL, Oracle, MS Active Directory. Any hints anyone? |
same here, LDAP lookup via Import Users works, Enable LDAP Nightly Sync is set to "true", but no sign of any nightly sync activity. No info in any of the logs. ah, I just learned that after installation / restart, RTC lets at least 86400 seconds (24 hrs) pass before it starts a sync at 1 am... So the first entry in /jazz/service/com.ibm.team.repository.common.internal.IFeedService?provider=ldapnightlysync is not the next morning but the morning after that... Resolved for me by learning patience... |
I see that LDAPNightlySync ran at 10:40 AM. Did you change the LDAP nightly sync interval ?
LDAPnightly sync uses the configuration defined in teamserver.properties. When you configured LDAP via RTC setup wizard, did the "test connection" succeed without errors ? Are you able to view the group information of all the users who are present in the system ? --- Balaji We are using LDPA for RTC 2.0 and (now) everything is working fine. |
There was an issue with ldap sync task with large groups (>1500 users) and active directory.
This issue has been fixed in CLM 3.0. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.