Closed EvertonSA closed 1 year ago
@EvertonSA Thanks for reporting this issue. We will look into this issue internally and get back to you.
Hi @EvertonSA
To fix this issue, please remove the following parameters from your custom binarystore.xml:
<binariesDir>data/filestore</binariesDir>
<tempDir>temp</tempDir>
These parameters (which are part of the templates published in JFrog docs) are redundant and create a conflict with the filesystem structure of Artifactory with splitServicesToContainers enabled.
Following the removal of these parameters from your binarystore.xml, Artifactory will use the code default location (/opt/jfrog/artifactory/var/data/artifactory/filestore), and upload of binaries should work as expected.
I'll appreciate your response. Yarden JFrog Support.
@gitta-jfrog right,
if I remove this, does it mean that we will not be able to use Direct (Eventual-less) uploads anymore?
Hi @EvertonSA
Removing these values should not impact the chain template you are using.
When using a Direct Chain Template, Artifactory needs the binariesDir/temp location only during the upload operation. Following the removal of binariesDir and tempDir from the binarystore.xml (and restart Artifactory nodes), Artifactory will use the default location for temp files during uploads ($JFROG_HOME/artifactory/var/data/artifactory/filestore)
Hope this clarifies.
I hereby confirm the solution works.
After upgrading our production instance to new jfrog helm chart, we notice that all services are deployed correctly, but jfrog stop working when uploading to azure storage account.
setting splitServicesToContainers to false make it work again.
I want to have splitServicesToContainers to true, because it's the default. Can you help me to fix? The open ticket to support is https://support.jfrog.com/s/tickets/5006900006gvRe5/migrating-from-75911-to-7637-breaks-azure-storage-account
The application logs indicate an error on the following: