Due to the hardening done in systemd RHEL 7.7, the systemd is no longer trusted by the Tomcat-created PID file. This behavior was fixed for Artifactory versions 6.14 and above. However, when upgrading from a version below this, you'll need to follow these instructions to change your Artifactory PID:
-
Stop Artifactory by running the command:
systemctl stop artifactory.service
Should any error messages be generated, ignore them, allowing the command to run, which will disable the systemd auto-start.
-
Stop any Artifactory Java processes that are still running. Find these by 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
Persistence of this issue beyond these steps means you still have a pointer being directed to a different PID location. Should this be the case, have a look at your artifactory.service, which can be found in /etc/systemd/system/artifactory.service, and make sure that your PID file is pointing to /var/run, just as you see here:
Restart your Artifactory service for the change to take effect.