/var/log/firsrtboot/vmafd-firstboot.py_####_stderr.log
YYYY-MM-DDTHH:MM:SS Initializing Directory server instance ...Vdcprono failed. Error -1: Possible errors:LDAP crror: Can't contact LDAP scrvcrWin Error: Operation failed with error -1 (4294967295)YYYY-MM-DDTHH:MM:SS cis.baseCISException. Base InstallException: YYYY-MM-DDTHH:MM:SS Exception: Traceback (most recent call last): File "/usr/lib/vmuarc-vmafd/firstboot/umafd-firstboot.py", line 184, in main controller.firstboot() File "/usr/lib/unware-vmafd/firstboot/umafd-firstboot.py", line 55, in firstboot self.init() File "/usr/lib/umuarc-vmafd/firstboot/umafd-firstboot.py", linc 61, in init service.init() File "/usr/lib/umuare-vmafd/firstboot/identityinstall/umdir Install.py", line 406, in init self.setup_domain() File "/usr/lib/vmuare-vmafd/firstboot/identityinstall/vmdir Install.py", line 261, in setup_domain problemld = problem)cis.baseCISException. Base InstallException: { "detail": [ "id": "install.vmafd.vmdir_vdcpromo_crror", "translatable": "Failed to run udcprono". "localized": "Failed to run vdcprono" "componentKcy": "umafd", "problemId": "install.umafd.undir_udcprono_error", "resolution": { "id": "install.vmafd.undir_udcpromo_error.resolution", "translatable": "Please scarch of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request." "localized": "Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request."vCenter 7.x
vCenter 8.x
The primary cause for the "Failed to run vdcpromo" error is often a DNS resolution failure that prevents the new vCenter Server from correctly setting up its identity management service. When the vCenter Server is configured with an FQDN (Fully Qualified Domain Name), it must be able to resolve its own FQDN
Follow these steps to ensure network and DNS settings are correctly configured before attempting the installation again:
Verify that the FQDN used for the vCenter Server has a corresponding Forward (A) and Reverse (PTR) DNS record created on the DNS server before beginning the installation.
Make sure port 53 (DNS) is not blocked by any firewalls (physical or software) between the VCSA and the DNS server.
Verify that other necessary ports, such as 389 (LDAP) and 636 (LDAPS), are open if the deployment involves joining an Active Directory domain or using an external identity source.
After addressing the DNS issues, re-attempt the Stage 2 of the vCenter Server installation.