Docker 3.1.5 oxtrust error

By: Lars Van Casteren user 12 Feb 2019 at 3:51 p.m. CST

6 Responses
Lars Van Casteren gravatar
Although it seems 3.1.5 Docker Edition is not yet "officially" released I've gone ahead and installed the 3.1.5 DEV environment mainly because it seems the vault approach seems to be the path forward hence there's no use in building a deploy pipeline for the 3.1.4 DE beta and we're in need of a Windows environment. Gluu 3.1.5 DE is working perfectly, after the docker Gluu install / base-config I use a custom docker image to import additional ldif's for AD/cache-refresh, OpenID clients & custom scripts configuration for a particular environment. There is 1 error in oxtrust.log I cannot seem to figure out what is causing it: ``` org.apache.commons.exec.ExecuteException: Process exited with an error: 12 (Exit value: 12) at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404) at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166) at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:153) at org.xdi.util.process.ProcessHelper.executeProgram(ProcessHelper.java:150) at org.xdi.util.process.ProcessHelper.executeProgram(ProcessHelper.java:65) at org.xdi.util.process.ProcessHelper.executeProgram(ProcessHelper.java:50) at org.gluu.oxtrust.ldap.service.StatusCheckerTimer.setFactorAttributes(StatusCheckerTimer.java:292) at org.gluu.oxtrust.ldap.service.StatusCheckerTimer.processInt(StatusCheckerTimer.java:153) at org.gluu.oxtrust.ldap.service.StatusCheckerTimer.process(StatusCheckerTimer.java:129) at org.gluu.oxtrust.ldap.service.StatusCheckerTimer$Proxy$_$$_WeldSubclass.process$$super(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) at org.xdi.service.cdi.async.AsynchronousInterceptor$1.get(AsynchronousInterceptor.java:36) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.lang.Thread.run(Thread.java:748) ``` Thanks for any insight! L
CentOS 7.6
closed

Answers

By Michael Schwartz Account Admin 12 Feb 2019 at 9:46 p.m. CST

Copy
Michael Schwartz gravatar
I don't think this is a critical issue.

By Lars Van Casteren user 13 Feb 2019 at 2:17 a.m. CST

Copy
Lars Van Casteren gravatar
Hi Michael, Thanks for you reply. I think it has to do with the LDAP cache refresh but I'm not sure. As you say, it doesn't seem to interfere with anything so we'll exclude it from any monitoring. Thanks! L

By Thomas Gasmyr Mougang staff 13 Feb 2019 at 2:37 a.m. CST

Copy
Thomas Gasmyr Mougang gravatar
Hi Casteren, This error is not critical but it affect the system informations display in the home screen: 1- FREE MEMORY 2- HOSTNAME 3- IP ADDRESS 4- UPTIME Login to oxTrust Admin Ui and check if these information are present.

By Lars Van Casteren user 13 Feb 2019 at 4:16 a.m. CST

Copy
Lars Van Casteren gravatar
Hi Thomas, This is what is shown on the home screen: https://monosnap.com/file/cn740RZiOhs8bBDb1ZWnAjL3zn8qta The values seem correct aside from the free disk space. Thanks! L

By Chris Clark user 14 Mar 2019 at 9:20 a.m. CDT

Copy
Chris Clark gravatar
This issue is happening in oxTrust in our 3.1.5 GA Gluu installation, so it needs to be looked at - anyone know the cause of this ? Regards, Chris

By Lars Van Casteren user 14 Mar 2019 at 10:07 a.m. CDT

Copy
Lars Van Casteren gravatar
I thought it was linked with the cache refresh because it set to 1 minute, but when changing cache refresh to 2 minutes interval the error still is thrown every minute.

Post an answer