Introduction
When working with VMware Cloud Director, you may encounter the message:
CloudCell is not active
This issue typically prevents normal operation of Cloud Director services and can impact tenant access, UI availability, or API functionality. In most cases, the problem is related to stopped services, database connectivity issues, or an unhealthy cell state.
This article explains what the error means and how to safely troubleshoot and resolve it.
Issue
When working with VMware Cloud Director, you may encounter the message:
CloudCell is not active
Understanding the Cause
The issue is usually triggered by one or more of the following:
Cloud Director services are not running
The cell cannot connect to the database
A previous upgrade or reboot did not complete cleanly
Disk space exhaustion (especially under
/opt/vmware/vcloud-director)Certificate or trust issues
Network or load balancer misconfiguration (in multi-cell setups)
Solution
- Log In to the Cloud Director Cell
- Check Cloud Director Service Status
systemctl status vmware-vcd
3. Start or Restart the Services. Wait a few minutes and monitor the startup process.
systemctl start vmware-vcd
systemctl restart vmware-vcd
4. Check Cloud Director Logs
cd /opt/vmware/vcloud-director/logs
tail -f vcloud-container-debug.log
Look for:
Database connection errors
Certificate validation failures
Disk or permission errors
Service dependency failures
These logs usually point directly to the root cause.
