By: Graham Private user 11 Jan 2019 at 11:17 a.m. CST

13 Responses
Graham Private gravatar
Was able to install and run a default build on an AWS instance of Ubuntu 16.04 in early Dec (9th, to be precise) however when trying to do exactly the same today/yesterday the service "appears" to install correctly but many things are not right. **Observation** While the ox-ldap.properties file was generated and saved to /install/community-edition-setup/output/ it was not present in /etc/gluu/conf/oxauth-config.json as complained about by the oxauth jetty logs: > 2019-01-11 16:30:42,163 ERROR [main] [org.xdi.oxauth.model.config.ConfigurationFactory] (ConfigurationFactory.java:368) - Failed to find entry: ou=oxauth,ou=configuration,inum=@!93F2.7F2D.2C28.492F!0002!F96F.C4F8,ou=appliances,o=gluu 2019-01-11 16:30:42,163 INFO [main] [org.xdi.oxauth.model.config.ConfigurationFactory] (ConfigurationFactory.java:345) - Unable to find configuration in LDAP, try to load configuration from file system... 2019-01-11 16:30:42,170 WARN [main] [org.xdi.oxauth.model.config.ConfigurationFactory] (ConfigurationFactory.java:500) - /etc/gluu/conf/oxauth-config.json (No such file or directory) java.io.FileNotFoundException: /etc/gluu/conf/oxauth-config.json (No such file or directory) Even if I put that where it belongs (and at this point I assume that something more catastrophic caused the above to occur), I still get nowhere as it doesn't look as though it succeeds connecting to OpenDJ: > 2019-01-11 17:08:17,272 WARN [weld-worker-1] [org.jboss.weld.bootstrap.Validator] (Validator.java:451) - WELD-001440: Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [UnbackedAnnotatedField] @Inject @ApplicationScoped private org.xdi.service.cache.CacheProviderFactory.instance at org.xdi.service.cache.CacheProviderFactory.instance(CacheProviderFactory.java:0) StackTrace 2019-01-11 17:08:17,673 INFO [main] [org.xdi.oxauth.model.util.SecurityProviderUtility] (SecurityProviderUtility.java:23) - Adding Bouncy Castle Provider 2019-01-11 17:08:48.003:WARN:oeja.ServletContainerInitializersStarter:main: org.xdi.exception.ConfigurationException: Failed to create LDAP connection pool! at org.xdi.oxauth.service.AppInitializer.createConnectionProvider(AppInitializer.java:342) at org.xdi.oxauth.service.AppInitializer.applicationInitialized(AppInitializer.java:168) at org.xdi.oxauth.service.AppInitializer$Proxy$_$$_WeldSubclass.applicationInitialized(Unknown Source) oxauth and identity services are up. OpenDJ is running. Front-end experience is I just see the default jetty HTTP ERROR 503. Did the 2019-01-10 19:30 build in https://repo.gluu.org/ubuntu/dists/ break this?

By Chris Blanton staff 11 Jan 2019 at 2:17 p.m. CST

Chris Blanton gravatar
> [org.xdi.oxauth.model.config.ConfigurationFactory] (ConfigurationFactory.java:345) - Unable to find configuration in LDAP, try to load configuration from file system... 2019-01-11 16:30:42,170 WARN [main] [org.xdi.oxauth.model.config.ConfigurationFactory] (ConfigurationFactory.java:500) - /etc/gluu/conf/oxauth-config.json (No such file or directory) java.io.FileNotFoundException: /etc/gluu/conf/oxauth-config.json (No such file or directory) This means that the data isn't available in the LDAP. Either the LDAP is empty or it can't connect to it. > FileNotFoundException: /etc/gluu/conf/oxauth-config.json This is a legacy method for storing configuration and isn't exactly supported any more. There's something wrong with your LDAP connection. That's where most of the services configuration exists. `/etc/gluu/conf/ox-ldap.properties` is what tells the service how to connect and where to look for the configuration.

By Mustafa Baser staff 13 Jan 2019 at 12:26 p.m. CST

