Directory server synchronization failed
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following exception is reported when starting up Bitbucket Server:
1
2
3
4
5
6
7
8
9
2013-11-08 00:54:16,702 ERROR [scheduler_Worker-8] c.a.c.d.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory [ 229377 ].
com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: GR.LOCAL:389; nested exception is javax.naming.CommunicationException: GR.LOCAL:389 [Root exception is java.net.UnknownHostException: GR.LOCAL]
...
Caused by: org.springframework.ldap.CommunicationException: GR.LOCAL:389; nested exception is javax.naming.CommunicationException: GR.LOCAL:389 [Root exception is java.net.UnknownHostException: GR.LOCAL]
...
Caused by: javax.naming.CommunicationException: GR.LOCAL:389
...
Caused by: java.net.UnknownHostException: GR.LOCAL
...Cause
The LDAP search received a follow-referral to another domain controller at 'GR.LOCAL' but this host is unreachable due to some DNS configuration issue.
Resolution
Disable the follow-referral property in Bitbucket Server, if not required.
If required, check the hosts file and enter the above host to it.
Was this helpful?