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

后端 未结 2 1315
耶瑟儿~
耶瑟儿~ 2021-01-18 20:42

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

相关标签:
2条回答
  • 2021-01-18 21:10

    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.

    0 讨论(0)
  • 2021-01-18 21:22

    Run this script:

    /opt/jfrog/artifactory/bin/artifactoryManage.sh start
    

    It will show the exact error to you.

    In my case it was java version not updated. So I updated to java 1.8.

    0 讨论(0)
提交回复
热议问题