Mustafa Baser gravatar
Hi, I never saw `/etc/gluu/conf/oxauth-config.json` file on any of my installations, gluu server always gives that error but works without any issue. Could you provide these files: ``` /install/community-edition-setup/setup.log /install/community-edition-setup/setup_error.log ``` Regards

By Graham Private user 13 Jan 2019 at 12:40 p.m. CST

Graham Private gravatar
Ah, yes. Those files seem useful. Looks like the generated LDAP config is wrong as during install it fails to connect? Or maybe I'm reading it wrong. I can give you the logs you requested as well as the auto-generated config that the (still running) OpenDJ service is using - where would you like them?

By Graham Private user 14 Jan 2019 at 12:51 p.m. CST

Graham Private gravatar
Do you have somewhere I can upload these files?

By Chris Blanton staff 14 Jan 2019 at 1:39 p.m. CST

Chris Blanton gravatar
If you're on your initial installation, I recommend starting from scratch. If it fails again can you provide me the `setup_error.log`?

By Graham Private user 14 Jan 2019 at 1:43 p.m. CST

Graham Private gravatar
Hi Chris, this isn't the first install. First install back in Dec worked fine and I'm still using that. Using this latest build, I've re-run from scratch around 5 or 6 times, each with the same result. The steps for a default install are quite simple, and I followed the exact same steps as per the successful Dec install. Each new attempt with this latest build I created a new Ubuntu instance via AWS to ensure a fresh start. Where do you want me to put the files?

By Chris Blanton staff 14 Jan 2019 at 1:52 p.m. CST

Chris Blanton gravatar
Pastebin will work for me.

By Chris Blanton staff 14 Jan 2019 at 1:52 p.m. CST

Chris Blanton gravatar
Send me the `setup.log` as well as the `setup_error.log`

By Graham Private user 14 Jan 2019 at 1:56 p.m. CST

Graham Private gravatar
setup.log: https://pastebin.com/9kpP0WbL setup_error.log: https://pastebin.com/ev3LRbY9

By Chris Blanton staff 14 Jan 2019 at 2:01 p.m. CST

Chris Blanton gravatar
You're having connectivity/port permission issues. Are you using AWS?

By Graham Private user 14 Jan 2019 at 2:04 p.m. CST

Graham Private gravatar
Yes, it's AWS, however the OpenDJ service is on the same server as the install, and I can see it is running on port 4444: ``` ubuntu@dev-auth:~$ netstat -an |grep 4444 tcp6 0 0 :::4444 :::* LISTEN ``` ``` ubuntu@dev-auth:~$ ps -ef |grep open ubuntu 317 32755 0 20:03 pts/0 00:00:00 grep --color=auto open aws 11427 1 0 Jan11 ? 00:09:09 /opt/jdk1.8.0_181/jre/bin/java -server -Dorg.opends.server.scriptName=start-ds org.opends.server.core.DirectoryServer --configClass org.opends.server.extensions.ConfigFileHandler --configFile /opt/opendj/config/config.ldif --quiet ```

By Chris Blanton staff 14 Jan 2019 at 2:05 p.m. CST

Chris Blanton gravatar
From `setup.log` ``` 16:21:53 01/11/19 Running: /usr/sbin/service opendj start 16:25:18 01/11/19 The timeout of '200' seconds to start the server has been reached. You can use the argument '--timeout' to increase this timeout ``` setup_error.log ``` 16:25:20 01/11/19 Unable to connect to the server at "localhost" on port 4444 16:25:21 01/11/19 Unable to connect to the server at "localhost" on port 4444 ``` My first inclination is inability to access port 4444 because of your security group settings for that instance. I could be wrong though.

By Graham Private user 14 Jan 2019 at 2:48 p.m. CST

Graham Private gravatar
Interestingly, with the working instance, OpenDJ bound to 127.0.0.1:4444 instead of the non-working (recent) binding to :::4444 Did the default OpenDJ host change from 127.0.0.1 to 0.0.0.0 by any chance?