Tomcat appears to still be running with PID 14069. Start aborted.

[malin.jayaweera]

Hi, 

I install Jira on CentOs machine when I try to run ./startup.sh I got this error , How can I fix this error, 

jiracodeplait@jira.codeplait.net [/opt/atlassian/jira/bin]# sudo ./startup.sh

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.5.1

If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-085/Troubleshooting+installation

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 14069. Start aborted.
If the following process is not a Tomcat process, remove the PID file and try again:
UID PID PPID C STIME TTY TIME CMD
jira 14069 1 0 04:48 ? 00:02:01 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org
jiracodeplait@jira.codeplait.net [/opt/atlassian/jira/bin]# ^C

[Tinker Fadoua]

@malin.jayaweera 

Did you try to kill the PID and then do systemctl jira stop? 

systemctl status jira to make sure it stopped.

Best,

Fadoua

[Mandia]

Hi @Tinker Fadoua 

Do you know, why we will have this error? I met the same issue as @malin.jayaweera 

Usually we manually kill pid. but i really want to know, why we will have this issue? We want to fix this issue and won't manually kill the Pid

[Tinker Fadoua]

Morning @Mandia 

A stale PID file failed to clear and is preventing startup.

It happens, it is a very common issue with TomCat. Explaining more is beyond my skills. May be a System Administrator can explain to you what happens exactly in TomCat.

All the best,

Fadoua