Artifactory 6.x

Using the latest version?
JFrog Platform User Guide

Expand all   Collapse all

JFrog Artifactory 6.x Documentation
To get the latest version, go to the JFrog Unified Platform

Skip to end of metadata
Go to start of metadata

Artifactory Does Not Start Up

 There are no log file entries in $ARTIFACTORY_HOME/logs/artifactory.log
Cause
Something within your $ARTIFACTORY_HOME or $CLUSTER_HOME directory is either not defined, or misconfigured
Resolution
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.
 After restarting a cluster node which uses a shared NFS mount, the startup fails

Relevant only when installing Artifactory version 5.6.x and below.

Cause

The $NFS_MOUNT/ha-etc still contains the bootstrap bundle archive used for the last upgrade. Artifactory tries redeploy the archive's contents to its respective locations under the $ARTIFATORY_HOME and runs in a conflict. The jfrog-access.bootstrap.log shows the following output:


[jfrog-access] [INFO ] Found bootstrap bundle file: /clusterhome/ha-etc/bootstrap.bundle.tar.gz
[jfrog-access] [INFO ] Deploying bootstrap bundle file to: /var/opt/jfrog/artifactory
Resolution

Delete the bootstrap bundle archive from the $NFS_MOUNT/ha-etc folder. Restart the node and the startup should succeed.

 The log says "Stopping Artifactory start up ,another server running converting process".
Cause
You are upgrading more than one server at a time.
Resolution
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".
Cause
You are trying to install different versions of Artifactory into the same system.
Resolution
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"
Cause

This may happen in one of two cases:

  1. Two servers are configured into your system with the same node.id specified in the $ARTIFACTORY_HOME/etc/ha-node.properties file.
  2. You have shut down an Artifactory server and tried to restart it within 30 seconds.
Resolution

Make sure that all servers within your Artifactory HA installation have a unique node.id value.

Shut down your server and wait at least 30 seconds before you restart it.

 The log says "Node could not join cluster. A Configuration mismatch was detected: Incompatible partition count! expected: 8, found: 1 Node is going to shutdown now!"
Cause

A new node has new Artifactory Hazelcast system property values defined $ARTIFACTORY_HOME/etc/artifactory.system.properties file and it is trying to join a cluster with nodes with different Hazelcast property values.

Resolution

Make sure that all servers within your Artifactory HA installation have the same values.

Shut down your cluster (not rolling restart), start the nodes one by one.

Page Contents


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"
Cause
Your server does not have a valid HA license installed
Resolution
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."
Cause
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.
Resolution
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"
Cause
Your $CLUSTER_HOME/ha-etc/cluster.properties file is not defined.
Resolution
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 UI login still prompts for credentials after a successful attempt 

 Artifactory version 5.x and above running with Hazelcast allow UI logins made without sticky session/persistance configuration required on the load balancer.
Cause

You have not opened the required Hazelcast ports (Artifactory's nodes syncronized memory component) which are configured under:

$ARTIFACTORY_HOME/etc/ha-node.properties file

Resolution
  1. Open the membership ports on your operating system level
  2. Ensure communication to the newly opened ports from the membering cluster nodes
  3. Verify that the UI login works now (no restart is needed)

Artifactory Starts Up But Not as an HA Installation

 Artifactory starts up as an instance of Artifactory Pro

Relevant only when installing Artifactory version 5.6.x and below.

Cause
You have not created a valid $ARTIFACTORY_HOME/etc/ha-node.properties file
Resolution
  1. Shutdown the node
  2. Delete the $ARTIFACTORY_HOME/access folder
  3. Delete the $ARTIFACTORY_HOME/etc/security/access folder
  4. Delete $ARTIFACTORY_HOME/etc/security/communication.key
  5. Delete $ARTIFACTORY_HOME/etc/security/artifactory.key
  6. Delete $ARTIFACTORY_HOME/etc/binarystore.xml
  7. Delete $ARTIFACTORY_HOME/etc/db.properties
  8. Delete $ARTIFACTORY_HOME/etc/cluster.id
  9. Copy the bootstrap bundle you created on the primary node, bootstrap.bundle.tar.gz, to the $ARTIFACTORY_HOME/etc folder on the secondary node.
  10. Ensure that the bundle is owned by artifactory user (chown artifactory:artifactory bootstrap.bundle.tar.gz)
  11. Create a valid $ARTIFACTORY_HOME/etc/ha-node.properties file as described in Installing Artifactory HA.
  12. Start up the node

A Cluster Node Does Not Synchronize with Other Nodes

 The log says "Could not decrypt encrypted password in ${ARTIFACTORY_HOME}/etc/db.properties".
Cause

There is a Master Key mismatch, and it cannot decrypt the DB props file.

The Master key is an AES 128 bit secret key that's used by Artifactory to securely synchronize files between cluster nodes. It is responsible to encrypt and decrypt the shared data in the database.

Resolution
Copy the $ARTIFACTORY_HOME/etc/security/master.key from the primary node to the secondary node.
 The log says "Your database password in ${ARTIFACTORY_HOME}/etc/db.properties is encrypted, but no ${ARTIFACTORY_HOME}/etc/security/master.key file exists".
Cause

There is a Master Key is missing.

The Master key is an AES 128 bit secret key that's used by Artifactory to securely synchronize files between cluster nodes. It is responsible to encrypt and decrypt the shared data in the database.

Resolution
Copy the $ARTIFACTORY_HOME/etc/security/master.key from the primary node to the secondary node.
 The node did not start with a bootstrap bundle or with a wrong bootstrap bundle

Relevant only when installing Artifactory version 5.6.x and below.

Cause
The node was installed without the right bootstrap bundle (bootstrap.bundle.tar.gz) or no bootstrap bundle at all.
Resolution

Install the right bootstrap bundle using the following procedure:

  1. Shutdown the node
  2. Delete the $ARTIFACTORY_HOME/access folder
  3. Delete the $ARTIFACTORY_HOME/etc/security/access folder
  4. Delete $ARTIFACTORY_HOME/etc/security/communication.key
  5. Delete $ARTIFACTORY_HOME/etc/security/artifactory.key
  6. Delete $ARTIFACTORY_HOME/etc/binarystore.xml
  7. Delete $ARTIFACTORY_HOME/etc/db.properties
  8. Delete $ARTIFACTORY_HOME/etc/cluster.id
  9. Copy the bootstrap bundle you created on the primary node, bootstrap.bundle.tar.gz, to the $ARTIFACTORY_HOME/etc folder on the secondary node.
  10. Ensure that the bundle is owned by artifactory user (chown artifactory:artifactory bootstrap.bundle.tar.gz)
  11. Start up the node

Upgrading from Version 5.4.5 or Below to Version 5.5 or Above Fails

 The log says "To upgrade your HA installation to this version, you first need to upgrade to version 5.4.6 which implements changes required to accommodate a database schema change."
Cause
Artifactory 5.5 introduces a change to the database schema. To upgrade to this version or above, the database must first be migrated to the new schema
Resolution
Artifactory 5.4.6 implements a process that performs the required database schema migration. To upgrade to version 5.5 or above from version 5.4.5 or below, you first need to upgrade to version 5.4.6 using the normal upgrade procedure according to your installation type, and then upgrade to your desired version (5.5 or above), also using the normal upgrade procedure.



  • No labels

JFrog.com | Documentation | Featured | Have a question? Want to report an issue? Contact JFrog support