Introduction
Each JFrog Access instance has a unique service_id (e.g. jfac@<random-hex>) that identifies it within the JFrog Platform. Placing an empty marker file named reset_service_id in the bootstrap directory causes Access to generate a new one on the next startup.
This only affects the service identity — keys, tokens, users, and permissions are untouched.
Cause / When to Use
Cloned node — the clone inherits the source's service_id, causing a conflict.
service_id mismatch after DB restore — the running instance no longer matches the DB record.
Resolution
-
Create the marker file and modify the file’s owner:
touch $JF_PRODUCT_HOME/var/bootstrap/access/reset_service_id
chown artifactory:artifactory $JF_PRODUCT_HOME/var/bootstrap/access/reset_service_id
-
Restart Artifactory:
systemctl restart artifactory
-
Verify the new service_id:
curl -u admin:password http://localhost:8082/artifactory/api/system/service_id
Access deletes the marker file automatically after processing. No manual cleanup needed.