Good Morning,I have a problem when users authenticate to JIRA.The problem is not always, is random, therefore do not know how to fix it.I guess the first thing I do is check the connection LOGS.The strange thing is that the error happens sometimes, not always.My setup is Microsoft Active Directory and the system has successfully exported users and groups I AD.Any idea what I can do to fix the problem.Thanks for all.

Solved: Error in connection Vs Active Directory

Good morning,

I put the partial content of file access-log from \Atlassian\JIRA\logs.

Look at the user ES101709 connect corretly and next time not connect.

Best Regards.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

I can't see the actual error in there, but it might be volume - would it be possible to shorten it to just the line where the user is ok, then fails on the next one?

More importantly, are there errors in the application log when this happens?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Thanks for your tracing, I decide attach the complete file of log for your best answer.

Thanks for All and best regards.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

No, we need to see the application log. And just the success and failure lines in the connection log - I can't see what's happening in the stuff you've posted.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Sorry, how are the application log in the system.

Are two possibilities:

C:\PROGRAM FILES\ATLASSIAN\APPLICATION DATA\JIRA\LOG\

C:\PROGRAM FILES\ATLASSIAN\JIRA\LOGS\

Thanks for all.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Probably the first, but we don't know what your "JIRA home" is. The file you're looking for is atlassian-jira.log

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Thats correct, I'm see the log and appears several errors of same kind

2016-04-06 19:02:30,461 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2016-04-06 19:02:30,461 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2016-04-06 19:02:31,633 Caesium-1-2 INFO ServiceRunner     [c.a.c.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=operacions,dc=local,dc=es took 1107ms
2016-04-06 19:02:31,633 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 10000 ] in [ 1172ms ]
2016-04-06 19:02:31,649 Caesium-1-2 ERROR ServiceRunner     [c.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory
com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: operacions.local.es:389 [Root exception is java.net.ConnectException: Connection refused: connect]]
   at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:441)
   at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:476)
   at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:459)
   at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findAllUserGuids(MicrosoftActiveDirectory.java:841)
   at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.validateAndReturnGuidsToAddAndDelete(UsnChangedCacheRefresher.java:296)
   at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseUserChangesGuid(UsnChangedCacheRefresher.java:320)
   at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseUserChanges(UsnChangedCacheRefresher.java:381)
   at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseChanges(UsnChangedCacheRefresher.java:124)
   at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:1097)
   at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:76)
   at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.synchronizeDirectory(JiraDirectorySynchroniser.java:77)
   at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:52)
   at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
   at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
   at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:453)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:447)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:394)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:279)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:275)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:78)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:70)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:40)
   at java.lang.Thread.run(Thread.java:745)
Caused by: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: operacions.local.es:389 [Root exception is java.net.ConnectException: Connection refused: connect]]
   at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:216)
   at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:385)
   at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:309)
   at com.atlassian.crowd.directory.ldap.SpringLdapTemplateWrapper$4.timedCall(SpringLdapTemplateWrapper.java:198)
   at com.atlassian.crowd.directory.ldap.SpringLdapTemplateWrapper$4.timedCall(SpringLdapTemplateWrapper.java:195)
   at com.atlassian.crowd.directory.ldap.SpringLdapTemplateWrapper.invokeWithContextClassLoader(SpringLdapTemplateWrapper.java:89)
   at com.atlassian.crowd.directory.ldap.SpringLdapTemplateWrapper.search(SpringLdapTemplateWrapper.java:195)
   at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:405)
   ... 23 more
Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: operacions.local.es:389 [Root exception is java.net.ConnectException: Connection refused: connect]]
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreImpl(AbstractLdapNamingEnumeration.java:237)
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreReferrals(AbstractLdapNamingEnumeration.java:347)
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreImpl(AbstractLdapNamingEnumeration.java:227)
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMore(AbstractLdapNamingEnumeration.java:189)
   at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:365)
Caused by: javax.naming.CommunicationException: operacions.local.es:389 [Root exception is java.net.ConnectException: Connection refused: connect]
   at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:95)
   at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:150)
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreReferrals(AbstractLdapNamingEnumeration.java:325)
   at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreImpl(AbstractLdapNamingEnumeration.java:227)
   ... 34 more
   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
   at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
   at java.net.Socket.connect(Socket.java:589)
   ... 2 filtered
   at java.lang.reflect.Method.invoke(Method.java:497)
   at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350)
   at com.sun.jndi.ldap.Connection.<init>(Connection.java:203)
   at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137)
   at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:64)
   at com.sun.jndi.ldap.pool.Connections.getOrCreateConnection(Connections.java:203)
   at com.sun.jndi.ldap.pool.Connections.get(Connections.java:144)
   at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Pool.java:148)
   at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(LdapPoolManager.java:329)
   at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1605)
   at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2746)
   at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
   at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
   at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)
   at com.sun.jndi.url.ldap.ldapURLContextFactory.getObjectInstance(ldapURLContextFactory.java:52)
   at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:601)
   at javax.naming.spi.NamingManager.processURL(NamingManager.java:381)
   at javax.naming.spi.NamingManager.processURLAddrs(NamingManager.java:361)
   at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:333)
   at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:114)
   ... 37 more

