Description

When starting up Artifactory, whether it's the initial startup or a restart, you may encounter an issue where Artifactory fails to start, and you observe the following error message in the logs:

2023-01-01T00:00:00.000Z [jfrou] [WARN ] [47ee19ae1d4a7055] [local_topology_helper.go:68   ] [main                ] [] - Missing required services: [jfrt]

The term "jfrt" is a shortened form for the Artifactory microservice.

To check the health status of the Artifactory services, you can execute the following command.
curl localhost:8082/router/api/v1/system/health

{
    "router": {
        "node_id": "test-artifactory",
        "state": "HEALTHY",
        "message": "OK",
        "required_service_types": [
            "jfrt",
            "jfac",
            "jfmd",
            "jffe",
            "jfob",
            "jfcon",
            "jfint",
            "jfevt"
        ]
    },
    "services": [
        {
            "service_id": "jfac@1q2wsx3ed4rfv5tg6yh7uj8ik9",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jfcon@1q2wsx3ed4rfv5tg6yh7uj8ik9",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jfevt@1q2wsx3ed4rfv5tg6yh7uj8ik9",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jffe@000",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY",
            "message": "Get \"http://localhost:8070/readiness\": dial tcp 127.0.0.1:8070: connect: connection refused"
        },
        {
            "service_id": "jfint@1q2wsx3ed4rfv5tg6yh7uj8ik9",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jfmd@8dheu362ys91uq62ts52rw4152",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jfob@9duej261gd52tw41tw83kdue62",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY_PEER",
            "message": "Service is healthy; there is at least one unhealthy service"
        },
        {
            "service_id": "jfrt@9duej261gd52tw41tw83kdue62",
            "node_id": "test-artifactory",
            "state": "UNHEALTHY",
            "message": "Unexpected response status code: 500"
        }
    ]
}

It appears that the "jfrt" service is currently in an unhealthy state.

To investigate further, we suggest checking the artifactory-service.log file for additional information. However, if you find that the artifactory-service.log file is not receiving any updates.

…
-rw-r-----. 1 artifactory artifactory   353416 Jan 1 20:07 artifactory-access.log
-rw-r-----. 1 artifactory artifactory        0 Jan 1 20:07 frontend-request.log
-rw-r-----. 1 artifactory artifactory   933606 Jan 1 20:07 artifactory-request.log
-rw-r-----. 1 artifactory artifactory  4169844 Jan 1 20:07 artifactory-service.log
…
-rw-------. 1 artifactory artifactory  1779737 Jan 1 21:51 router-service.log
-rw-r--r--. 1 artifactory artifactory   546120 Jan 1 21:51 observability-request.log
-rw-r-----. 1 artifactory artifactory 11096544 Jan 1 21:51 console.log
-rw-------. 1 artifactory artifactory 17093396 Jan 1 21:51 router-request.log
-rw-r-----. 1 artifactory artifactory  5415161 Jan 1 21:51 access-request.log