Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Firstboot fails when upgrading vCenter Server Appliance 6.7 with no DNS records (57126)

Last Updated: 2/4/2021Categories: TroubleshootingTotal Views: 19258Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Firstboot fails during Install/Deployment, Upgrade or Migration of vCenter Server Appliance 6.7 with no DNS records.

In the firstbootStatus.json file, you see following services failed to configure or start during firstboot:

"failedsteps": "vapi_firstboot"

"failedSteps": "vpxd_firstboot"

"failedSteps": "vmafd-firstboot"

"failedSteps": "vmidentity-firstboot"

In the vapi_firstboot.py_####_stderr.log file, you see the error:

"Failed to configure vAPI Endpoint Service at the firstboot time"

In the cloudvm.log file, you see the error:

Stdout: DNS reverse lookup on [IP_Address] has failed.
Unable to obtain hostname from DNS reverse lookup.
Please examine DNS/network configuration.

In the endpoint.log file, you see entries similar to:
Note: vCenter Server Appliance - Each service will have it's own folder in the /var/log/vmware/ directory. The endpoint logs are located in the /var/log/vmware/vapi/endpoint folder.

Native platform error [code: 5][Begin enum on store 'TRUSTED_ROOTS' failed

Cannot initialize STS SSL trust certificate settings

In the vpxd_firstboot.py_####_stderr.log file, you see the entries similar to:

ERROR:root:Security error: (vmodl.fault.SecurityError)

Error: Operation timed out

VirtualCenter firstboot failed

An error occurred while starting service 'vpxd-svcs'

ParseStatusFile: curr error msg: "VMware VirtualCenter failed firstboot."
ParseStatusFile: curr error msg: "An error occurred while starting service 'vpxd'"

In the vpxd-#.log file, you see the error:

Failed to connect to SSO

Note: vCenter Server Appliance - Each service will have it's own folder in the /var/log/vmware/ directory. The vpxd logs are located in the /var/log/vmware/vpxd folder.

In the vmidentity-firstboot.py_####_stdout.log file, you see the error:

The SSL certificate of STS service cannot be verified

In the vmware-sts-idmd.log file, you see the error:

PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed

In the vmafd_firstboot.py_#####_stderr.log file, you see the error:

2018-04-25T14:24:50.397Z Exception: Traceback (most recent call last):
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 189, in main
wait_for_dc_reg_val_update()
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 126, in wait_for_dc_reg_val_update
problemId = "install.vmafd.wait_for_dc_reg_val_update_failed")
cis.baseCISException.BaseInstallException: {
"problemId": "install.vmafd.wait_for_dc_reg_val_update_failed",
"componentKey": "vmafd",
"resolution": {
"translatable": "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.",
"id": "install.vmafd.wait_for_dc_reg_val_update_failed.resolution",
"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."
},
"detail": [
{
"translatable": "ERROR: failed to create initial dc reg value",
"id": "install.vmafd.wait_for_dc_reg_val_update_failed",
"localized": "ERROR: failed to create initial dc reg value"
}
]
}

In the /var/log/vmware/applmgmt/vami.log file, you see the error:

"status": "error",
"warning": [],
"question": null,
"progress_message": {
"id": "install.ciscommon.component.starting",
"args": [
"VMware Authentication Framework"
"translatable": "The installation of vCenter Server failed due to an internal error."
"componentKey": "fb-infra",
"problemId": null,
"resolution": {
"id": "install.default.failure.resolution",
"translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."

For more information on:

Firstboot issues, see: An Error Occurred while Starting Service vpxd-svcs during Firstboot

Cause

This issue occurs when deploying a vCenter Server Appliance 6.7 with an IP address that has no DNS record configured. IP based deployments without DNS are not supported.

Resolution

To resolve this issue, ensure to verify that the IP address has a valid (internal) domain name system (DNS) registration before deploying a vCenter Server Appliance 6.7 with a static IP address.

For more information about DNS requirements, see DNS Requirements for the vCenter Server Appliance and Platform Services Controller Appliance. If this article didn’t solve your issue:

Ask for help here : Click for VMware Communities

Related Information

To avoid DNS issue, ensure that:

vCenter Server Appliance deployments utilizing a static IP address are configured with a valid internal domain name system (DNS) registration.

vCenter Server Appliance deployments utilizing a fully qualified domain name (FQDN) are resolvable by a DNS server.

Ensure that Reverse lookup is implemented using PTR records.

Ensure the network and portgroup the vCenter Server Appliance is deployed to can reach a DNS Server.

To collect a log bundle or review log files:

Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure (2106760)

Triaging a vCenter Server 6.0 installation or upgrade failure (2105258)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VCSA deploy cannot start Stage 2 with "The installer is unable to connect to the vCenter Appliance Management Interface." (87749)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant