How to determine which cause is preventing JIRA from starting?

[Travis DePuy]

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"

[Jonas Andersson]

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.

[Nic Brough -Adaptavist-]

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.