Liagent.ini get changed post configuring Loginsight Agent on NSX nodes through CLI
search cancel

Liagent.ini get changed post configuring Loginsight Agent on NSX nodes through CLI

book

Article ID: 377992

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Trying to configure LogInsight agent on NSX Manager and NSX EDGE nodes through CLI using set logging-server does not work.
  • Following the steps in this document Configure Remote Logging on NSX works for sometime but the configuration on /etc/liagent.ini on the NSX appliance gets reset.
  • We can see the following entries in the liagent logs on the NSX appliance:
    2024-09-16 09:19:46.619637 0x00006a1287fc7700 <debug> CFApiTransport:221 | ControlThreadFunc thread waiting...
    2024-09-16 09:19:46.659900 0x00006a12d1898700 <trace> ConfigMonitor:132  | File change detected for "/var/lib/loginsight-agent/liagent.ini"
    2024-09-16 09:19:46.660217 0x00006a12d1055700 <trace> AgentDaemon:327    | Reading configuration received from server. Hash = ##################################
    2024-09-16 09:19:46.660332 0x00006a12d1055700 <trace> Config:138         | Reading configuration from: /var/lib/loginsight-agent/liagent.ini
    2024-09-16 09:19:46.660413 0x00006a12d1055700 <warng> Config:375         | Cannot find section for [server].central_config in config. Using default: yes
    2024-09-16 09:19:46.660657 0x00006a12d1055700 <trace> Config:109         | The current effective configuration is dumped into file /var/lib/loginsight-agent/liagent-effective.ini
    2024-09-16 09:19:46.660924 0x00006a12d1055700 <trace> AgentDaemon:391    | AgentDaemon Configuring...
    2024-09-16 09:19:46.660964 0x00006a12d1055700 <warng> Config:261         | Cannot find section for [server].ssl_fips_mode in config. Using default: 1
    2024-09-16 09:19:46.660990 0x00006a12d1055700 <trace> AgentDaemon:396    | Enabling FIPS mode...
    2024-09-16 09:19:46.661016 0x00006a12d1055700 <trace> AgentDaemon:706    | OpenSSL FIPS mode is already ON

Environment

Aria Operations for Logs 8.12

Resolution

To workaround this symptoms, we can configure the syslog service from NSX-UI by following the below steps:

  1.  Login to the NSX manager and go to System->Fabric->Profiles->Node Profiles->All NSX Nodes->Under Syslog serves Click Add



  2. You can then fill the information for the Log Insight server with the port number, protocol and log level then click save. Below is a sample screenshot



  3. You should now be able to see logs getting forwarded to the Aria Operations for logs server.
Powered by Wolken Software