Cannot connect to AD for cache refresh

By: Harrison Dragoo user 19 Jan 2017 at 9:29 a.m. CST

3 Responses
Harrison Dragoo gravatar
we cannot seem to get gluu to connect back to AD for the cache refresh. Based on what I can see the Source Backend LDAP servers are setup correctly. Also I notice a discrepancy in the time. The server time is correct but the time displayed in the application is a different time zone not sure if this is a related issue. the log information is as follows first we were seeing: ``` 2017-01-19 15:06:03,830 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-5) Failed to connect to LDAP server using configuration nsut-ad1 2017-01-19 15:06:03,890 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-5) Skipping cache refresh due to invalid server configuration 2017-01-19 15:08:03,836 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-7) Failed to connect to LDAP server using configuration nsut-ad1 2017-01-19 15:08:03,868 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-7) Skipping cache refresh due to invalid server configuration 2017-01-19 15:10:03,830 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-1) Failed to connect to LDAP server using configuration nsut-ad1 2017-01-19 15:10:03,849 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-1) Skipping cache refresh due to invalid server configuration 2017-01-19 15:12:03,822 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-8) Failed to connect to LDAP server using configuration nsut-ad1 2017-01-19 15:12:03,846 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-1-thread-8) Skipping cache refresh due to invalid server configuration ```
U1404
closed

Answers

By Aliaksandr Samuseu staff 19 Jan 2017 at 9:58 a.m. CST

Copy
Aliaksandr Samuseu gravatar
Hi, Harrison. >we cannot seem to get gluu to connect back to AD for the cache refresh Do you mean it was able to connect before, but now it can't? >Skipping cache refresh due to invalid server configuration Usually this means that provided configuration cannot be used to establish connection *from within the container*. Can you run some search against backend from inside the container using console tools like `ldapsearch` with provided bind DN, password and base DN? May be you specify your backend by DNS name, and it cannot be resolved from inside? Or you set SSL option, but try to connect to SSL-less port of the backend?

By Michael Schwartz Account Admin 19 Jan 2017 at 1:13 p.m. CST

Copy
Michael Schwartz gravatar
Yes, also post screenshots of how you configured the various tabs, and that normally helps us give you some advice.

By Harrison Dragoo user 19 Jan 2017 at 1:19 p.m. CST

Copy
Harrison Dragoo gravatar
looks like we got it fixed. the issue was with the resolve.conf file. We block external DNS requests.

Post an answer