Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Startup check failed. Jira will be locked Coming up in Jira 8.9.1

sumit.tyagi September 6, 2020

Hello,

I am trying to upgrade jira version of my organization to 8.9.1 and while starting the jira via script getting this error.

"Startup check failed. Jira will be locked"

Below mentioned error is coming on our jira webpage.

Setup: Your jira.home path is a parent of your webapp servlet path

Your jira.home path /opt/jiraupgrade/atlassian-jira-software-8.9.1-standalone can't be the parent directory your webapp servlet path /opt/jiraupgrade/atlassian-jira-software-8.9.1-standalone/atlassian-jira.
Review our documentation for more information on setting your JIRA home

3 answers

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 7, 2020

Changing the path is the wrong answer here.

You need to re-install or move the directories so that they are separated out.  Otherwise you will have problems with your installation, possibly ending in total corruption of your database.

You must never put the install inside the data directory or the data directory inside the install.  In other words:

Never do:

Jira home+ log
+ attachments
+ caches
+ Jira install

or

Jira install
+ bin
+ atlassian-jira
+ log
+ Jira home

 

A lot of us do:

Atlassian directory
+ Jira data
+ Jira home
0 votes
sumit.tyagi September 7, 2020

Thanks for your suggestion. but there is a different error coming now.

 

2020-09-07 09:46:13,489+0000 JIRA-Bootstrap WARN [c.a.jira.startup.DatabaseLauncher] JRADEV-23357: unable to select from the 'MovedIssueKey' entity.
2020-09-07 09:46:13,491+0000 JIRA-Bootstrap ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalStateException: Need to rename the MOVED_ISSUE_KEY table, but there is existing data in it. Please contact Atlassian Support

 

If you can suggest how it can be corrected.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 7, 2020

This is the sort of corruption you can get when you nest home inside install or vice-versa.  Your database is damaged, and you probably need to re-install and recover from a recent backup.

Like sumit.tyagi likes this
0 votes
sumit.tyagi September 7, 2020

I have Setup the correct path in /bin/setenv.sh

 

JAVA_HOME="xxxxxx"

 

And it started fine after that.

Suggest an answer

Log in or Sign up to answer