com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name '#SE - EMEA'

Atlassian JIRA | Sorin Sbarnea (Citrix) | 5 years ago
  1. 0

    As anyone would expect AD administration is not the same as CROWD and changing things in AD is almost always a very bureaucratic process that takes many days. Duplicate groups should only give warnings and not stopping the synctronization. In addition to that, the number of groups with duplicate names cannot be detected at once... so if you have 100 duplicates and it takes 7 days (optimistic) to solve a duplicate group naming issue in corporate Active Directory, it could easily take *years* to setup Crowd. 012-03-23 15:03:05,013 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 13533 ] groups for update in DB cache in [ 356ms ] 2012-03-23 15:03:05,051 scheduler_Worker-0 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronized [ 13533 ] groups in [ 394ms ] 2012-03-23 15:03:05,414 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 13533 ] groups for delete in DB cache in [ 363ms ] 2012-03-23 15:03:05,453 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete in [ 23868ms ] 2012-03-23 15:03:05,467 scheduler_Worker-0 ERROR [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 32770 ]. com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name '#SE - EMEA' at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:133) at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:44) at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAll(UsnChangedCacheRefresher.java:223) at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:621) at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63) at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50) at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

    Atlassian JIRA | 5 years ago | Sorin Sbarnea (Citrix)
    com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name '#SE - EMEA'
  2. 0

    As anyone would expect AD administration is not the same as CROWD and changing things in AD is almost always a very bureaucratic process that takes many days. Duplicate groups should only give warnings and not stopping the synctronization. In addition to that, the number of groups with duplicate names cannot be detected at once... so if you have 100 duplicates and it takes 7 days (optimistic) to solve a duplicate group naming issue in corporate Active Directory, it could easily take *years* to setup Crowd. 012-03-23 15:03:05,013 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 13533 ] groups for update in DB cache in [ 356ms ] 2012-03-23 15:03:05,051 scheduler_Worker-0 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronized [ 13533 ] groups in [ 394ms ] 2012-03-23 15:03:05,414 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 13533 ] groups for delete in DB cache in [ 363ms ] 2012-03-23 15:03:05,453 scheduler_Worker-0 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete in [ 23868ms ] 2012-03-23 15:03:05,467 scheduler_Worker-0 ERROR [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 32770 ]. com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name '#SE - EMEA' at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:133) at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:44) at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAll(UsnChangedCacheRefresher.java:223) at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:621) at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63) at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50) at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

    Atlassian JIRA | 5 years ago | Sorin Sbarnea (Citrix)
    com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name '#SE - EMEA'
  3. 0

    h2. Problem Summary Crowd-integrated applications (e.g. Confluence, JIRA, Stash) can suddenly fail to sync from the Crowd server. This happens seemingly out of the blue without changes to the application. Stacktrace shown on the client application side in logs: {code} 2014-04-29 11:18:38,252 ERROR [scheduler_Worker-5] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 38076417 ]. com.atlassian.crowd.exception.OperationFailedException: Internal error from Crowd server: class com.atlassian.crowd.model.event.AliasEvent is not supported at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleCommonExceptions(RestCrowdClient.java:1308) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.getNewEvents(RestCrowdClient.java:1082) at com.atlassian.crowd.directory.RemoteCrowdDirectory.getNewEvents(RemoteCrowdDirectory.java:682) at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseChanges(EventTokenChangedCacheRefresher.java:73) at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:612) at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63) at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50) at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$1.run(ConfluenceQuartzThreadPool.java:20) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) {code} "com.atlassian.crowd.model.event.AliasEvent" should be invoked when a user's alias has been updated/created/removed. However in cases where this has been observed, the integrated application in question does not have aliasing enabled in Crowd. In some cases, there may be an unrelated application (e.g. Google Apps) where aliasing is enabled. Not sure if this is a red herring. h2. Workaround # In Crowd, re-set the integrated application's name and password. # In the integrated application's user directory configurations, update the application credentials as appropriate This should allow the sync to succeed once more.

    Atlassian JIRA | 3 years ago | Robert Chang [Atlassian]
    com.atlassian.crowd.exception.OperationFailedException: Internal error from Crowd server: class com.atlassian.crowd.model.event.AliasEvent is not supported
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h2. Problem Summary Crowd-integrated applications (e.g. Confluence, JIRA, Stash) can suddenly fail to sync from the Crowd server. This happens seemingly out of the blue without changes to the application. Stacktrace shown on the client application side in logs: {code} 2014-04-29 11:18:38,252 ERROR [scheduler_Worker-5] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 38076417 ]. com.atlassian.crowd.exception.OperationFailedException: Internal error from Crowd server: class com.atlassian.crowd.model.event.AliasEvent is not supported at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleCommonExceptions(RestCrowdClient.java:1308) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.getNewEvents(RestCrowdClient.java:1082) at com.atlassian.crowd.directory.RemoteCrowdDirectory.getNewEvents(RemoteCrowdDirectory.java:682) at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseChanges(EventTokenChangedCacheRefresher.java:73) at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:612) at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63) at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50) at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$1.run(ConfluenceQuartzThreadPool.java:20) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) {code} "com.atlassian.crowd.model.event.AliasEvent" should be invoked when a user's alias has been updated/created/removed. However in cases where this has been observed, the integrated application in question does not have aliasing enabled in Crowd. In some cases, there may be an unrelated application (e.g. Google Apps) where aliasing is enabled. Not sure if this is a red herring. h2. Workaround # In Crowd, re-set the integrated application's name and password. # In the integrated application's user directory configurations, update the application credentials as appropriate This should allow the sync to succeed once more.

    Atlassian JIRA | 3 years ago | Robert Chang [Atlassian]
    com.atlassian.crowd.exception.OperationFailedException: Internal error from Crowd server: class com.atlassian.crowd.model.event.AliasEvent is not supported

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.crowd.exception.OperationFailedException

      Unable to synchronise directory: duplicate groups with name '#SE - EMEA'

      at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships()
    2. com.atlassian.crowd
      DirectoryPollerJobBean.executeInternal
      1. com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:133)
      2. com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:44)
      3. com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAll(UsnChangedCacheRefresher.java:223)
      4. com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:621)
      5. com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63)
      6. com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)
      7. com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29)
      7 frames
    3. Spring Context Support
      QuartzJobBean.execute
      1. org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
      1 frame
    4. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:203)
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
      2 frames