nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

kannan raja

[root@server bin]# ./stop-confluence.sh
executing as current user
If you encounter issues starting up Confluence, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide

Server startup logs are located in /home/user/atlassian/confluence/logs/catalina.out
Using CATALINA_BASE:   /home/user/atlassian/confluence
Using CATALINA_HOME:   /home/iuser/atlassian/confluence
Using CATALINA_TMPDIR: /home/user/atlassian/confluence/temp
Using JRE_HOME:        /home/user/atlassian/confluence/jre/
Using CLASSPATH:       /home/user/atlassian/confluence/bin/bootstrap.jar:/home/izaapinn/atlassian/confluence/bin/tomcat-juli.jar
Using CATALINA_PID:    /home/user/atlassian/confluence/work/catalina.pid
PID file found but no matching process was found. Stop aborted.

Accepted answers

All comments

Daniel Eads

Hey Kannan,

This happens sometimes if there were issues starting up (or shutting down cleanly). Looks like the stop process thinks that Confluence is already stopped.

You can check if Confluence is still running by looking for a matching Java process in ps:

ps aux | grep confluence

At this point if you find one, you could kill it with the kill -9 command. Otherwise you should be alright to start Confluence back up.

Cheers,
Daniel

kannan raja

Hi daniel,

Thanks alot please check with command output

[root@server ~]# ps aux | grep confluence
root 14401 0.0 0.0 103316 892 pts/1 S+ 18:02 0:00 grep confluence

kannan raja

Hi dianel,

My issue i have turned off backup plans(daily weekly monthly)

"Otherwise you should be alright to start Confluence back up."

Thanks,

Kannan

kannan raja

[root@server ~]# ps aux | grep confluence
root 14401 0.0 0.0 103316 892 pts/1 S+ 18:02 0:00 grep confluence
[root@server ~]# ^C
[root@server ~]# kill -9 14401
-bash: kill: (14401) - No such process
[root@server ~]# kill -9 103316
-bash: kill: (103316) - No such process
[root@server ~]#

Daniel Eads

The process that returned was actually the search process! Sorry for not calling out to ignore that one. Had Confluence been running, you've have seen a java process (not just the grep one) with a lot of startup flags after it - that process would take a few lines of output.

Regarding backups - there are basically two things to think about:

Confluence itself can write an xml backup on a schedule. I'm guessing this is what you've turned off. It's ok to turn this off if you've got a production-level backup plan in place for your system (see next point)
We suggest backing up the file system on your application server and also using your database's backup tools to back up Confluence's database on a regular interval. Details on that are in this guide.