Do you see any interesting logs in `/opt/tomcat/logs` or `/var/log/apache2` (in the container). Also you might try to restart it... exit the container and stop the gluu sever expicitly (always a good idea, i.e. service gluu-serverX.X.X stop).

As sugested stopped and restarted. Still the same error. what is the best OS to install it easily and move forward. we are okay with Ubuntu or Centos or Windows server. there are quite few errors from logs ``` org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authClient' defined in ServletContext resource [/WEB-INF/spring-configuration/applicationContext.xml oxauth.log 2016-05-13 16:00:56,754 INFO [org.jboss.seam.Component] Component: errorResponseFactory, scope: APPLICATION, type: JAVA_BEAN, class: org.xdi.oxauth.model.error.ErrorResponseFactory The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1745) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1703) at com.unboundid.ldap.sdk.LDAPConnectionPool.invokeHealthCheck(LDAPConnectionPool.java:2972) at com.unboundid.ldap.sdk.LDAPConnectionPool.invokeHealthCheck(LDAPConnectionPool.java:2667) at com.unboundid.ldap.sdk.LDAPConnectionPool.doHealthCheck(LDAPConnectionPool.java:2637) at com.unboundid.ldap.sdk.LDAPConnectionPoolHealthCheckThread.run(LDAPConnectionPoolHealthCheckThread.java:94) May 13, 2016 4:02:38 PM org.apache.catalina.loader.WebappClassLoaderBase loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load com.unboundid.ldap.protocol.ProtocolMessages. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1745) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1703) at com.unboundid.ldap.protocol.LDAPMessage.readLDAPResponseFrom(LDAPMessage.java:1160) at com.unboundid.ldap.sdk.LDAPConnectionReader.run(LDAPConnectionReader.java:251) May 13, 2016 4:06:22 PM org.apache.catalina.loader.WebappClassLoaderBase loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.ldaptive.provider.jndi.JndiConnection$JndiSearchIterator. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1745) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1703) at org.ldaptive.provider.jndi.JndiConnection.search(JndiConnection.java:532) at org.ldaptive.SearchOperation.executeSearch(SearchOperation.java:119) at org.ldaptive.SearchOperation.invoke(SearchOperation.java:101) at org.ldaptive.SearchOperation.invoke(SearchOperation.java:28) at org.ldaptive.AbstractOperation.execute(AbstractOperation.java:142) at org.ldaptive.pool.SearchValidator.validate(SearchValidator.java:97) at org.ldaptive.pool.SearchValidator.validate(SearchValidator.java:34) at org.ldaptive.pool.AbstractPool.validate(AbstractPool.java:223) at org.ldaptive.pool.AbstractConnectionPool.validate(AbstractConnectionPool.java:805) at org.ldaptive.pool.AbstractConnectionPool$3.run(AbstractConnectionPool.java:308) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) May 13, 2016 4:06:22 PM org.apache.catalina.loader.WebappClassLoaderBase loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load com.unboundid.ldap.sdk.LDAPConnectionPoolHealthCheckThread. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1745) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1703) at com.unboundid.ldap.sdk.LDAPConnectionPool.close(LDAPConnectionPool.java:740) at com.unboundid.ldap.sdk.LDAPConnectionPool.finalize(LDAPConnectionPool.java:1680) at java.lang.System$2.invokeFinalize(System.java:1213) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:98) at java.lang.ref.Finalizer.access$100(Finalizer.java:34) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:210) May 13, 2016 4:10:54 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["http-bio-127.0.0.1-8443"] May 13, 2016 4:10:54 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["ajp-bio-127.0.0.1-8009"] May 13, 2016 4:10:54 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina May 13, 2016 4:10:54 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [/idp] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. May 13, 2016 4:10:54 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["http-bio-127.0.0.1-8443"] May 13, 2016 4:10:54 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["ajp-bio-127.0.0.1-8009"] May 13, 2016 4:13:13 PM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property. May 13, 2016 4:13:13 PM ```

Looks like LDAP did not start. Can you check the logs from `/opt/opendj/logs` and see if you see any errors? Can you post how you answered the questions in the setup?

LDAP Logs: ``` [13/May/2016:19:43:08 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.135 msg=The Directory Server has started successfully [13/May/2016:19:43:08 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID org.opends.messages.core-135): The Directory Server has started successfully ``` Install: ``` My answers to questions IP Address : 192.168.110.130 hostname : txdalgluu-01.plutosystem.local City southlake State Code : TX Country : US Organization : ttdnow e-mail help@ttdnow.com Max RAM (1536) : Password : ********** Install oxAuth2 : Yes Install oxTrust UI : Yes Install Gluu OpenDJ LDAP : Yes Install Apache HTTPD : Yes Install Shibboleth 2 SAML IDP : Yes Install Asimba SAML Proxy (NO) : Yes Install CAS : Yes Install oxAuth RP : yes Proceed with these values : Y ```

Can you give the exact version of Ubuntu? You used Ubuntu Server and not desktop, right ?

Michael Schwartz thank you for quick response. we have server version of ubuntu. Distribution ID : Ubuntu Description : Ubuntu 14.04.4 LTS Release : 14.04 Codename: trusty Greatly appreciate your help. Reddy E

I think its a memory issue. ``` Max RAM (1536) : ``` You installed a lot of components, I think you need to give the tomcat JVM more memory. I would uninstall the package, re-install and give the server 8GB at least.

Michael, You are great. That was the issue. I changed memory to 10 GB (10240) and now it is working. Hope we can continue to work with configuration. Greatly appreciate your quick response. Reddy

Michael, Thank you for your help. Another quick question 1. Does Gluu Server needs external IP accessible from web or can it be internal to Organization have web site send requests to Gluu Server 2. Whats recommended network zone for Gluu Server (DMZ, Restricted, Private) 3. is it possible to have HIPPA complaint SMS/Text messaging added for 2F authentication Greatly appreciate your help. Reddy

The hostname has to point to a Internet IP, but how you route that is up to you. For example, sometimes the hostname points to the Load Balancer, but the servers have private IP's. Also, keep in mind that in prod, you probably don't want oxTrust to be Internet facing--you may have to adjust the apache config to have oxTrust listen on a different ethernet interface. As far as 2FA options, the Gluu Server has many, and its really easy to add additional methods. We use "custom authenticatoin interception scripts" to do this task. For SMS, we've been working on this one: - [Script](https://github.com/GluuFederation/oxAuth/tree/master/Server/integrations/TwilioSMS) - [Page](https://github.com/GluuFederation/oxAuth/tree/master/Server/src/main/webapp/auth/TwilioSMS) It needs some work... it was never really tested. If you want to setup a meeting to discuss your requirements next week, [http://gluu.org/booking](http://gluu.org/booking)