Why I’m still getting the error “Can’t open PID file /opt/jfrog/artifactory/run/artifactory.pid (yet?) after start: No such file or directory”

Batel Tova
2020-06-21 14:36



Due to the hardening done in systemd RHEL 7.7, the PID file created by Tomcat is not trusted by systemd anymore.


This behavior fixed on Artifactory version 6.14.0 but in case of and upgrade we need to follow these steps in order to change the Artifactory PID:

  1. Stop Artifactory by running the command "systemctl stop artifactory.service".
    * Ignore any errors that may arise, and allow it to run to disable the auto start by systemd.

  2. Stop any running Artifactory Java process that may still be running. Find it using the command:

$ ps -ef | grep java | grep artifactory | grep tomcat 

Rename the existing /etc/opt/jfrog/artifactory/default to the new artifactory.pid file location:

  • export ARTIFACTORY_PID=/var/run/artifactory.pid

Start Artifactory by running the command:

  • $ systemctl start artifactory.service 


In case that this use case persists it means that we still have a pointer to a different PID location. In this case, please check the artifactory.service that can be found under /etc/systemd/system/artifactory.service and make sure that the PID file is pointing to /var/run like the following:


Restart the Artifactory service to point to the new PID