By: Carl Brenton user 03 Jan 2019 at 11:06 a.m. CST

2 Responses
Carl Brenton gravatar
I have observed the inability to login occasionally. The log message shows several entries of the following : ``` 2018-12-12 16:27:02,125 ERROR [Thread-169586] [org.xdi.oxauth.service.AppInitializer] (AppInitializer.java:554) - Failed to load appliance entry from Ldap\ org.gluu.site.ldap.persistence.exception.EntryPersistenceException: Failed to find entry: inum=@!D321.61D6.A072.7E00!0002!1645.6F69,ou=appliances,o=gluu\ at org.gluu.site.ldap.persistence.LdapEntryManager.find(LdapEntryManager.java:303) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.gluu.site.ldap.persistence.AbstractEntryManager.find(AbstractEntryManager.java:444) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.gluu.site.ldap.persistence.AbstractEntryManager.find(AbstractEntryManager.java:381) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.gluu.site.ldap.persistence.LdapEntryManager$Proxy$_$$_WeldClientProxy.find(Unknown Source) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.xdi.oxauth.service.AppInitializer.loadAppliance(AppInitializer.java:552) [classes/:?]\ at org.xdi.oxauth.service.AppInitializer.loadLdapIdpAuthConfigs(AppInitializer.java:486) [classes/:?]\ at org.xdi.oxauth.service.AppInitializer.loadLdapAuthConfigs(AppInitializer.java:580) [classes/:?]\ at org.xdi.oxauth.service.AppInitializer.reloadConfiguration(AppInitializer.java:257) [classes/:?]\ at org.xdi.oxauth.service.AppInitializer.reloadConfigurationTimerEvent(AppInitializer.java:244) [classes/:?]\ at org.xdi.oxauth.service.AppInitializer$Proxy$_$$_WeldSubclass.reloadConfigurationTimerEvent$$super(Unknown Source) [classes/:?]\ at sun.reflect.GeneratedMethodAccessor302.invoke(Unknown Source) ~[?:?]\ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_112]\ at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_112]\ at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.0.Final.jar:3.0.0.Final]\ at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.0.Final.jar:3.0.0.Final]\ at org.xdi.service.cdi.async.AsynchronousInterceptor$1.get(AsynchronousInterceptor.java:36) [oxcore-service-3.1.2.Final.jar:?]\ at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) [?:1.8.0_112]\ at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]\ Caused by: org.gluu.site.ldap.exception.ConnectionException: Failed to lookup entry --> A client-side timeout was encountered while waiting 300000ms for a response to search request with message ID 25, base DN 'inum=@!D321.61D6.A072.7E00!0002!1645.6F69,ou=appliances,o=gluu', scope BASE, and filter '(objectClass=*)' from server localhost:1636.\ at org.gluu.site.ldap.OperationsFacade.lookup(OperationsFacade.java:513) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.gluu.site.ldap.persistence.LdapEntryManager.find(LdapEntryManager.java:297) ~[oxcore-ldap-3.1.2.Final.jar:?]\ ... 17 more\ Caused by: com.unboundid.ldap.sdk.LDAPSearchException: A client-side timeout was encountered while waiting 300000ms for a response to search request with message ID 25, base DN 'inum=@!D321.61D6.A072.7E00!0002!1645.6F69,ou=appliances,o=gluu', scope BASE, and filter '(objectClass=*)' from server localhost:1636.\ at com.unboundid.ldap.sdk.SearchRequest.process(SearchRequest.java:1193) ~[unboundid-ldapsdk-3.2.0.jar:3.2.0]\ at com.unboundid.ldap.sdk.LDAPConnection.search(LDAPConnection.java:3635) ~[unboundid-ldapsdk-3.2.0.jar:3.2.0]\ at com.unboundid.ldap.sdk.LDAPConnection.getEntry(LDAPConnection.java:1712) ~[unboundid-ldapsdk-3.2.0.jar:3.2.0]\ at com.unboundid.ldap.sdk.AbstractConnectionPool.getEntry(AbstractConnectionPool.java:611) ~[unboundid-ldapsdk-3.2.0.jar:3.2.0]\ at org.gluu.site.ldap.OperationsFacade.lookup(OperationsFacade.java:510) ~[oxcore-ldap-3.1.2.Final.jar:?]\ at org.gluu.site.ldap.persistence.LdapEntryManager.find(LdapEntryManager.java:297) ~[oxcore-ldap-3.1.2.Final.jar:?]\ ... 17 more\ ``` These occur several times a day. Does anyone know if they relate problems authenticating ?

By Michael Schwartz staff 03 Jan 2019 at 1:31 p.m. CST

Michael Schwartz gravatar
``` . . . A client-side timeout was encountered . . . ``` A timeout on a search with `scope BASE` normally indicates a memory problem. Are you sure the server and LDAP process have enough memory? You may also want to adjust the LDAP process memory settings and run the `dsjavaproperties` command in `/opt/opendj`

By Carl Brenton user 04 Jan 2019 at 4:31 a.m. CST

Carl Brenton gravatar
Many thanks Michael for that speedy response. I shall check the memory allocation and see if any change has an effect.