Unable to access Jira through browser after stopping restore process

[anshu02]

We performed a restore backup process yesterday where we tried to move our production data to UAT environment. but the import process got stuck in between at 58% for 2 hours without any progress, so we decided to stop the import and restart the Jira and again give it a try. 

But after restarting jira i am not able to access it through browser, although Tomcat is in running status. and i can't see any errors in atlassian-jira.log file

Please suggest !

[Charly [DEISER] · Accepted solution]

Hi @anshu02 

I think this should be the correct behaviour because you stopped the process before it finished.

Can you please share the atlassian-jira.log and the catalina.out files? in order to see what could have gone wrong.

Regards

[anshu02]

Hi @Charly [DEISER] 

Please have a look over the logs and let me know if you find something odd, 

10-Apr-2019 08:15:46.544 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.29
10-Apr-2019 08:15:46.547 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 5 2018 13:11:12 UTC
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.29.0
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 3.10.0-693.25.4.el7.x86_64
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /opt/atlassian/jira/jre
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
10-Apr-2019 08:15:46.548 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
10-Apr-2019 08:15:46.553 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /opt/atlassian/jira
10-Apr-2019 08:15:46.554 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /opt/atlassian/jira
10-Apr-2019 08:15:46.554 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties
10-Apr-2019 08:15:46.554 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
10-Apr-2019 08:15:46.554 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms12288m
10-Apr-2019 08:15:46.554 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx12288m
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dhttp.proxyHost=genproxy
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dhttp.proxyPort=8080
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dhttps.proxyHost=genproxy
10-Apr-2019 08:15:46.555 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dhttps.proxyPort=8080
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dfile.encoding=UTF-8
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseG1GC
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-DisableExplicitGC
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dstructure.bulkLinkProcessor.useLinkManager=true
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
10-Apr-2019 08:15:46.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log
10-Apr-2019 08:15:46.557 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
10-Apr-2019 08:15:46.557 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
10-Apr-2019 08:15:46.557 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
"catalina.2019-04-10.log" 49L, 7109C

[anshu02]

Please also have a look at atlassian-jira.log file.  

2019-04-02 10:01:46,120 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,127 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,163 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,208 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,214 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,260 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,298 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,304 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,346 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,387 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:46,396 http-nio-8080-exec-11 url:/ username:jiraadmin url:/secure/MyJiraHome.jspa username:jiraadmin url:/secure/Dashboard.jspa username:jiraadmin WARN jiraadmin 601x158506x1 uugfca 10.233.161.7,10.233.128.11 / [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:52,538 http-nio-8080-exec-7 url:/plugins/servlet/streams username:jiraadmin WARN jiraadmin 601x158549x1 uugfca 10.233.161.7,10.233.128.11 /plugins/servlet/streams [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:01:52,545 http-nio-8080-exec-7 url:/plugins/servlet/streams username:jiraadmin WARN jiraadmin 601x158549x1 uugfca 10.233.161.7,10.233.128.11 /plugins/servlet/streams [c.a.applinks.core.DefaultApplicationLinkService] Couldn't find type id for application link with id 89b26790-57aa-333b-bf1c-dafbbe579218. Link is corrupted
2019-04-02 10:02:40,713 http-nio-8080-exec-13 url:/secure/QuickCreateIssue.jspa username:jiraadmin DEBUG jiraadmin 602x158655x1 uugfca 10.233.161.7,10.233.128.11 /secure/QuickCreateIssue.jspa [c.o.j.groovy.groovyrunner.spring] BeforeInstantiation [bean=com.onresolve.jira.groovy.GroovyFunctionPlugin, type=com.onresolve.jira.groovy.GroovyFunctionPlugin]
@
"atlassian-jira.log" 86753L, 13113648C

[Charly [DEISER]]

Hi,

I don't see anything odd in those traces, maybe if you share the complete files i can dig more, at this point I can only think in two options:

• Create a new empty and clean installation (new server & new db) and use the backup to try to restore the data, if everything is ok destroy the current instance and move forward with the new instance
• Create a support ticket directly in atlassian using this link https://support.atlassian.com/contact/

If you pick option number 2 be ready to provide all the log files because they are going to ask you to provide them.

Regards