Jira stopped. Now can't start


The jira was configured and working fine till yesterday but it now stopped and can't start again. Here is the error message when I tried to start


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.

Unable to read PID file. Start aborted.


Thansk for looking into this. 


2 answers

1 accepted

7 votes
Accepted answer

Thanks Sam for quick revert. I really appreicate your help. Finally I am able resolve the issue. I am posting answer here so it may help someone else with same problem.

Goto: /opt/atlassian/jira/work/ directory and delete catalina.pid file. ( Due to some strange reason, the pid proces was killed but file not removed)

stop and start jira again and it works.


Found this while trying to get my Confluence instance to start too. Thanks for asking!

0 votes

Hi Nav,

What command are you using to start JIRA?

The 'Existing PID file found during start' message inticates there might be reminants of existing JIRA/tomcat process that you need to kill/remove.

Also, take look at this thread, which is a similar (but not exactly the same) problem. The answers from Brian Jones and Nic Brough might help.

Hi Sam

Thanks for the quick revert.

I use any one of these commands to start Jira. It worked until today.

service jira start



 I had looked at this thread earlier but it wouldn't help as question from eiger3970 thread snippet tells secific existing PID number but in my case it says later 'Unable to read PID file'.

I see messaging coming from catalina.sh.

Also when I try to stop the jira ( assume PID still running), it says

 "PID file found but no matching process was found. Stop aborted"

The general advice on the other thread about checking for running processes and killing them is really what I was referring to. I spotted that the snippet showed slighlty different error from yours.

Anyway, have a look at this Knowledge Base article, particuarly the diagnosis part, and see if it helps you fix.


Also, take note of the info in the admin users guides about starting/stopping JIRA (assuming you are on JIRA v7) as there are different commands depending on whether you installed JIRA as a service or not:


p.s. I edited your replies above to remove blank space.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,532 views 15 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you