Log Agent Container Fails with Error "keytool error: java.io.FileNotFoundException" in Aria Operations for Logs SaaS
search cancel

Log Agent Container Fails with Error "keytool error: java.io.FileNotFoundException" in Aria Operations for Logs SaaS

book

Article ID: 397468

calendar_today

Updated On: 05-13-2025

Products

VMware Aria Suite

Issue/Introduction

  • The Aria Operations for Logs agent fails to start after successful configuration, resulting in Log Agents container that continuously restarts.

  • The error "keytool error: java.io.FileNotFoundException: /opt/vmware/log-forwarder/security/server.crt (No such file or directory)" is observed in the docker logs (using docker logs log-agent command).

Environment

  • Aria Operations for Logs (SaaS)

Cause

  • The primary cause of this issue is an incorrect configuration of the ENDPOINT_URL in the /etc/log-agent/log-agent.conf file on the VM.

  • Specifically, the https:// prefix is missing from the URL.

  • The docker log shows that the application is trying to access the certificate file, but the application is failing to start because of an incorrect endpoint URL.

Resolution

  • Teardown the existing log agent deployment.

  • Recreate the log agent configuration, ensuring that the ENDPOINT_URL in the user prompt includes the https:// prefix.

  • Deploy the log agent with the corrected configuration.

Additional Information

  • Confirming the presence of the https:// prefix in the configuration within /etc/log-agent/log-agent.conf is crucial for the correct operation of the log agent.