Aria Operations for Logs Virtual Machine is showing corruption. Unable to login to the UI.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

On Aria Operations for Logs, Loginsight service is showing as Active: failed. However, Cassandra is not running. 

You suspect there is a data corruption issue as you are not able to login to the UI with admin credential. 

The following line can be seen on the result from the command:  systemctl status loginsight

Check Previous Start and try to unlock path /storage/core/loginsight/cidata/store/strata_writer.log

 

Environment

Aria Operations for Logs 8.x

Cause

When an Aria Operations for Logs appliance is not properly shutdown, or there has been a power interruption on the VM or the ESXi, loginsight service on the appliance wasn't stopped cleanly. The loginsight lock file did not get removed. The following screenshot shows an example of the service stopped.  However, the strata_writer.lock file still showing in the /storage/core/loginsight/cidata/store folder:

In addition, due the the disruption on the appliance, hint files may get corrupted. The following error can be seen from the /storage/var/loginsight/cassandra.log file:

ERROR [HintsDispatcher:1] ####-##-## 07:00:24,378 HintsDispatchExecutor.java:243 - Failed to dispatch hints file ########-####-####-####-############-#############-#.hints: file is corrupted ({})"

Resolution

SSH into Aria Operations for Logs appliance as root user.

1. Stop loginsight service:
   

   systemctl stop loginsight

2. Go to data store folder:  
   

   cd /storage/core/loginsight/cidata/store

3. Remove the lock file:
   

   rm -f strata_writer.lock

4. Follow KB Error "Failed to dispatch hints file" "file is corrupted" in cassandra.log to cleanup the corrupted hint files.
5. Start up loginsight service:  
   

   systemctl start loginsight

Ensure you can now bring up the Aria Operations UI and able to login with your admin credential.