Artifactory Does Not Start Up
There are no log file entries in $ARTIFACTORY_HOME/logs/artifactory.log
|Something within your |
$ARTIFACTORY_HOME or $CLUSTER_HOME directory is either not defined, or misconfigured
|In some cases in which the $|
ARTIFACTORY_HOME directory tree is not validly constructed, log file entries are written to $ARTIFACTORY_HOME/logs/catalina/localhost/<date>/logs. Check the contents of this file to see which specific errors were logged.
The log says "Stopping Artifactory start up ,another server running converting process".
|You are upgrading more than one server at a time.|
|When upgrading your system, make sure you complete the upgrade process on one server before starting to upgrade the next one.|
The log says "Stopping Artifactory start up ,another server with different version has been found".
|You are trying to install different versions of Artifactory into the same system.|
|Make sure that all the instances of Artifactory installed in your system are the same version.|
The log says "Stopping Artifactory since duplicate node ids have been found in registry. If you restarted this server, make sure to wait at least 30 seconds before re-activating it"
This may happen in one of two cases:
- Two servers are configured into your system with the same
node.id specified in the
- You have shut down an Artifactory server and tried to restart it within 30 seconds.
Make sure that all servers within your Artifactory HA installation have a unique
Shut down your server and wait at least 30 seconds before you restart it.
An exception is thrown for "java.lang.IllegalStateException: Provided private key and latest private key fingerprints mismatch"
During startup, Artifactory fails to start and an error is thrown:
java.lang.IllegalStateException: Provided private key and latest private key fingerprints mismatch.
Artifactory tries to validate and compare access keys' fingerprint that reside on Artifactory's database and the local file system. If the keys do not match, the exception above will be thrown along with the mismatching fingerprint IDs.
A. During an attempted upgrade/installation of an Artifactory HA cluster node.
B. When setting up your circle of trust, something has gone wrong and the different participating Artifactory installations do not share the same private key and root certificate. This causes cross-site authentication to fail since keys between the different sites cannot be validated.
Follow the steps below to make sure that all instances in your circle of trust have the same private key and root certificate:
Key rotation will invalidate any issued access tokens
The procedure below will create new key pairs which in turn will invalidate any existing Access Tokens.
Copy the private key and root certificate files from the first Artifactory instance to a location on your file system that is accessible by all other instances/nodes that are in your circle of trust.
- Before bootstrapping, for each of the other instances/nodes:
- Delete the existing private key and root certificate files (
root.cert) from the
Create the $ARTIFACTORY_HOME/access/etc/
access.bootstrap.config with the following contents:
Add the following JVM property to
Start up the new instance and verify that the artifactory.log file shows the following entry:
*** Forcing replacement of the root private key and certificate ***
Delete the JVM property you added to $ARTIFACTORY_HOME/bin/artifactory.default in step c.
Artifactory Starts Up But Remains Offline
The log says "Changing Artifactory mode to offline since the server is configured as HA but the license does not exist or is not an HA License"
|Your server does not have a valid HA license installed|
|Install a valid HA license in your server and restart it|
The log says "Changing Artifactory mode to offline since the local server is running as HA but found no HA server in registry."
|You are starting an Artifactory server as an HA installation, however you already have an Artifactory Pro (or OSS version) running within the same system.|
|Make sure your system is consistent - either you have a set of Artifactory Pro instances running separately, or you all of your servers are configured as Artifactory HA|
The log says "Could not find cluster properties"
$CLUSTER_HOME/ha-etc/cluster.properties file is not defined.
|When installing Artifactory HA, you need to manually create a |
$CLUSTER_HOME directory and the
$CLUSTER_HOME/ha-etc/cluster.properties file. For details please refer to Configuring the Cluster.
Artifactory Starts Up But Not as an HA Installation
Artifactory starts up as an instance of Artifactory Pro
|You have not created a valid |
|Create a valid |
$ARTIFACTORY_HOME/etc/ha-node.properties file as described in Configuring a Cluster Node.
A Cluster Node Does Not Synchronize with Other Nodes
The node does not contain the right bootstrap bundle
|The node was installed without the right bootstrap bundle (bootstrap.bundle.tar.gz) or no bootstrap bundle at all.|
Install the right bootstrap bundle using the following procedure:
1) Shutdown the node
2) Delete the
3) Delete the
4) Copy the bootstrap bundle you created on the primary node,
bootstrap.bundle.tar.gz, to the
$ARTIFACTORY_HOME/etc folder on the secondary node.
5) Start up the node