Unable to access or start VMware Aria Operations for Logs

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The Cassandra service on the primary node of VMware Aria Operations for Logs crashes. When checking the cluster status via SSH (using root credentials) on any of the worker nodes, the nodetool-no-pass status command shows the primary node in a Down/Normal (DN) state, while the worker nodes remain Up/Normal (UN).
  
  Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address      Load       Tokens  Owns (effective)  Host ID                               Rack
UN  #.#.#.#       # MiB     ###     100.0%            ########-####-####-####-############  rack1
DN  #.#.#.#       ?         256     100.0%            ########-####-####-####-############  rack1
UN  #.#.#.#       # MiB     256     100.0%            ########-####-####-####-############  rack1

 

• Additionally, the /storage/core/loginsight/var/cassandra.log displays the following errors indicating a corrupted hints file:

ERROR [HintsDispatcher:1] 2026-03-12T16:08:00,523 HintsDispatchExecutor.java:260 - Failed to dispatch hints file ########-####-####-####-############.hints: file is corrupted
org.apache.cassandra.io.FSReadError: java.io.IOException: Corrupt hint file found

 

Environment

VMware Aria Operations for Logs 8.18.x

Resolution

• Take an offline snapshot of all VMware Aria Operations for Logs nodes. Ensure the "Snapshot the virtual machine's memory" option is deselected.
  
  
• Follow the troubleshooting steps outlined in the related Knowledge Base article:   Error "Failed to dispatch hints file" "file is corrupted" in cassandra.log