I am install standalone JIRA 6.21, execute ./start-jira.sh
console print this
Using JIRA_HOME: /var/atlassian/application-data/jira
Server startup logs are located in /opt/atlassian/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian
Using CATALINA_HOME: /opt/atlassian
Using CATALINA_TMPDIR: /opt/atlassian/temp
Using JRE_HOME: /usr/lib/jvm/java-6-oracle
Using CLASSPATH: /opt/atlassian/bin/bootstrap.jar:/opt/atlassian/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
You should have a look at the logs. First check what the atlassian-jira.log file in your "JIRA_home"/logs directory. However, as it's failing so quickly, it might not be getting there at all, so read the catalina.out file it refers to. There will be a reason for failure in one of them
Now that is very odd. Tomcat starts, then is behaving like you have used "kill -9" on it. I've never seen it do that without writing to the application log, OR being killed by a security process of some sort. I'd check the rest of the logs found alongside catalina.out, check very carefully that you are not trying to relocate any logging in Jira (a lot of us relocate the application logs to somewhere more system-standard) and then see if /var/log contains any logs mentioning java or Jira.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot