I can't install and/or start Jira?

[eiger3970]

This question is in reference to Atlassian Documentation: Installation Troubleshooting Guide

Hello, I installed JIRA on Linux 64-bit, but start shows error:

/opt/atlassian/jira/bin $ sudo ./startup.sh 
                .....
          .... .NMMMD.  ...
        .8MMM.  $MMN,..~MMMO.
        .?MMM.         .MMM?.
     OMMMMZ.           .,NMMMN~
     .IMMMMMM. .NMMMN. .MMMMMN,
       ,MMMMMM$..3MD..ZMMMMMM.
        =NMMMMMM,. .,MMMMMMD.
         .MMMMMMMM8MMMMMMM,
           .ONMMMMMMMMMMZ.
             ,NMMMMMMM8.
            .:,.$MMMMMMM
          .IMMMM..NMMMMMD.
         .8MMMMM:  :NMMMMN.
         .MMMMMM.   .MMMMM~.
         .MMMMMN    .MMMMM?.
      Atlassian JIRA
      Version : 7.0.10
                  
If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE:   /opt/atlassian/jira
Using CATALINA_HOME:   /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME:        /opt/atlassian/jira/jre/
Using CLASSPATH:       /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar
Using CATALINA_PID:    /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Tomcat appears to still be running with PID 1403. Start aborted.

[Brian Jones · Accepted solution]

The last line in your log shows it's already running. Typically after you install it starts JIRA. Go to the webpage and see if its running.

If you need to stop just do a "service jira stop" or "sudo service jira stop" or if you want to use the same syntax as how you tried to start "sudo ./shutdown.sh"

[Nic Brough -Adaptavist-]

This can happen if you killed it instead of shutting it down properly (Brian has given you the info for how you should have shut it down)

If you did kill it, then you need to check that it's definitely not running ("ps -ef | grep java" and look for jira/tomcat in the result), and if it isn't, then you can delete the lock file and try again. 

Note that if it is running and you run a second copy, there's a risk of damage to your data.

[eiger3970]

Thanks. Fixed by killing the process.