Unable to stop Jira service due to "no matching process was found"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
While issuing a stop command in the terminal as described in the doc Start and Stop Jira applications, this error is returned:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
jira@xxxxx bin]$ ./stop-jira.sh
executing as current user
`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.20.9
If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-0820/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/at lassian/jira/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
PID file found but either no matching process was found or the current user does not have permission to stop the process. Stop aborted.
jira@xxxxx bin]$ []Causes
Lacking user file permissions to access the file.
Lacking or wrong PID on the /opt/atlassian/jira/work/catalina.pid file.
Resolution
Follow these steps:
1. Run this on the server's terminal:
ps -ef | grep jira
2. Copy the PID from the Jira that is running. 3. Go to the PID file on this path:
/opt/atlassian/jira/work/catalina.pid
4. Confirm if the PID saved in the file is actually the PID of the Jira running. 5. If it is not, update and save. 6. Try again to stop the Jira service.
Was this helpful?