Synchronization with LDAP fails Only deleted users can be archived


アトラシアン コミュニティをご利用ください。


プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。


Synchronization between Bitbucket Sever and an external LDAP fails.

The following appears in the atlassian-bitbucket.log

2016-05-04 10:28:23,990 ERROR [clusterScheduler_Worker-10]  c.a.c.d.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory [ 111111 ].
java.lang.IllegalArgumentException: Only deleted users can be archived
        at ~[guava-18.0.jar:na]
        at com.atlassian.stash.internal.user.HibernateStashUserDao.archive( ~[bitbucket-dao-impl-4.5.2.jar:na]
        at com.atlassian.stash.internal.crowd.HibernateUserDao.archiveIfNeeded( ~[bitbucket-dao-impl-4.5.2.jar:na]
        at com.atlassian.stash.internal.crowd.HibernateUserDao.rename( ~[bitbucket-dao-impl-4.5.2.jar:na]
        at com.atlassian.stash.internal.crowd.HibernateUserDao.rename( ~[bitbucket-dao-impl-4.5.2.jar:na]
        at ~[crowd-persistence-2.8.4-m2.jar:na]
        at ~[crowd-core-2.8.4-m2.jar:na]
        at$Proxy1471.updateUsers(Unknown Source) ~[na:na]
        at ~[crowd-core-2.8.4-m2.jar:na]
        at ~[crowd-ldap-2.8.4-m2.jar:na]
        at ~[crowd-ldap-2.8.4-m2.jar:na]
        at ~[crowd-ldap-2.8.4-m2.jar:na]
        at ~[crowd-core-2.8.4-m2.jar:na]
        at ~[crowd-core-2.8.4-m2.jar:na]
        at ~[crowd-core-2.8.4-m2.jar:na]
        at [crowd-core-2.8.4-m2.jar:na]
        at com.atlassian.scheduler.core.JobLauncher.runJob( [atlassian-scheduler-core-1.7.0.jar:na]
        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse( [atlassian-scheduler-core-1.7.0.jar:na]
        at com.atlassian.scheduler.core.JobLauncher.launch( [atlassian-scheduler-core-1.7.0.jar:na]
        at com.atlassian.scheduler.quartz2.Quartz2Job.execute( [atlassian-scheduler-quartz2-1.7.0.jar:na]
        at [quartz-2.2.2.jar:na]
        at org.quartz.simpl.SimpleThreadPool$ [quartz-2.2.2.jar:na]
        ... 60 frames trimmed


  1. Disable the external user directory from within Bitbucket Server
  2. Add a new user directory to Bitbucket Server with the same settings the one that has failed the sync but with a different name
  3. Test the sync between the newly added user directory and Bitbucket Server
  4. If the sync is successful, disable the user directory and test the previous directory

The issue should be resolved. If the initial directory still does not sync and new directory does, use the new directory and remove the old one.

最終更新日 2016 年 9 月 15 日


Powered by Confluence and Scroll Viewport.