Not able to access Bitbucket

Question

Hello,

Bitbucket Server version  is 4.9.0 on RedHat and received the following error:

The remote authentication server is not available. Please try again later.

Bitbucket installation authenticates against Crowd 2.9.1 and after checking the Crowd logs I see the following error:

2018-11-16 11:28:56,806 http-bio-8095-exec-16 ERROR [crowd.manager.application.ApplicationServiceGeneric] Directory 'TEST - LDAP - CHI - TEST- Repositories' is not functional during authentication of 'assfdfds5'. Skipped.

Restarting the Crowd and  Bitbucket Server does not solve the problem.

Everything was working fine. The issue started this morning.

Dana Shankar_dcpj9t · Answer

when i do an authentication test in Crowd UI I get the following error:

org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - No such object]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - No such object]

Invalid verification.

Dana Shankar_dcpj9t · Answer

this is what i am seeing in the crowd log:

2018-11-16 12:13:47,438 scheduler_Worker-5 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 458756 ] in [ 3ms ]
2018-11-16 12:13:47,440 scheduler_Worker-2 ERROR [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 458755 ].
com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - No such object]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - No such object]
at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:512)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:464)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchUserObjects(SpringLDAPConnector.java:685)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchUsers(SpringLDAPConnector.java:1098)
at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.findAllRemoteUsers(RemoteDirectoryCacheRefresher.java:55)
at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.synchroniseAllUsers(RemoteDirectoryCacheRefresher.java:83)
at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:56)
at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:1127)
at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy32.synchronise(Unknown Source)

Christian Glockner · Answer

Hi Dana,

The logs should also give you more information about why this failed. If you want to set up the authentication from scratch, you can use the lockout recovery procedure to re-gain access to Bitbucket:

https://confluence.atlassian.com/bitbucketserver/lockout-recovery-process-776640158.html

Cheers,

Christian

Premier Support Engineer

Atlassian