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

VCHA failover to passive node fails to bring up SSO services due to vmdird LDAP error 49 (76341)

Last Updated: 9/22/2020Categories: TroubleshootingTotal Views: 7886Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You are running a VCHA manual failover to the passive node

The VCHA failover completes successfully however the vCenter Webclient  page shows the error "503 Service Unavailable"

vmware-sts-idmd logs show idmd service not starting

[2019-10-30T22:59:41.691Z ERROR] [IdmServer] IDM Server has failed to start
com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials

vmdird logs show password errors for the vCenter machine account

19-10-30T22:57:51.581345+00:00 err vmdird t@140674263410432: VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL step failed.)), (0) socket (127.0.0.1)
19-10-30T22:57:51.602017+00:00 err vmdird t@140674263410432: Bind Request Failed (127.0.0.1) error 49: Protocol version: 3, Bind DN: "cn=vc01.test.local,ou=Domain Controllers,dc=vsphere,dc=local", Method: SASL
19-10-30T22:58:01.591518+00:00 err vmdird t@140674263410432: SASLSessionStep: sasl error (-13)(SASL(-13): authentication failure: client evidence does not match what we calculated. Probably a password error)

Resetting the machine account password for vCenter user using KB https://kb.vmware.com/s/article/2147280 fixes the issue temporarily, however issue recurs post failover to the passive node

Cause

vmdird logs showed that the copy interval for data.mdb file is 0

19-02-01T02:29:15.527397+00:00 info vmdird t@140331222071040: VmDirInitDbCopyThread: database snapshot reg keys: CopyDbWritesMin 1 CopyDbIntervalInSec 0 CopyDbBlockWriteInSec 30

vmdir maintains copy of machine account passwords in registry and mdb file . mdb file is always updated with any changes happening (like password changes) at an interval specified by CopyDbIntervalInSec. Since it is currently set to 0, no mdb file will be created and a password mismatch ( between mdb & registry) happens. The current sync interval for the machine account password is 45 days and if a vcha failover is triggered within 45 days then this issue will be triggered.

Resolution

VMware Engineering is aware of this issue and is working on a permanent fix in a future release.
Currently there is no permanent solution, however a workaround is available.

Workaround

To work-around the issue, follow the below steps in order:

Login to Active vCenter and perform the below steps

1. Set the CopyDbIntervalInSec registry value using this command
/opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\vmdir\Parameters]' "CopyDbIntervalInSec" "60"
2. Reset password using methods described in KB https://kb.vmware.com/s/article/2147280
3. Restart the vmdird service using KB https://kb.vmware.com/s/article/2109887
4. Wait for few minutes for replication of snapshot and registry values to complete - ~5 mins
5. Trigger a VCHA manual Failover
6. Once the Passive node becomes Active set the CopyDbIntervalInSec Registry in the Passive Node(Now Active)
/opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\vmdir\Parameters]' "CopyDbIntervalInSec" "60"
8. Restart the vmdird service using KB https://kb.vmware.com/s/article/2109887
9. Trigger a VCHA manual failover and confirm the services are accessible

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Automation 7.x での Internet Information Services (IIS) アプリケーション プールのリサイクルの無効化 (76333)

KB
•
VUM 扫描失败：VMware vSphere Update Manager 存在未知错误。请查看事件和日志文件 (76357)

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

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

VMware Update Manager

Related Versions:

VMware vCenter Server Appliance 6.5.x

VMware Update Manager 6.5

Take Our Survey

Support Assistant