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

"install.vmafd.vmdir_vdcpromo_error_21" error during VC convergence, cross domain repoint and fresh deployment (74678)

Last Updated: 4/9/2020Categories: TroubleshootingTotal Views: 41923Language:
Chinese (Simplified)JapaneseEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

You are observing failure while performing one of below the operations on vCenter Server Appliance 6.7 U2c or 6.7 U3 :

Upgrading from either version to vCenter Server 7.0

Converging a vCenter Server (fails at 42%)

Deploying a new vCenter Server by joining to existing vSphere Domain (ELM)

Cross Domain Repoint of vCenter Server to an existing vSphere Domain

In the /var/log/firstboot/vmafd-firstboot.py_<PID>_stderr.log file, you see entries similar to:

2019-09-09T21:10:03.961Z  Initializing Directory server instance ...
Vdcpromo failed. Error[9126]
Could not connect to the local service VMware Directory Service.
Verify VMware Directory Service is running.
2019-09-09T21:10:03.961Z  <class 'cis.baseCISException.BaseInstallException'>
2019-09-09T21:10:03.964Z  Exception: Traceback (most recent call last):
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 177, in main
controller.firstboot()
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 53, in firstboot
self.init()
File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 59, in init
service.init()
File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmdirInstall.py", line 404, in init
self.setup_domain()
File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmdirInstall.py", line 259, in setup_domain
"translatable": "Could not connect to the local service VMware Directory Service. Verify VMware Directory Service is running.",
"id": "install.vmafd.vmdir_vdcpromo_error_21",
"localized": "Could not connect to the local service VMware Directory Service. Verify VMware Directory Service is running."

In the /var/log/firstboot/vmafd-firstboot.py_<PID>_stdout.log file, you see entries similar to:

2019-09-09T21:04:32.587Z  Starting the First boot for VMDIR
2019-09-09T21:04:32.590Z  Setting up as a secondary domain Controller
2019-09-09T21:04:32.591Z  Running command: ['/usr/lib/vmware-vmafd/bin/vdcpromo', '-u', 'Administrator', '-s', '<domain name>', '-h', '<destination vCenter / PSC>', '-H', '<source vCenter / PSC>']
2019-09-09T21:10:03.961Z  VMAFD Boot failed

In the /var/log/vmware/vmdird/vmdird-syslog.log file, you see entries similar to:

