Error: "502 Bad Gateway" accessing VMware Cloud Director Provider Portal following log collection

Products

• VMware Cloud Director
• VMware Telco Cloud Platform

Issue/Introduction

• Administrators are unable to log into the VMware Cloud Director (VCD) Provider Portal.
• Accessing the VCD Provider Portal returns a 502 Bad Gateway error in the web browser.
• Running service vmware-vcd status on standby VCD cells shows the service in an unexpected active (exited) state:

* vmware-vcd.service - LSB: The VMware vCloud Director service
     Loaded: loaded (/etc/rc.d/init.d/vmware-vcd; generated)
     Drop-In: /etc/systemd/system/vmware-vcd.service.d
              `-10-aftervaos.conf
     Active: active (exited) since ...

• The issue occurs shortly after generating or collecting a VCD support log bundle.

Environment

VMware Cloud Director 10.6.0.1

TCP 5.0

Cause

Generating VCD log bundles can consume significant disk space. If legacy log bundles or large log files are already present on the appliance (e.g., in /opt/vmware/vcloud-director/logs), the additional space required during new log collection can saturate the disk/partition.

When available disk space drops below required thresholds, the vmware-vcd background service fails to maintain normal operational state across standby cells, resulting in a 502 error when attempting to access the portal.

Resolution

1. Identify partitions that are at or near 100% utilization on the root partition
   
   

   df -h

2. Locate and remove legacy or unneeded log bundles (e.g., old .tgz or .zip files)
3. Once adequate disk space is restored on all affected cells, restart the VCD service across the cells:
   
   

   service vmware-vcd restart

4. Confirm the status is now active (running)
   
   

   service vmware-vcd status

5. Verify that access to the VCD Provider Portal URL is restored and login completes successfully without returning a 502 Error.