The loginsight service fails to start due to loginsight-config-base.xml corruption

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The Aria Operations for Logs UI shows a node disconnected in the Management > Cluster page
• The UI is not available on the affected node - a connection refused error is shown in the browser
• The status of the loginsight service on the node is failed

• # systemctl status loginsight
  
  * loginsight.service - VMware Aria Operations for Logs
     Loaded: loaded (/lib/systemd/system/loginsight.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since date; #min ago
    Process: 1234 ExecStop=/usr/lib/loginsight/application/bin/loginsight stop (code=exited, status=0/SUCCESS)
    Process: 1234 ExecStart=/usr/lib/loginsight/application/bin/loginsight start (code=exited, status=1/FAILURE)
   Main PID: 1234 (code=exited, status=1/FAILURE)

• journal logs indicate a xml parsing error
  

  # journalctl -u loginsight -e
  
  systemd[1]: Started VMware Aria Operations for Logs.
  loginsight[1234]: Traceback (most recent call last):
  ...
  loginsight[1234]:     self.config = StrataConfig(os.path.join(home, "application", "etc", "loginsight-config-base.xml"))
  ...
  loginsight[1234]: xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 19
  systemd[1]: loginsight.service: Main process exited, code=exited, status=1/FAILURE
  systemd[1]: loginsight.service: Failed with result 'exit-code'.

Environment

VMware Aria Operations for Logs 8.x

Cause

The loginsight-config-base.xml file which is required for successful service start is corrupted.

Resolution

1. Log in to the affected node as root via SSH or console
   
   
2. Stop the loginsight service
   
   

   systemctl stop loginsight

   
   
   
3. Copy the loginsight-config-base.xml from one of the other nodes in the cluster
   

   scp root@other-node:/usr/lib/loginsight/application/etc/loginsight-config-base.xml* /usr/lib/loginsight/application/etc/

   Note: Replace other-node with the IP or FQDN of a working node in the cluster
   
   

4. Provide the other-node's root user password
   
   
5. Start the loginsight service
   
   

   systemctl start loginsight