To overcome this behaviour, first check if the Artifactory's secondary nodes are actually upgraded correctly to the version of Primary Artifactory nodes. If the upgrade was correct and successful, and the below error is encountered while starting up the secondary node,
2020-01-20 00:37:52,867 [art-init] [ERROR] (o.a.w.s.ArtifactoryContextConfigListener:96) - Application could not be initialized: Stopping Artifactory, couldn't start Artifactory upgrade, on slave node!
Please run Artifactory upgrade on the master first!
The reason for this issue is due to some hidden marker files that are left as it is in the
$ARTIFACTORY_HOME/etc folder, such as,
We need to take the backup of these marker files and then remove all these .marker files from the
<Artifactory_Home>/etc location and restart the secondary nodes.