ARTIFACTORY:How to resolve ‘Duplicate key errors during startup caused by Federated members associated with the Artifactory instance?’

Yuvarajan Johnpaul
2022-08-11 07:28

Symptoms:

During the Artifactory initialisation, the artifactory-service.log file would return an error message of the following kind. This error indicates a conflicting entry of the Federated Members registered with the Artifactory instance.

 

Caused by: java.lang.IllegalStateException: Duplicate key https://<ARTIFACTORY_HOSTNAME>:<PORT>/artifactory/<REPOSITORY_NAME> (attempted merging values org.jfrog.storage.binstore.ifc.BinaryStoreFederatedMember@624ddafc 

Where the existence of such a configuration conflict can be verified?

I have shared a sample configuration snippet highlighting the duplicate entries. 

User-added image

This configuration would be available in the Artifactory’s Config Descriptor (/var/opt/jfrog/artifactory/etc/artifactory/artifactory.config.latest.xml). 

  1. Use the repository reference indicated in the log snippet.
  2. Search for the conflicting entries from the Config Descriptor.
  3. Remove the duplicate snippet and for the changes to be deployed, we need to Bootstrap the configuration file using the instructions defined here

Note: A restart of the Artifactory is required for the configuration update to take effect. This issue arises in rare scenarios where automation is involved for provisioning the Artifactory repositories that attempt to send creation requests on a loop/concurrent basis, at a specific point in time.