2019-09-09T21:04:54.244357+00:00 info vmdird  t@140243357394688: VmDirSrvInitializeHost success: (<Domain Name>)(Administrator)(<domain name>)(ldap://<Replication Partner FQDN>)
2019-09-09T21:04:54.245695+00:00 info vmdird  t@140243617404672: _VmDirGetRemoteDBUsingRPC: Connected to the replication partner (Replication Partner FQDN).
2019-09-09T21:04:54.247188+00:00 info vmdird  t@140243617404672: _VmDirGetRemoteDBUsingRPC: copying remote file /storage/db/vmware-vmdir/data.mdb with data size 128 MB with Map size 20480 MB ...
2019-09-09T21:09:58.472168+00:00 err vmdird  t@140243617404672: VmDirReadDatabaseFile failed. Error[382312502]
2019-09-09T21:09:58.472873+00:00 err vmdird  t@140243617404672: _VmDirGetRemoteDBFileUsingRPC: RpcVmDirReadDatabaseFile() failed on remote file /storage/db/vmware-vmdir/data.mdb with error: 382312502
2019-09-09T21:09:58.638164+00:00 err vmdird  t@140243617404672: VmDirFirstReplicationCycle: _VmDirGetRemoteDBUsingRPC() call failed with error: 1
2019-09-09T21:09:58.638522+00:00 warning vmdird  t@140243617404672: vdirReplicationThrFun: VmDirReplURIToHostname or VmDirFirstReplicationCycle failed, error (-402647496).
2019-09-09T21:09:58.638907+00:00 err vmdird  t@140243617404672: Vmdird force exiting ...
2019-09-09T21:09:58.639466+00:00 info vmdird  t@140243617404672: VmDir State (5)
2019-09-09T21:09:58.639903+00:00 err vmdird  t@140243617404672: vdirReplicationThrFun: Replication has failed with unrecoverable error.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

VMAFD firstboot process copies the VMware Directory Service Database (data.mdb) from the replication partner. The copy operations gets stuck on the source Platform Services Controller or Replication Partner vCenter Appliance while sending the data. This results in VMAFD firstboot failure. The underlying reason for the hang during data transfer is a networking bug in the TCP/IP stack of Linux kernel version used in vCenter Server Appliance 6.7 U2c and 6.7 U3.

Resolution

This issue is resolved in vCenter Server 6.7 U3a, available at VMware Downloads.

During upgrades from vCenter Server 6.7U2c or 6.7U3 to vCenter Server 7.0, the workaround below must be applied first.

Workaround

To work around this issue, disable TSO (TCP Segmentation Offload) and GSO (Generic Segmentation Offload) on the Ethernet Adapter Configuration of the source Platform Services Controller or Replication Partner vCenter Appliance before performing Convergence / Fresh Deployment / Cross Domain Repoint.

To disable TSO and GSO:

Connect to the source PSC or Replication Partner vCenter Appliance using SSH.

Change shell to Bash.
For example:
Command> shell

Execute these commands:
ethtool -K eth0 tso off
ethtool -K eth0 gso off

Note: TSO & GSO will be automatically enabled during appliance reboot.

To enable TSO and GSO after Convergence / Fresh Deployment / Cross Domain Repoint is completed:

Execute these commands:

ethtool -K eth0 tso on
ethtool -K eth0 gso on

To identify on which VCSA to apply the Workaround :

Scenario-1 [Convergence]: - Converging instances of vCenter Server Appliance with an external Platform Services Controller instances into vCenter Server Appliance with an embedded Platform Services Controller

VC1 -> PSC1
Converging VC1 pointing to PSC1 - Apply the workaround on PSC1

Scenario-2[Convergence]: - Converging instances of vCenter Server Appliance with an external Platform Services Controller instances into vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode

PSC1 <-> Embedded VC2
^
|
VC1

Converging VC1 pointing to Embedded VC2 as Replication Partner where VC2 is an already Converged node - Apply the workaround on Embedded VC2

Scenario-3[Fresh Install]: - Adding a new vCenter Server Appliance with an embedded Platform Services Controller connected in Embedded Linked Mode

VC2 Embedded[Installing] <-> VC1 Embedded
VC2 getting installed pointing to Embedded VC1 - Apply the workaround on VC1

Scenario-4[Embedded Domain repoint]: - Repointing a vCenter Server Appliance with an Embedded Platform Services Controller to an existing vsphere domain

Embedded VC1[vsphere.local] <-> Embedded VC2[vmc.local]
VC1 is being repointed to VC2 - Apply the workaround on VC2

Note: You may apply the workaround on all the vCenter Server Appliances which are part of Enhanced Linked Mode if difficulty in finding out on which vCenter Server Appliance the workaround needs to be applied and enable it again when the activity is complete. Please note rebooting vCenter Server Appliance will automatically enable GSO and TSO by default.

Related Information

'install.vmafd.vmdir _vdcpromo_error_ 23' error while deploying, upgrading or installation of vCenter Server vmafd firstboot fails (59538)

VMware vSphere 7.0 Release Notes

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
•
HTML5 ユーザー インターフェイスを使用してメディア ファイルをカタログにアップロードすると、「入力が長すぎます (Input is too long)」というエラーが表示される (78640)

KB
•
在 NSX-T 环境中执行 vMotion 后，虚拟机断开网络连接 (74767)

KB
•
使用单元管理工具停止或静默 vCloud Director 服务后，其他单元上未重新启动已调度的作业 (78620)

Results 1-4 of 4

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