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"
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.
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot