If you see your Artifactory PID, but no Artifactory webpage, the most likely cause is a lower-level Apache Tomcat error.
Tomcat can typically start Artifactory without any problems. However, the Tomcat server relies on a few system files to run Artifactory. If things get stuck at this stage, it's probable there will be no output in the $ART_HOME/logs/artifactory.log file. If there is Artifactory log output, skip to Stage 3.
Also check the log files in your $ARTIFACTORY_HOME/logs/catalina folder. Chances are good an error was recorded in either the $ART_HOME/logs/catalina/catalina.out file or $ART_HOME/logs/catalina/localhost.<Timestamp>.log file.
Usually the problem will be identified as either a system issue or license error. For example, Tomcat won't start Artifactory if your Artifactory license has expired and you tried to upgrade. Accordingly, before commencing an upgrade, make sure you have a valid license installed. Apache Tomcat won't even start the Artifactory webapp if it detects an expired license.
Tomcat can typically start Artifactory without any problems. However, the Tomcat server relies on a few system files to run Artifactory. If things get stuck at this stage, it's probable there will be no output in the $ART_HOME/logs/artifactory.log file. If there is Artifactory log output, skip to Stage 3.
Also check the log files in your $ARTIFACTORY_HOME/logs/catalina folder. Chances are good an error was recorded in either the $ART_HOME/logs/catalina/catalina.out file or $ART_HOME/logs/catalina/localhost.<Timestamp>.log file.
Usually the problem will be identified as either a system issue or license error. For example, Tomcat won't start Artifactory if your Artifactory license has expired and you tried to upgrade. Accordingly, before commencing an upgrade, make sure you have a valid license installed. Apache Tomcat won't even start the Artifactory webapp if it detects an expired license.