-
Suggestion
-
Resolution: Fixed
-
None
Currently
When an incremental sync fails, the logs are not very helpful in determining the cause. This makes it tough for support and DoS to diagnose these kinds of Crowd issues (which pop up way too much).
2015-09-14 17:16:31,320 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] starting 2015-09-14 17:16:31,321 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 786433 ] 2015-09-14 17:16:31,358 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Incremental synchronisation for directory [ 786433 ] was not completed, falling back to a full synchronisation 2015-09-14 17:16:31,358 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] was not successful, attempting FULL
Solution
Something like this would be more ideal:
2015-09-14 17:16:31,320 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] starting 2015-09-14 17:16:31,321 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 786433 ] 2015-09-14 17:16:31,352 ERROR [scheduler_Worker-7] [directory.ldap.cache.EventTokenChangedCacheRefresher] synchroniseChanges Incremental synchronisation failed: com.atlassian.crowd.event.user.UserRenamedEvent is not supported by incremental sync.
- relates to
-
CONFSERVER-33455 After renaming a user in Active Directory, Confluence syncs that user in as a new user (if and only if Confluence is connected to JIRA or Crowd, which is in turn connected to LDAP)
- Closed
- mentioned in
-
Page Loading...