Changes to liagent.ini are constantly overwritten on Aria Automation and Aria Orchestrator.
search cancel

Changes to liagent.ini are constantly overwritten on Aria Automation and Aria Orchestrator.

book

Article ID: 385957

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

When trying to make manual changes to the Aria Operations for Logs agent configuration file in the below location on vRA and vRO, any changes are almost immediately reverted to previous values :

/var/lib/loginsight-agent/liagent.ini

 

Environment

Aria Operations for Logs 8.x

Aria Automation 8.x

Aria Orchestrator 8.x

Cause

Aria Automation and Aria Orchestrator already has an existing log forwarding configuration set as per the following doc:
 

Resolution

To confirm that the Aria Automation and Aria Orchestrator has been configured to forward logs previously:

  1. SSH to the vRA/vRO appliance.
  2. Run the following command:

    vracli vrli

  3. If the command above returns a response similar to the following:

    {
        "agentId": "0",
        "environment": "prod",
        "host": "hostname.example.com",
        "port": 9543,
        "scheme": "https",
        "sslVerify": false
    }

    Then the integration needs to be reconfigured using the vracli command examples given on this page: How do I configure log forwarding to VMware Aria Operations for Logs in VMware Aria Automation

NOTE: You cannot make changes on vRO and vRA liagent file manually. The only supported way to configure is the agent is through the vracli utility. Alternatively, you could configure a VIP for use with your vRA/vRO endpoints and add tags to all logs that come in to that VIP