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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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