artifactoryentitlements

Artifactory OSS won't start, log shows "Failed executing GetEntitlements, Server responded with an invalid status 404 UNIMPLEMENTED"


I just installed Artifactory OSS 7.84.15 on a Windows Server 2019 IBM cloud machine. I only changed 4 options: I changed 2 default ports that conflict with other Tomcat installs on this machine, I changed the database used to the embedded Derby because this is just a proof of concept, and I configured the IP to 127.0.0.1 because I saw it use an IPv6 address somewhere during troubleshooting and I read on a different question that might cause issues.

When starting Artifactory, whether that's as a service or from the artifactory.bat file, after a minute or two of waiting I end up with the below error in my log output:

2024-06-24T07:59:46.763Z [1;33m[jfac ][0;39m [1;31m[ERROR][0;39m [                ] [o.j.c.ExecutionUtils:60       ] [jf-common-pool-2    ] - Uncaught exception.
org.jfrog.jfconnect.client.exception.JFConnectClientException: Could not init the client
    at org.jfrog.jfconnect.client.EntitlementsClientImpl.init(EntitlementsClientImpl.java:36)
    at org.jfrog.jfconnect.client.JFConnectClientImpl.init(JFConnectClientImpl.java:63)
    at org.jfrog.access.server.service.license.EntitlementsService.lambda$init$1(EntitlementsService.java:59)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: org.jfrog.jfconnect.client.exception.RetryFailedException: org.jfrog.common.ExecutionFailed: Failed executing GetEntitlements, last error [Server responded with an invalid status, [localhost:8046]. Status code: [UNIMPLEMENTED]. Description [HTTP status code 404
invalid content-type: text/plain; charset=utf-8
headers: Metadata(:status=404,content-type=text/plain; charset=utf-8,x-content-type-options=nosniff,date=Mon, 24 Jun 2024 07:59:46 GMT,content-length=19)
DATA-----------------------------
404 page not found
]. Err [UNIMPLEMENTED: HTTP status code 404
invalid content-type: text/plain; charset=utf-8
headers: Metadata(:status=404,content-type=text/plain; charset=utf-8,x-content-type-options=nosniff,date=Mon, 24 Jun 2024 07:59:46 GMT,content-length=19)
DATA-----------------------------
404 page not found
]]. Will not retry anymore.
    at org.jfrog.jfconnect.client.grpc.GrpcRetryableCallSupplier.executeWithRetry(GrpcRetryableCallSupplier.java:37)
    at org.jfrog.jfconnect.client.grpc.GrpcClient.executeWithRetryAndConfig(GrpcClient.java:132)
    at org.jfrog.jfconnect.client.grpc.GrpcClient.getEntitlementsUntilSucceed(GrpcClient.java:122)
    at org.jfrog.jfconnect.client.EntitlementsAutoUpdatingCache.updateEntitlements(EntitlementsAutoUpdatingCache.java:120)
    at org.jfrog.jfconnect.client.EntitlementsAutoUpdatingCache.init(EntitlementsAutoUpdatingCache.java:46)
    at org.jfrog.jfconnect.client.EntitlementsClientImpl.init(EntitlementsClientImpl.java:34)
    ... 5 common frames omitted

I've tried Googling this error and I didn't find anything relevant. The weird thing is that earlier on the day, I tried to use Artifactory Pro, and that would start without any problems. Reason I stopped using it was because we didn't have a Pro license to install and we had to swap to the OSS version.


Solution

  • From the log snippet provided, the JFconnect micro-service seems to have failed to start.

    As far as I know, this service should not block Artifactory from loading and starting, but rather just show the expected exception. If Artifactory is failing to start this is a potential bug.

    Regardless, I would recommend you check if disabling this microservice resolves your issue. You can do that by editing the system.yaml configuration file:

    jfconnect:
       enabled: false