/opt/vmware/vcloud-director/logs/cell.log
file/opt/vmware/vcloud-director/logs/cell.log
repeats after "Application Initialization: 'Legacy Cell Application' 77% complete. Subsystem 'com.vmware.vcloud.presentation-api-impl' started"
/opt/vmware/vcloud-director/logs/cell-runtime.log
contains FATAL errors similar to the following:2025-04-04 15:09:47,716 | FATAL | Module: com.vmware.vcloud.statsfeeder-application | ModuleRegistry | Error in module: "com.vmware.vcloud.statsfeeder-application"; Bean: cassandraClient, Message: Error creating bean with name 'cassandraClient': Invocation of init method failed; nested exception is com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed ...
/opt/vmware/vcloud-director/logs/vcloud-container-debug.log
the following error is observed: "Failure connecting to Cassandra cluster nodes"
VMware Cloud Director 10.5.1.1
Cloud Director service is unable to start because it is configured to connect to a Cassandra server that is not available.
To resolve this error, make sure that the Cassandra server(s) are running and reachable from the Cloud Director cells.
Workaround:
If we have removed the Cassandra servers and aren't able to restore that connectivity to Cloud Director we can remove the Cassandra server configuration so that Cloud Director does not look for them during the service start up process.
To remove Cassandra configuration from Cloud Director:
/opt/vmware/vcloud-director/bin/cell-management-tool cassandra --clean
Impact/Risks:
Will need to remove Cassandra configuration from Cloud Director.