Aria Operations For Logs UI will not load with error "The element type 'config' must be terminated by the matching end-tag '</config>'"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Cassandra and Loginsight services are running, however Ui will not load

Following error is encountered in the /var/log/vmware/loginsight/ui-runtime.log:

2025-04-24 01:25:55.241+0000] [main/10.xx.xx.xx INFO] [com.vmware.loginsight.web.config.UIConfigPuller] [Going to update UIConfigManager with newer user config #152] 2025-04-24 01:25:55.242+0000] [main/##.##.##.###.ERROR] [com.vmware.loginsight.web.config.UIConfigManager] [Failed to reconfigure with version#152] org.jdom.input.JDOMParseException: Error on line 22: The element type "config" must be terminated by the matching end-tag "</config>"

 

Environment

Aria Operations For Logs 8.18.x

Cause

This issue is caused by an incorrect entry in config.xml file,specifically one that is missing the closing </config> tag. The file in question is identified by its version number, for example, version #152.

Resolution

Note: Valid snapshot of all the nodes is mandatory 

Resolution Steps:

 

• Access the Appliance:

  SSH into the problematic Aria Operations for Logs node.

• Navigate to the Configuration File Directory:

  Go to the following directory:

  /storage/core/loginsight/config/loginsight-config.xml#number

• Identify the Configuration File:

  Look for the configuration file corresponding to the version mentioned in the logs (e.g., config-150.xml).

• Review the File for Syntax Issues:

  Check the file for any syntax issues, especially for an unmatched <config> tag, as indicated by the error message.

• Compare with Working Configuration Files:

  In the same directory, locate other working configuration files that don’t show this error. Compare the problematic file with a working one using the vimdiff command:

  vimdiff <filename1>  <filename2> 

  Use this command to compare the problematic XML file with other configuration files in the same directory.

• Replace the Problematic File:

  After identifying the issue, replace the problematic file with an older, working version.

  Once replaced, copy the file and use WinSCP to push it across all nodes in the cluster.

• Apply the Changes:

  Ensure the corrected configuration file is applied across all nodes in your Aria Operations for Logs setup.

• Restart the Cassandra Service:

  After applying the changes, restart the Cassandra service on all nodes.

• Verify the Fix:

  Check the logs to confirm the error no longer appears, and ensure the Cassandra service is running without any issues.