A binary provider is a storage element based on checksum-based storage systems, and it is possible to use one or more binary providers to build the storage setup.
When you define the $JFROG_HOME/artifactory/var/etc/artifactory/binarystore.xml file, ensure it complies with the values published in JFrog’s documentation (according to the binary providers you are using). You may also want to review the XML syntax to ensure it is correct.
One of the values configured in the binarystore.xml is the file-store directory; regarding the file-store directories, in some cases, we may encounter one of the following errors:
1. 2022-11-24T20:51:41.583Z [jfrt ] [ERROR] [2eb124d82e61dabf] [.p.u.FileBinaryProviderUtil:15] [art-init ] - Could not create dir '/home/nirsh/shards/shard1' 2022-11-24T20:51:41.584Z [jfrt ] [ERROR] [2eb124d82e61dabf] [.p.u.FileBinaryProviderUtil:15] [art-init ] - Could not create dir '/home/nirsh/shards/shard1/_pre' 2022-11-24T20:51:41.586Z [jfrt ] [ERROR] [2eb124d82e61dabf] [wareFileBinaryProviderImpl:160] [art-init ] - Binary store /home/nirsh/shards/shard1 deactivated due to: 503 : Could not find file store folder '/home/nirsh/shards/shard1' 2. 2023-02-04T19:21:35.831Z [1;32m[jfrt ][0;39m [1;31m[ERROR][0;39m [d0aa93a9734d109] [ctoryContextConfigListener:128] [art-init ] -Application could not be initialized: 503 : Could not create file store folder 'mnt/cache/'
Generally, These errors suggest that there is a file-store permission issue. As a result, Artifactory will not be able to start properly, and the above errors will be thrown.