Symptom:
2024-06-18T04:19:51,379+0000 ERROR [DistTaskSync-########-####-####-####-########ce3c] com.vmware.vcops.auth.server.ldap.Sync.run - Groups sync for ldap: <YourLDAPServer> failed: Unable to fetch users in usergroups. Reason: <YourLDAPServerAddress>:636
com.vmware.vcops.auth.exception.AuthException: Unable to fetch users in usergroups. Reason: <YourLDAPServerAddress>:636
at com.vmware.vcops.auth.server.ldap.LdapQueryHelper.getUsersInGroups(LdapQueryHelper.java:280) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.Sync.fetchLatestGroups(Sync.java:512) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.Sync.doSyncWithRetry(Sync.java:105) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.Sync.run(Sync.java:83) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.platform.distributedtask.DistributedTaskExecutor$TaskProcessorThread.run(DistributedTaskExecutor.java:576) ~[alive_platform.jar:?]
at com.integrien.alive.common.util.BaseThread$BaseThreadRunnable.run(BaseThread.java:177) ~[vrops-adapters-sdk.jar:?]
at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: javax.naming.CommunicationException: <YourLDAPServerAddress>:636
at com.sun.jndi.ldap.Connection.<init>(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapClient.<init>(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapClient.getInstance(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtx.connect(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtx.<init>(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxFromUrl(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(Unknown Source) ~[?:?]
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(Unknown Source) ~[?:?]
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) ~[?:?]
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) ~[?:?]
at javax.naming.InitialContext.init(Unknown Source) ~[?:?]
at javax.naming.ldap.InitialLdapContext.<init>(Unknown Source) ~[?:?]
at com.vmware.vcops.auth.server.ldap.LdapUtil.getLdapContext(LdapUtil.java:349) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.LdapUtil.createContext(LdapUtil.java:258) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.LdapUtil.createContext(LdapUtil.java:201) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
at com.vmware.vcops.auth.server.ldap.LdapQueryHelper.getUsersInGroups(LdapQueryHelper.java:250) ~[vcops-auth-server-1.0-SNAPSHOT.jar:?]
... 6 more
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
Aria Operations 8.10.x and above
One of the AD/LDAP DC controllers cannot be reached from the Aria Operations Analytics nodes. When the LDAP load balance direct to that DC it will produce an error, but when it points to other DCs the sync works properly.
Find Source of time out:
Example: Success
* Trying 192.168.1.2:636...
* Connected to 192.168.1.2 (192.168.1.2) port 636 (#0)
> GET / HTTP/1.1
> Host: 192.168.1.2:636
> User-Agent: curl/8.1.2
> Accept: */*
Press “ctrl +c” to exit the command
If you receive a timeout error, you have found the problematic DC.
Check firewall and networking rules to diagnose the problem further with your networking team.