Confluence 6.15.7 migrate to cloud error

Vinh Nguyen August 15, 2019

I'm using the migration tool to migrate and encounter this error

The Server being hosted on Linux

Snip of the error - 

Thanks

2019-08-16 16:23:25,020 ERROR [Caesium-1-2] [agent.service.analytics.AnalyticsEventConsumer] error An unhandled exception occurred when processing a AnalyticsEventConsumer job request. Reason: An IO exception occurred when communicating with a downstream service
com.atlassian.migration.agent.okhttp.IOHttpException: An IO exception occurred when communicating with a downstream service
at com.atlassian.migration.agent.okhttp.HttpService.callImpl(HttpService.java:65)
at com.atlassian.migration.agent.okhttp.HttpService.call(HttpService.java:47)
at com.atlassian.migration.agent.okhttp.HttpService.callJson(HttpService.java:33)
at com.atlassian.migration.agent.service.analytics.AnalyticsSenderService.sendAnalyticsEventBatch(AnalyticsSenderService.java:56)
at com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.sendBatchOfEvents(AnalyticsEventConsumer.java:172)
at com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.lambda$submitEvents$0(AnalyticsEventConsumer.java:138)
at com.atlassian.migration.agent.store.jpa.impl.DefaultPluginTransactionTemplate.on(DefaultPluginTransactionTemplate.java:51)
at com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.write(PluginTransactionTemplate.java:26)
at com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.submitEvents(AnalyticsEventConsumer.java:138)
at com.atlassian.migration.agent.service.analytics.AnalyticsEventConsumer.runJob(AnalyticsEventConsumer.java:120)
at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:117)
at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.lambda$runJob$0(JobRunnerWrapper.java:88)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:87)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:71)
at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.runJob(JobRunnerWrapper.java:88)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: api-private.atlassian.com
at java.net.InetAddress.getAllByName0(InetAddress.java:1281)
at java.net.InetAddress.getAllByName(InetAddress.java:1193)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at okhttp3.Dns$1.lookup(Dns.java:40)
at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.java:185)
at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.java:149)
at okhttp3.internal.connection.RouteSelector.next(RouteSelector.java:84)
at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:214)
at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)

1 answer

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 19, 2019

Hello Vinh,

Happy to help!

Users tend to run into that error when the application link was able to establish a connection with the remote application but no response was received. The possible causes for this can be:

  • The remote application is in deadlock - For this, you can check that the remote application is operational, by accessing it as usual from the browser.
  • There is a network connection problem - Use the tools to check the connection with the remote machine.

You can find very detailed information for network connections troubleshooting on the below page:

I hope this helps! Let us know if you have any trouble.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events