Hi Renjith,
Minh reported this to us through a SAC ticket and, after the ticket resolution, he posted this question to Answers.
Not to leave a question here unanswered, I summarise below how this was solved:
Logs:
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:389' but this host is unreachable due to some DNS/hosts file configuration issue.
Solution:
Disable the follow-referral property in Stash, if not required.
I understand that another possible solution would be if he could have added that domain to the hosts file.
Where is the log?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.