Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

"Leave fed not complete, tries left 0", Convergence of vCenter Server in Enhanced Linked Mode fails due to Replication Partner VMDIR in Standalone Mode (71391)

Last Updated: 4/29/2020Categories: TroubleshootingTotal Views: 24036Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

You are running vCenter Server in Enhanced Linked Mode and Convergence of very first vCenter Server Completed successfully.

Convergence of subsequent vCenter Server in ELM pointing to the first Converged vCenter Server hangs at 8% and eventually fails.

Converge log (/var/log/vmware/converge/converge.log) of failed vCenter Server shows similar to below entries,

2019-07-09T14:14:07.135Z INFO converge Collected replication_flag:True as a part of Telemetry
2019-07-09T14:14:07.146Z INFO converge Leave fed not complete, tries left 29
2019-07-09T14:14:37.177Z INFO converge Collected replication_flag:True as a part of Telemetry
2019-07-09T14:14:37.190Z INFO converge Leave fed not complete, tries left 28
2019-07-09T14:27:38.177Z INFO converge Leave fed not complete, tries left 2
2019-07-09T14:28:08.180Z INFO converge Collected replication_flag:True as a part of Telemetry
2019-07-09T14:28:08.192Z INFO converge Leave fed not complete, tries left 1
2019-07-09T14:28:38.192Z INFO converge Collected replication_flag:True as a part of Telemetry
2019-07-09T14:28:38.204Z INFO converge Leave fed not complete, tries left 0
2019-07-09T14:29:08.235Z INFO converge Leave fed complete status: False
2019-07-09T14:29:08.241Z INFO converge Unsetting the converge running flag

VMware Directory Service Log (/var/log/vmware/vmdird/vmdird-syslog.log) on the Converged vCenter (Replication Partner) shows similar to below entries,

2019-07-09T11:29:01.120342+01:00 info vmdird  t@139733669390080: VmKdcInit: done!
2019-07-09T11:29:01.120517+01:00 info vmdird  t@139733669390080: Lotus Vmkdcd: running...
2019-07-09T11:29:01.120739+01:00 info vmdird  t@139733669390080: VmDir State (8)
2019-07-09T11:29:01.120926+01:00 info vmdird  t@139733669390080: Lotus Vmdird: running... state (8)
2019-07-09T11:29:01.122121+01:00 info vmdird  t@139711444145920: Vmkdc: initializing directory
2019-07-09T11:29:01.122366+01:00 info vmdird  t@139711444145920: Vmkdc: VmKdcdStateSet(1)
2019-07-09T11:29:01.122566+01:00 info vmdird  Starting VMware Directory Servicedone
2019-07-09T11:29:18.712393+01:00 err vmdird  t@139710823380736: _VmDirSearchPreCondition: Server in not in normal mode, not allowing outward replication.
2019-07-09T11:29:18.712755+01:00 err vmdird  t@139710823380736: VmDirSendLdapResult: Request (Search), Error (53), Message (Server in not in normal mode, not allowing outward replication.), (0) socket (<IP Address>)
2019-07-09T11:29:48.776604+01:00 err vmdird  t@139710143899392: _VmDirSearchPreCondition: Server in not in normal mode, not allowing outward replication.
2019-07-09T11:29:48.777148+01:00 err vmdird  t@139710143899392: VmDirSendLdapResult: Request (Search), Error (53), Message (Server in not in normal mode, not allowing outward replication.), (0) socket (<IP Address>)

Cause

During Converge process, VMware Directory Service DB will be set in Standalone mode and exits from Standalone mode at the end of process. However, likewise Service Manager where the Standalone arguments for VMDIRD service are stored is not refreshed post Convergence. Whenever, VMDIRD service is restarted post Convergence it will restart in Standalone Mode and due to that Convergence of second or subsequent vCenter Server will fail as the replication will not happen to the first node which was already converged.

Resolution

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

Workaround

Before Starting the Convergence process of vCenter Server in ELM, verify the VMDIRD Status of the Replication Partner. Status of VMDIRD should be NORMAL. Follow below steps to verify and set the status:

Login to the Replication Partner VC using SSH Client (Embedded vCenter Server).

Change Shell to Bash running the command below,

shell

Verify the current status of VMDIR (it will prompt for SSO Admin Credentials) running the command below,

/usr/lib/vmware-vmafd/bin/dir-cli state get

Example:
/usr/lib/vmware-vmafd/bin/dir-cli state get
Enter password for [email-masked]:
Directory Server State: Standalone (8)

If the State is Standalone, execute below command to Set VMDIR in NORMAL State (If it is already in NORMAL state, skip this step and proceed with the final step to Refresh Likewise Service Manager),

/usr/lib/vmware-vmafd/bin/dir-cli state set --state NORMAL
Enter password for [email-masked]:
Directory Server State set to: NORMAL (3)

Run below command to verify the status to confirm the change,

/usr/lib/vmware-vmafd/bin/dir-cli state get
Enter password for [email-masked]:
Directory Server State: Normal (3)

Refresh Likewise Service Manager by executing below command,

/opt/likewise/bin/lwsm refresh

Proceed with Convergence of vCenter Server.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Windows 自動検出を使用せず職場のアクセス経由で Windows 8.1/10 デバイスを加入する方法 (50122147)

KB
•
Customer Purchasing Program FAQ - オンライン ツールと移行 (71388)

KB
•
vApp テンプレートから vApp をデプロイすると、「ハブの「リソース」が仮想マシンのホスト アフィニティ ルールに違反しています (Hub "Resources" violates VM host affinity rule)」というエラーが表示される (71366)

KB
•
K8S 服务创建停滞，一直处于等待服务 IP 状态，并出现错误“超过负载平衡器服务上的最大池数 (Exceed maximum number of pools on the Load balancer service)” (71372)

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 vSphere ESXi

VMware vCenter Server Appliance

Related Versions:

VMware vSphere ESXi 6.7

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant