Aria Operations for Logs 8.14 UI is not reachable through all nodes with error "This site can't be reached"

Products

• VMware Aria Suite

Issue/Introduction

1. All nodes are up and running in the vCenter.

2. service loginsight status shows active (running) on all nodes.

3. Accessing UI through all nodes encountering error "This site can't be reached".

4. Running the below command via SSH or console to the primary node, as root, returns 127.0.0.1 as IP address of one of the nodes.

    nodetool-no-pass status

5. Under /storage/core/loginsight/config, the .xml file with the highest number has a node's hostname listed instead of IP address. 

6. IP address 127.0.0.1 is also listed in the following entries in /storage/core/loginsight/cidata/cassandra/config/cassandra.yaml.

    seeds

    listen_address

    braodcast_rpc_address

 

Impact/Risks:

It is advised to take snapshots of all nodes prior to running through this process. Please remember to remove the snapshots promptly after the change is confirmed to be successful.

Environment

Aria Operations for Logs 8.14.x

Cause

This is a known issue affecting VMware Aria Operations for Logs (formerly known as vRealize Log Insight) 8.14, there is no resolution at this time for this version.

It's highly recommended to upgrade to the latest version 8.18, which does not have this issue anymore.

Resolution

Workaround:

1. Perform the same steps in Upgrade to Aria Operations for Logs 8.14 does not proceed after primary node. Or the following option:

2. SSH into all nodes as root. Note: Performing the following steps on all nodes.

3. Run the following command to stop the loginsight service on all nodes.

    service loginsight stop

4. Locate the .xml config file with the highest number by going to the following directory.

   cd /storage/core/loginsight/config

   e.g.:

   

5. Run the following command to make a copy of the .xml#55 in the above example and change the copied .xml file to one number higher.

    cp -p loginsight-config.xml#55 loginsight-config.xml#56

6. Run the following command to enter edit mode for loginsight-config.xml#56.

    vi  loginsight-config.xml#56

7. Locate deamon host entries (should be starting from the 9th line) and find the one that has the node's hostname instead of the IP address.

8. Click i to insert the change. If the hostname is listed, change it to the IP address instead. If the loopback address 127.0.0.1 is listed, change it to the correct IP address.

9. Click "Shift +:", then "wq!" to save the change. 

    e.g. :wq!

10. Once the change is made on all nodes, run the following command to check the Cassandra status again on all nodes. All nodes should show UN (Up Normal). If not, open a new case.

      nodetool-no-pass status

11. Run the following command to start the loginsight service.

      service loginsight start

12. The UI should be accessible again. Note: This might need to wait for a moment due to the change of the config file and the restart of loginsight service.