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

scranthony

Hello,

have the same problem under docker machine. Could you help with please.

https://community.atlassian.com/t5/Confluence-questions/PID-file-found-but-no-matching-process-was-found-Stop-aborted/qaq-p/942493

there is my output inside container:

oot@3eabf7e7505a:/var/atlassian/application-data/confluence# ps -ef | grep confluence
root 8 1 0 11:13 ? 00:00:00 su -s /bin/bash daemon -c /opt/atlassian/confluence/bin/start-confluence.sh -fg
daemon 11 8 99 11:13 ? 00:05:30 /opt/java/openjdk/bin/java -Djava.util.logging.config.file=/opt/atlassian/confluence/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -XX:ReservedCodeCacheSize=256m -XX:+UseCodeCacheFlushing -Dconfluence.context.path= -Datlassian.plugins.startup.options=-fg -Dorg.apache.tomcat.websocket.DEFAULT_BUFFER_SIZE=32768 -Dsynchrony.enable.xhr.fallback=true -Xms1024m -Xmx1024m -Dconfluence.home=/var/atlassian/application-data/confluence -XX:+UseG1GC -Datlassian.plugins.enable.wait=300 -Djava.awt.headless=true -XX:G1ReservePercent=20 -Xloggc:/opt/atlassian/confluence/logs/gc-2019-05-05_11-13-49.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -XX:-PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintTenuringDistribution -DcatalinaConnectorProxyName= -DcatalinaConnectorProxyPort= -DcatalinaConnectorScheme=http -DcatalinaConnectorSecure=false -DcatalinaContextPath= -Dignore.endorsed.dirs= -classpath /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/confluence -Dcatalina.home=/opt/atlassian/confluence -Djava.io.tmpdir=/opt/atlassian/confluence/temp org.apache.catalina.startup.Bootstrap start
root 139 128 0 11:16 pts/0 00:00:00 grep --color=auto confluence

if i'm trying to kill these processes, docker just closes bash connection then.

i tried to restart confluence using:

docker exec -it 3eabf7e7505a sh /opt/atlassian/confluence/bin/stop-confluence.sh

but the error still the same:

root@sss:/var/laradock# docker exec -it 3eabf7e7505a sh /opt/atlassian/confluence/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 /opt/atlassian/confluence/logs/catalina.out
---------------------------------------------------------------------------
Using Java: /opt/java/openjdk/bin/java
Picked up JAVA_TOOL_OPTIONS: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
Picked up JAVA_TOOL_OPTIONS: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
2019-05-05 11:19:39,139 INFO [main] [atlassian.confluence.bootstrap.SynchronyProxyWatchdog] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required
---------------------------------------------------------------------------
Using CATALINA_BASE: /opt/atlassian/confluence
Using CATALINA_HOME: /opt/atlassian/confluence
Using CATALINA_TMPDIR: /opt/atlassian/confluence/temp
Using JRE_HOME: /opt/java/openjdk
Using CLASSPATH: /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/confluence/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.

what's wrong with permissions? it's root already

Diego_88dj6o

Hello there!

Anton, there could be problems with the permissions used for both <confluence-install> and <confluence-home> folders.

We can start by making sure that there is no PID file. We can go here:

/opt/atlassian/confluence/work/catalina.pid

And then, remove the catalina.pid file manually. We must now check the permissions for <confluence-home> and <confluence-install> folders:

1.  Shutdown Confluence
   1. Make sure that the process is not running
   2. You can check that with ps -aux | grep confluence in Linux and via the Process manager in Windows
2. Check permissions for <confluence-home>
   1. The user running Confluence must have *full read/write/execute permission on this folder
   2. You can use the following commands to set this. Keep in mind that the user confluence here is just a placeholder, you must use the user that exists in your system
   3. sudo chown -R confluence:confluence /path/to/<confluence-home>
   4. chmod -R u=rwx,g=rx,o=rx /path/to/<confluence-home>
3. Check permissions for <confluence-install>
   1. The user running Confluence must have *full read/write/execute permission on this folder
   2. You can use the following commands to set this. Keep in mind that the user confluence here is just a placeholder, you must use the user that exists in your system
   3. sudo chown -R confluence:confluence /path/to/<confluence-install>
   4. chmod -R u=rwx,g=rx,o=rx /path/to/<confluence-install>
4. Try starting Confluence with the designated user

The permissions must be propagated to all files and folders within bot <confluence-home> and <confluence-install>. With this in mind, we need to check those before trying to start Confluence once this procedure is finished.

If you are running Confluence as a service, this type of problem (starting up Confluence fails) can happen if a previous restart or start up used another user (such as root) and this fiddled with the permissions for files and folders. When the system tries to use the user created specifically to start the service, the process fails.

Let us know your thoughts Anton!