jfrog
Deb package appears to not honor modified files
Forgive me if this is not the proper place for this, but thought I should bring this up.
We currently run an artifactory service which upgraded from 5.3.2 to 5.4.0 (OSS). It appears that during that upgrade the /etc/opt/jfrog/artifactory/db.properties file was upgraded, or otherwise reverted to original installation state. We are unsure as to the exact specifics at this time, but nonetheless, we had to manually revert that file from a previous backup.
Can I just get verification that that should NOT have happened? Thanks!
Hi @jbaird8,
The db.properties file should not be modified following an upgrade. We've tried to reproduce it internally (on Debian) with no success - the db.properties file was not modified.
Any chance the symlink of the "etc" folder that redirects to /etc/opt/jfrog/artifactory/ was removed or changed? If so, Artifactory cannot detect the previous etc folder. In that case, any other changes made in the etc folder should be affected.
Can you please confirm?
As a result of this, i am tearing apart our lack of puppetization for this server, specifically for the artifactory piece. Give me 24-48 hours and I should be able to get back to you regarding specifics about setup and configuration to hopefully shed more light on this. I will definitely look for symlinks. Thanks!