Directory server synchronization failed
Symptoms
The following exception is reported when starting up Bitbucket Server:
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.
Last modified on Apr 6, 2016
Powered by Confluence and Scroll Viewport.