Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,945
Community Members
 
Community Events
176
Community Groups

JIRA Upgrade 8.6.1 to 8.18.1. Will not start FATAL : Startup check failed. Jira will be locked.

I have upgraded from JIRA 8.6.1 to 8.18.1 and now JIRA will not start up.

I followed the normal installation instructions from the atlassian-jira-core-8.18.1-x64.bin file and this gave no errors. Previous similar upgrades have worked fine.

The only error I have is the following in catalina.out 

2021-07-28 19:12:45,322+0100 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.

No other log files show any errors. I do have a warning about not using SSL for MySQL connection but I am pretty sure this was present before the upgrade and is not the problem.

This is running on Lubuntu 18.04LTS, using a MySQL database with the mysql driver mysql-connector-java-5.1.46-bin.jar installed in the lib directory.

What can I do to investigate and resolve this issue?

1 answer

Update - I rolled back to 8.6.1 and all is working again now.

I would like to upgrade to 8.18,1 if possible but with it failing with just that FATAL error message with no clue what the actual issue is - it makes it rather impossible.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events