$ select count(*) as “Nodes: No-SHA256” from nodes where node_type=1 and sha256 is NULL;
$ select count(*) as “Binaries: No-SHA256" from binaries where sha256 is NULL;
If the output is not zero, that means there are artifacts without SHA-256 checksum calculated in the database.
Step 2: Hence, we need to perform a sha-256 migration by adding the below parameters mentioned in the JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties
file on each node of your Artifactory instance.
Perform rolling restart of Artifactory after updating the artifactory.system.properties file.
By adding the above attributes to artifactory.system.properties, SHA-256 value will be generated for each artifact for which it is currently not having an entry on the database.
Once the migration is completed, we will be able to view the packages page on the UI without any warnings and the error message observed on the logs should be eliminated.
Note: Post SHA256 Migration, it is recommended to remove all SHA256 related system properties after the migration has completed and perform a restart.
$ select count(*) as “Binaries: No-SHA256" from binaries where sha256 is NULL;
If the output is not zero, that means there are artifacts without SHA-256 checksum calculated in the database.
Step 2: Hence, we need to perform a sha-256 migration by adding the below parameters mentioned in the JFROG_HOME/artifactory/var/etc/artifactory/artifactory.system.properties
file on each node of your Artifactory instance.
##SHA2 Migration block artifactory.sha2.migration.job.enabled=true artifactory.sha2.migration.job.queue.workers=5
Perform rolling restart of Artifactory after updating the artifactory.system.properties file.
By adding the above attributes to artifactory.system.properties, SHA-256 value will be generated for each artifact for which it is currently not having an entry on the database.
Once the migration is completed, we will be able to view the packages page on the UI without any warnings and the error message observed on the logs should be eliminated.
Note: Post SHA256 Migration, it is recommended to remove all SHA256 related system properties after the migration has completed and perform a restart.