Since no logs are being updated, it is possible that there may be an issue with the logback.xml file. The logback.xml file contains configuration settings that determine how Artifactory logs events and messages during runtime.
To proceed, navigate to the $JFROG_HOME/artifactory/var/etc/artifactory directory and inspect the logback.xml file. Here is an example of the directory listing:
Although Artifactory doesn't remove the contents of the logback.xml file, it's possible that the user deleted the file manually or it was overwritten by an empty file due to running an automation script. To determine how the content was erased, you may need to conduct an internal investigation.
To address this issue, you can try the following solutions:
After replacing the file,
Restart Artifactory and the service is now running as expected.
To proceed, navigate to the $JFROG_HOME/artifactory/var/etc/artifactory directory and inspect the logback.xml file. Here is an example of the directory listing:
drwxr-xr-x. 6 artifactory artifactory 4096 Jan 1 20:08 . drwxr-xr-x. 13 artifactory artifactory 4096 Jan 1 20:09 .. -rw-r-----. 1 artifactory artifactory 3251 Jan 1 00:05 artifactory.config.20230323.000514.yml -rw-r-----. 1 artifactory artifactory 32841 Jan 1 00:03 artifactory.config.latest.1679529832741.xml -rw-r-----. 1 artifactory artifactory 32841 Jan 1 00:03 artifactory.config.latest.xml -rw-r-----. 1 artifactory artifactory 4062 Jan 1 00:05 artifactory.lic -rw-r-----. 1 artifactory artifactory 115 Jan 1 20:07 artifactory.properties -rw-r-----. 1 artifactory artifactory 13452 Jan 1 00:03 artifactory.system.properties -rw-r-----. 1 artifactory artifactory 1145 Jan 1 00:03 binarystore.xml drwxr-x---. 2 artifactory artifactory 6 Jan 1 00:03 keys -rw-r-----. 1 artifactory artifactory 0 Jan 1 20:08 logback.xml -rw-r-----. 1 artifactory artifactory 6242 Jan 1 00:03 mimetypes.xml drwxr-x---. 3 artifactory artifactory 4096 Jan 1 19:58 plugins drwx------. 3 artifactory artifactory 43 Jan 1 00:03 security drwxr-x---. 2 artifactory artifactory 6 Jan 1 00:03 uiFrom the directory listing, it appears that the logback.xml file has a file size of 0 bytes, indicating that it is empty and has no contents. When the logback.xml file is empty or missing, it means that the logging framework has no configuration to work with, and it may not be able to initialize properly.
Although Artifactory doesn't remove the contents of the logback.xml file, it's possible that the user deleted the file manually or it was overwritten by an empty file due to running an automation script. To determine how the content was erased, you may need to conduct an internal investigation.
To address this issue, you can try the following solutions:
- Locate a backup copy of the logback.xml file.
- Copy the logback.xml file from another Artifactory instance that is currently functioning correctly, ensuring that the versions match.
- Download the Artifactory Linux Archive Installer and extract the logback.xml file from under the artifactory-pro-<VERSION>/app/misc/etc/artifactory directory.
After replacing the file,
drwxr-xr-x. 6 artifactory artifactory 4096 Jan 1 20:08 . drwxr-xr-x. 13 artifactory artifactory 4096 Jan 1 20:09 .. -rw-r-----. 1 artifactory artifactory 3251 Jan 1 00:05 artifactory.config.20230323.000514.yml -rw-r-----. 1 artifactory artifactory 32841 Jan 1 00:03 artifactory.config.latest.1679529832741.xml -rw-r-----. 1 artifactory artifactory 32841 Jan 1 00:03 artifactory.config.latest.xml -rw-r-----. 1 artifactory artifactory 4062 Jan 1 00:05 artifactory.lic -rw-r-----. 1 artifactory artifactory 115 Jan 1 20:07 artifactory.properties -rw-r-----. 1 artifactory artifactory 13452 Jan 1 00:03 artifactory.system.properties -rw-r-----. 1 artifactory artifactory 1145 Jan 1 00:03 binarystore.xml drwxr-x---. 2 artifactory artifactory 6 Jan 1 00:03 keys -rw-r-----. 1 artifactory artifactory 22124 Jan 1 20:08 logback.xml -rw-r-----. 1 artifactory artifactory 6242 Jan 1 00:03 mimetypes.xml drwxr-x---. 3 artifactory artifactory 4096 Jan 1 19:58 plugins drwx------. 3 artifactory artifactory 43 Jan 1 00:03 security drwxr-x---. 2 artifactory artifactory 6 Jan 1 00:03 ui
Restart Artifactory and the service is now running as expected.
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": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfcon@1q2wsx3ed4rfv5tg6yh7uj8ik9",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfevt@1q2wsx3ed4rfv5tg6yh7uj8ik9",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jffe@000",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfint@1q2wsx3ed4rfv5tg6yh7uj8ik9",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfmd@8dheu362ys91uq62ts52rw4152",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfob@9duej261gd52tw41tw83kdue62",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
},
{
"service_id": "jfrt@9duej261gd52tw41tw83kdue62",
"node_id": "test-artifactory",
"state": "HEALTHY",
"message": "OK"
}
]
}