Thanks for the support

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Ok, that pretty much answers it - JIRA's connection to your active directory is being broken, so it can't authenticate them.

You'll need to read the AD logs to find out why AD is refusing the connection (it may be network related, but "connection refused" usually means "the server is there, but it's not letting me in", rather than "can't get to server")

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Sorry I've located a log in de just moment that user are authenticate in de system JIRA

the conncret log is:

2016-04-21 15:27:04,958 analyticsEventProcessor:thread-1 ERROR OASYSCARM1     [c.a.a.client.listener.ProductEventListener] Failed to send analytics event com.atlassian.analytics.api.events.MauEvent@b3985b64
com.atlassian.cache.CacheException: com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
   at com.atlassian.cache.memory.DelegatingCache$DelegatingLoadingCache.get(DelegatingCache.java:330)
   at com.atlassian.analytics.client.serialize.EventSerializer.hashEmailPropertyForMauEvent(EventSerializer.java:111)
   at com.atlassian.analytics.client.serialize.EventSerializer.toAnalyticsEvent(EventSerializer.java:84)
   at com.atlassian.analytics.client.listener.ProductEventListener$1.run(ProductEventListener.java:112)
   at com.atlassian.sal.core.executor.ThreadLocalDelegateRunnable.run(ThreadLocalDelegateRunnable.java:38)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
   at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
   at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
   at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
   at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.hashInternal(BcryptAnalyticsEmailHasher.java:45)
   at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.hash(BcryptAnalyticsEmailHasher.java:40)
   at com.atlassian.analytics.client.serialize.EventSerializer$1.load(EventSerializer.java:58)
   at com.atlassian.cache.memory.MemoryCacheManager$3$1.load(MemoryCacheManager.java:132)
   at com.atlassian.cache.memory.BlockingCacheLoader.load(BlockingCacheLoader.java:51)
   at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527)
   at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2319)
   at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2282)
   at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197)
   at com.google.common.cache.LocalCache.get(LocalCache.java:3937)
   at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3941)
   at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4824)
   at com.atlassian.cache.memory.DelegatingCache$DelegatingLoadingCache.get(DelegatingCache.java:324)
   ... 9 more
Caused by: java.lang.NullPointerException
   at java.io.Reader.<init>(Reader.java:78)
   at java.io.InputStreamReader.<init>(InputStreamReader.java:72)
   at org.apache.commons.io.IOUtils.copy(IOUtils.java:1407)
   at org.apache.commons.io.IOUtils.copy(IOUtils.java:1433)
   at org.apache.commons.io.IOUtils.toString(IOUtils.java:585)
   at com.atlassian.analytics.client.hash.reader.RemoteHashingInstructionsReader.readInstructions(RemoteHashingInstructionsReader.java:27)
   at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher$HashingInstructionsResettableLazyReference.create(BcryptAnalyticsEmailHasher.java:154)
   at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher$HashingInstructionsResettableLazyReference.create(BcryptAnalyticsEmailHasher.java:144)
   at com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:140)
   at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321)
   at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
   at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
   at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
   at com.atlassian.analytics.client.hash.BcryptAnalyticsEmailHasher.readRemoteInstructions(BcryptAnalyticsEmailHasher.java:123)
   at com.atlassian.analytics.client.upload.RemoteFilterRead.execute(RemoteFilterRead.java:61)
   at com.atlassian.scheduler.compat.local.LocalOnlyPluginJob.execute(LocalOnlyPluginJob.java:30)
   at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:110)
   at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:80)
   at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
   at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
   at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:453)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:416)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:279)
   at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:275)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:78)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:70)
   at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:40)
   ... 1 more

The problem is the same?

Thanks , I'm going to check

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Hi, have a any configuration on change de time (for example) with the JIRA connect versus AD.

This kind of request is parametrized in cicle of ms, seconds. Is possible that request force a AD at reject the connection.

I don't know what is the problem in this case.

The Log of DC machine is clean the errors and warnings.

Any idea.

Thanks.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

I'm really sorry, I don't understand the first couple of lines of that comment.

I don't know what the problem here is either. Your AD server is not responding to JIRA when it makes a request - that needs to be fixed. I don't know if it's a networking issue, or the AD server (although it looks like the AD server, as the error message is "request refused" rather than "cannot connect")

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Hi Nic, i test another once the configuration and not is correct the obtains users and groups.

This is a screenshot of the error, i dont know the error because have one user autenticate in this moment.

Error.PNG

My configuration is follow:

configuracion.PNG

Any Idea, why happens??.

Thanks for all.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

I'm afraid I can't tell you why the AD server is refusing the connection. It looks like the settings are wrong.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Hi Nic, I solved the problem with your indications, is correct, the problem reside in one DNS.

I've a two resolution DNS, one is deprecated and not include the users AC.

Thanks for elp me and the support.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Forums

Product Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Error in connection Vs Active Directory

2 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events

Forums

Product Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Error in connection Vs Active Directory

2 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events

Welcome to the new Atlassian Community