Follow these troubleshooting steps to identify the issue and implement a proper resolution.
1. Disk space is full or constrained:
- SSH into the SDDC Manager, log in as the
vcf user, and elevate to root using the following command: su root - Check the disk space by running the following command:
df -h - Check if any of the partitions on the SDDC Manager have over 80% usage.
- Navigate (
cd) into any directories that are full and safely clear out unnecessary files to free up space. - For additional guidance, refer to the KB article: SDDC Manager UI becomes inaccessible due to root (/dev/sda4) partition filling up
2. The SSO password changed/does not match:
3. The vCenter root password does not match due to an out-of-band change:
- Run the following command in SDDC Manager to retrieve the password for the VCENTER resource (this will output the vCenter root password stored in SDDC Manager):
lookup_passwords - Test if the stored password matches the actual password by initiating an SSH session to the vCenter Server directly from the SDDC Manager appliance.
- If the SSH login fails, the root account on the vCenter Server is either locked out, or the password was changed out-of-band and no longer matches.
- To unlock the account and reset the credentials, refer to the KB article: Reset Root Password.
Note: SDDC requires SSH access to vCenter. Ensure that SSH is enabled on the Management vCenter (of the Management Domain).
4. vCenter Server service accounts fail to authenticate or are disconnected:
- Run the VCF Diagnostic Tool for SDDC Manager.
- Inspect the CREDENTIAL CHECKS section of the output for any service account authentication failures.
- If any failures are found, Retrieve the service accounts credentials from SDDC Manager.
- Log in to the vSphere Client and update the passwords for those individual accounts on their respective vCenter Servers to match.
5. The SDDC Manager certificate is expired:
- Run the VCF Diagnostic Tool (VDT) on the SDDC Manager appliance to check the current expiration status of the certificate.
- If the tool indicates that the certificate has expired, refer to the following KB article for instructions on how to replace it: Reset SDDC Manager Certificate.
6. SDDC Manager does not trust the Management vCenter root certificate:
- To verify that the SDDC Manager trusts the Management vCenter root certificate, refer to the following KB article: Import vCenter Root Cert into SDDC Manager Truststore.
- Run the
root synchronization script as outlined in the article.
7. NTP fails to synchronize:
- Network Time Protocol (NTP) synchronization issues can cause severe slowness within the UI or prevent it from loading entirely.
- Run the following commands to check the NTP status and restart the service:
ntpq -psystemctl stop ntpd.servicentpdate ntp_server_ipsystemctl start ntpd.servicesystemctl restart ntpd.servicentpq -p
8. Certificate files or certificate stores are corrupted:
- If the root partition on the SDDC Manager reaches 100% capacity, changes to the
commonsvcs trust store or the cacerts file may fail due to a lack of space, resulting in file corruption. - To verify if the
commonsvcs trust store is corrupted, refer to the following KB article: SDDC manager UI failed load due to empty "trusted_certificates.store". - To verify if the
cacerts file is corrupted, refer to the following KB article: SDDC manager UI failed to load due to corrupted cacerts file.
9. Database errors prevent access:
10. Account permissions are misconfigured:
11. Management vCenter host key validation fails: