Cassandra Service Fails to Start with "Cassandra is not running" - Aria Operations for Logs

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Aria Operations for Logs UI is inaccessible.

Environment

Aria Operations for Logs 8.x

Cause

The issue is caused by a corrupted internal Java Truststore file on the secondary nodes, which completely breaks the secure SSL/TLS handshakes required for intra-cluster communication and web UI initialization.

Resolution

To remediate the cluster state and restore UI accessibility, execute the following procedures sequentially:

1. Replace the Corrupted Truststore: Extract and copy a known-functional truststore file from the operational primary node to the corrupted secondary nodes. Follow the precise step-by-step restoration workflow outlined in Replace a corrupted truststore in VCF/Aria Operations for Logs.
   
   
2. Reset the Internal Application Certificates: Clear the failed or invalid certificate states within the Aria Operations for Logs configuration database. Follow the procedure documented in VMware Aria Operations for Logs GUI Inaccessible - Received fatal alert: certificate_expired
   
   
3. Regenerate Cluster SSL Certificates: Generate new internal SSL certificates to re-establish secure handshakes across all nodes within the deployment. Execute the regeneration commands as specified in Install a self-signed certificate in VMware Aria Operations for Logs 8.12 and Later.
   
   
4. Verify that all cluster nodes return to a connected state using the command below and confirm that the web user interface initializes successfully.
   nodetool-no-pass status