Cache refresh: Failed to connect to LDAP server

By: Sravana Lakshmi user 14 May 2020 at 11:50 p.m. CDT

4 Responses
Sravana Lakshmi gravatar
Hi, I have installed gluu on Ubuntu VM and configured cache refresh to connect and sync users from docker base ldap server. I am facing the same issue as https://support.gluu.org/cache-refresh/8220/failed-to-connect-to-ldap-server/ with 4.1 docker base setup. To check the validity of Parameters and network status, I have created separate docker-openldap(refer:https://github.com/osixia/docker-openldap) server and tested Multi master replication where ldap search will be performed between docker containers(Add a new user "billy" on the first ldap server and Search on the second ldap server, and billy should show up!). But the same is not working with cache refresh setup as the test ldap server is always showing **504. That's an error. The server encountered a temporary error and could not complete your request. Please try later again.** Is it a bug or am I missing any thing here? Below is the /opt/gluu/jetty/identity/logs/oxtrust_persistence.log 2020-05-14 18:43:50,243 INFO [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:234) - Attempting to create connection pool: 1 2020-05-14 18:44:36,863 INFO [qtp1818402158-10] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:234) - Attempting to create connection pool: 1 2020-05-14 18:45:35,246 ERROR [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:83) - Failed to create connection pool with properties: {bindDN=cn=admin,dc=example,dc=org, useSSL=false, bindPassword=REDACTED, servers=ldap.example.org:389} com.unboundid.ldap.sdk.LDAPException: An error occurred while attempting to connect to server ldap.example.org:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='Unable to establish a connection to server ldap.example.org/172.17.0.2:389 within the configured timeout of 100000 milliseconds.', ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb)) at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:875) ~[unboundid-ldapsdk-4.0.14.jar:4.0.14]
Ubuntu 18.04
closed

Answers

By Mohit Mali staff 19 May 2020 at 2:49 a.m. CDT

Copy
Mohit Mali gravatar
hi Sravana Lakshmi, Its look to me a connection probelm with LDAP server , please take a look at configuration once again, Cache refresh works well with all version of gluu. Thanks and Regards Mohit Mali

By Sravana Lakshmi user 19 May 2020 at 3:33 a.m. CDT

Copy
Sravana Lakshmi gravatar
The same ip ldap.example.org/172.17.0.2:389 is accessible from other docker ldap server but not from Gluu docker ldap. I have added 172.17.0.2:389 to the /etc/hosts file in oxtrust and ldap containers. Do I need to add the same in other containers? How can I make sure it is connectivity issue as the same connection is working fine with all other ways except with Gluu Docker. Please assist as it is blocking us further. Thanks for your response.

By Mohib Zico staff 29 May 2020 at 7:05 a.m. CDT

Copy
Mohib Zico gravatar
No response from community....

By Sravana Lakshmi user 30 May 2020 at 1:21 p.m. CDT

Copy
Sravana Lakshmi gravatar
Sorry, what does it mean ** "No response from community"? ** I still not found any useful support to resolve this issue. It would be good if you can provide how Cache refresh works on Docker base Gluu containers? And I was wondering why the ticket got closed with out proper support provided?

Post an answer