Problems with CATALINA_PID and ARTIFACTORY_PID while upgrading Artifactory to the latest version

Question

While upgrading my Artifactory server (free OSS version) from the version 5.2.0 to the latest 5.4.5, I was hit by an ARTIFACTORY_PID problem. After migrating from 5.3.2 to 5

Answer 1

In my case (in a slow virtual machine) the error message from the command artifactoryManage.sh start was:

ERROR: Artifactory Tomcat server did not start in 60 seconds. Please check the logs

The log file told that the only problem was slowness (/var/opt/jfrog/artifactory/logs/artifactory.log):

### Artifactory successfully started (64.802 seconds) ###

The problem was solved by adding a longer timeout to the service definition at /etc/systemd/system/artifactory.service:

[Service]
Environment=START_TMO=120

After editing the service definition, as you know, systemctl daemon-reload was needed.