How to avoid losing ownership after upgrading Artifactory RPM version to 4.0.0 (fixed in 4.0.1)

Artifactory 4.0.0 upgrade can cause your files to lose their ownership (fixed on 4.0.1).  Before the upgrade you can see if you have the problem with the following command:

awk ‘FS=”:” {print $3 ” ” $1}'</etc/passwd|sort -n

You should see a number followed by artifactory.  Look above this, if there are any numbers missing between 500 and the current artifactory number you’ll run into this problem.  

How to upgrade if you have this problem:

Make a note of artifactory’s number from the previous command.

run: rpm -e artifactoryrun: useradd -u <number from above> artifactory

 

Then follow the instructions on https://bintray.com/jfrog/product/artifactory/download to install the rpm

If you have already done the upgrade and now artifactory won’t start, you’ll see something like:

 

service start artifactory/opt/jfrog/artifactory/tomcat/bin/setenv.sh: line 3: /etc/opt/jfrog/artifactory/default: Permission denied** ERROR: Artifactory Tomcat server did not start. Please check the logs

 

If that is the case, the easiest way to fix the problem is:

 

chown -R artifactory /etc/opt/jfrog/artifactory /var/opt/jfrog/artifactory /var/opt/jfrog/run

 

You may have to reinstall artifactory after doing the chown.