JIRA in Offline mode: [zephyr.je.job.UpgradeCheckerJob] Unable to perform version check

[David Toussaint _Communardo_]

Hi guys,

we are using JIRA in offline mode (settings of the UPM) and also disabled the Zephyr option "Check for software updates". Anyway Zephyr seemingly tries to contact "version.yourzephyr.com" without success. This leads to the error listed below and to Zephyr indexing Job to stop. We could only resolve this by manually reeindexing all zephyr data and the job than seems to work again. But probably only until the version check is perfomed again.

So how to resolve this?

2014-05-09 08:10:25,236 QuartzScheduler_Worker-1 FATAL ServiceRunner    Zephyr for JIRA background job [zephyr.je.job.UpgradeCheckerJob] Unable to perform version check
java.net.UnknownHostException: version.yourzephyr.com
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)

Thanks for your input!

Cheers, David

[Bibek_ikuTeam_ · Accepted solution]

Hello David,

This is a known defect registerd with ID ZFJ-1229 and was resolved under the latest release of Zephyr for JIRA i.e. 2.5.1.
I would suggest you to update to the latest version.This is fix the issue for you.

Thank you,

Best Regards,
Bibek

[SIGERI]

yo tengo el mismo problema tengo jira 7.5 y  Zephyr versión je-4.4.0.44008304

Favorece su apoyo con este problema

nuestra base de datos es oráculo 11g

el log

2020-08-04 10:57:56,947 Caesium-1-2 ERROR ServiceRunner [c.a.bonfire.job.BonfireJobRunnerImpl] Unable to perform version check
java.net.UnknownHostException: version.yourzephyr.com
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:166)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.atlassian.bonfire.job.BonfireJobRunnerImpl.execute(BonfireJobRunnerImpl.java:97)
at com.atlassian.scheduler.compat.clustered.ClusteredJobRunner.runJob(ClusteredJobRunner.java:54)
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:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
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:745)

[LEM]

Hi Bibek,

we have the same issue with Zephyr 2.5.1.25101747 in JIRA 6.2.2.

Any ideas?

Cheers,

Werner