How to determine which cause is preventing JIRA from starting?

This question is in reference to Atlassian Documentation: Troubleshooting JIRA Startup Failed Error

Would it be possible to add a section on how to determine which cause is the issue? It would be very helpful to have a few quick things to check to see which resolution to pursue, instead of trying each one individually. 

For example. "To determine if the issue is memory related, search the xyz log file located at path /path/to/file/with/all/the/answers for memory issue right here"

 

2 answers

0 votes

It's always "read the log file", if reading the front-end web page fails you. The range of issues you might have (especially if you deviate away from the standard documented isntallation) is so wide, any other approach is pointless.  Read the log file.

I like the Support tool -> Log analyzer, it parses all related logs, drills down for issues and reports it with links to the workarounds/KB. This way it doesn't matter what category it would fall into but allows you to get a list of all current issues.

 

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

268 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot