Search the VMware Knowledge Base (KB)
View by Article ID

Unable to sync with Identity source after changing DC name in vRA 7.x (2147737)

  • 0 Ratings

Symptoms

  • Unable to add new users to vRealize Automation.
  • vRealize Automation fails to sync with Identity source.
  • You can log in to vRealize Automation portal and perform administrative tasks with existing accounts.
  • In the /storage/log/vmware/horizon/connector.log file, you see entries similar to:

    2016-11-10 11:53:42,720 WARN  (tomcat-http--8) [3001@VSPHERE.LOCAL;vraadmin@VSPHERE.LOCAL;127.0.0.1] com.vmware.horizon.directory.ldap.LdapConnector - Failed to connect to zeus.bctchn.local:null
            javax.naming.CommunicationException: zeus.bctchn.local:389 [Root exception is java.net.ConnectException: Connection timed out]
                    at com.sun.jndi.ldap.Connection.<init>(Connection.java:226)
                    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137)
                    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1614)
                    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2746)
                    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
                    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
                    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
    zeus.bctchn.local is the decommissioned
 
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides steps about how to edit domain_krb.properties file to add correct hostnames.

Cause

This issue occurs if the old DC would still be referenced after adding new hostnames.

Resolution

To resolve the issue:

  1. Take a backup or snapshot of the vRealize Automation appliance.
  2. Log in to vRealize Automation appliance through putty using root credentials.
  3. Change directory to /usr/local/horizon/conf .
  4. Take a back up of the existing domain_krb.properties file by running the command:

    cp domain_krb.properties /tmp

  5. Edit the domain_krb.properties file and add the correct hostnames after removing the incorrect address using appropriate Linux commands.
  6. Restart the horizon service by running the command:

     service horizon-workspace restart

Note: If the environment is distributed, then we must perform the preceding steps on both the appliances.

Additional Information

For more information, refer to Edit the domain_krb.properties file section of  vRealize Automation 7.0 Information.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: