By: Xuejiao Zhang user 25 Aug 2019 at 6:18 a.m. CDT

7 Responses
Xuejiao Zhang gravatar
# What happened I was trying to install Gluu-3.16 on AWS, following the instruction of the official docs. Everything went well, I got the message " Gluu Server installation successful! Point your browser to https://test.gluu.com" And when I tried to access it, I got the complaint" ``` HTTP ERROR 503 Problem accessing /identity/. Reason: Service Unavailable Powered by Jetty:// 9.4.12.v20180830 ``` ## Logs [root@test ~]# cat /opt/gluu/jetty/identity/logs/oxtrust.log ``` 2019-08-25 10:38:06,685 INFO [main] [org.gluu.oxtrust.util.BuildVersion] (BuildVersion.java:82) - Root element :beans 2019-08-25 10:38:06,717 INFO [main] [org.xdi.oxauth.model.util.SecurityProviderUtility] (SecurityProviderUtility.java:24) - Adding Bouncy Castle Provider 2019-08-25 10:38:06,786 INFO [main] [org.gluu.oxtrust.ldap.service.AppInitializer] (AppInitializer.java:301) - Build date 2019-05-09 20:04. Code revision 25374f6ff051a2c82fe6157702ac7e9452329074 on ${git.commit.time}. Build 532 2019-08-25 10:38:06,801 INFO [main] [org.gluu.oxtrust.config.ConfigurationFactory] (ConfigurationFactory.java:134) - Creating oxTrustConfiguration 2019-08-25 10:38:06,801 INFO [main] [org.gluu.oxtrust.config.ConfigurationFactory] (ConfigurationFactory.java:420) - ########## ldapFileName = /etc/gluu/conf/ox-ldap.properties 2019-08-25 10:38:06,845 ERROR [main] [org.xdi.util.properties.FileConfiguration] (FileConfiguration.java:59) - Failed to load '/etc/gluu/conf/oxtrust-central-ldap.properties' configuration file from config folder 2019-08-25 11:03:07,458 INFO [Scanner-0] [org.richfaces.log.JavaLogger] (JavaLogger.java:213) - Auto-registered servlet ResourceServlet with mapping '/org.richfaces.resources/*' 2019-08-25 11:03:18,626 INFO [Scanner-0] [org.gluu.oxtrust.util.BuildVersion] (BuildVersion.java:82) - Root element :beans ```

By William Lowe staff 25 Aug 2019 at 10:24 a.m. CDT

William Lowe gravatar
did you adjust your system host file to include `test.gluu.com` ?

By Michael Schwartz staff 25 Aug 2019 at 9:48 p.m. CDT

Michael Schwartz gravatar
``` 2019-08-25 10:38:06,845 ERROR [main] [org.xdi.util.properties.FileConfiguration] (FileConfiguration.java:59) - Failed to load '/etc/gluu/conf/oxtrust-central-ldap.properties' configuration file from config folder ``` That's very strange. Why can't it load the properties file?

By Xuejiao Zhang user 25 Aug 2019 at 11:32 p.m. CDT

Xuejiao Zhang gravatar
@William.Lowe @Michael.Schwartz Thanks a lot for your prompt reply. The problem is solved after I increaed the disk space , probably it was caused by "not enough disk space". However, I met another issue. I am plannging to use AWS Cognito identity pool, Gluu server as Authentication provider (SAML). Following the instructions here: https://gluu.org/docs/ce/integration/saas/aws/, After creating AWS Custom Attributes in LDAP and restarted opendj service. when I tried to create attributes in the Gluu web UI, it complainted ``` The Attribute type ‘RoleEntitlement’ not defined in LDAP schema Failed to update aAttribute ‘RoleEntitlement’ ``` Do you have any clue about this? Thanks in advance. ### /opt/gluu/jetty/oxauth/logs/oxauth.log ``` 2019-08-26 02:45:49,938 INFO [qtp804611486-11] [org.xdi.oxauth.auth.Authenticator] (Authenticator.java:262) - Authentication s uccess for Client: '@!896F.9543.A0D3.2B07!0001!014A.8063!0008!1304.D2FF' 2019-08-26 04:12:09,834 ERROR [ForkJoinPool.commonPool-worker-0] [org.xdi.oxauth.model.config.ConfigurationFactory] (Configurat ionFactory.java:384) - Failed to find entry: ou=oxauth,ou=configuration,inum=@!896F.9543.A0D3.2B07!0002!43A3.76E2,ou=appliances ,o=gluu 2019-08-26 04:12:09,935 ERROR [ForkJoinPool.commonPool-worker-0] [org.xdi.oxauth.service.AppInitializer] (AppInitializer.java:6 28) - Failed to load appliance entry from Ldap org.gluu.site.ldap.persistence.exception.EntryPersistenceException: Failed to find entry: inum=@!896F.9543.A0D3.2B07!0002!43A3. 76E2,ou=appliances,o=gluu at org.gluu.site.ldap.persistence.LdapEntryManager.find(LdapEntryManager.java:303) ~[oxcore-ldap-3.1.6.sp1.jar:?] at org.gluu.site.ldap.persistence.AbstractEntryManager.find(AbstractEntryManager.java:444) ~[oxcore-ldap-3.1.6.sp1.jar: ?] ... ``` ### /opt/gluu/jetty/identity/logs/oxtrust.log ``` [26/Aug/2019:04:11:53 +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.DirectoryServerShutdown, alert ID org.opends.messages.core-141): The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServerShutdownHook and the reason provided for the shutdown was The Directory Server shutdown hook detected that the JVM is shutting down. This generally indicates that JVM received an external request to stop (e.g., through a kill signal) [26/Aug/2019:04:11:55 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.370 msg=The backend metric is now taken offline [26/Aug/2019:04:11:55 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.370 msg=The backend site is now taken offline [26/Aug/2019:04:11:55 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.370 msg=The backend userRoot is now taken offline [26/Aug/2019:04:11:55 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.203 msg=The Directory Server is now stopped [26/八月/2019:04:12:09 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.21 msg=Installation Directory: /opt/opendj [26/八月/2019:04:12:09 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.23 msg=Instance Directory: /opt/opendj [26/八月/2019:04:12:09 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.17 msg=JVM Information: 1.8.0_181-b13 by Oracle Corporation, 64-bit architecture, 122159104 bytes heap size [26/八月/2019:04:12:09 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.18 msg=JVM Host: localhost, running Linux 4.14.123-111.109.amzn2.x86_64 amd64, 16818462720 bytes physical memory size, number of processors available 4 [26/八月/2019:04:12:09 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.19 msg=JVM Arguments: "-Xms128m",: "-Xmx128m", "-Dorg.opends.server.scriptName=start-ds" [26/八月/2019:04:12:10 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.513 msg=The database backend site containing 2 entries has started [26/八月/2019:04:12:10 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.513 msg=The database backend metric containing 335 entries has started [26/八月/2019:04:12:10 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.513 msg=The database backend userRoot containing 173 entries has started [26/八月/2019:04:12:10 +0000] category=EXTENSIONS severity=NOTICE msgID=org.opends.messages.extension.221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: localhost [26/八月/2019:04:12:10 +0000] category=PROTOCOL severity=NOTICE msgID=org.opends.messages.protocol.276 msg=Started listening for new connections on Administration Connector 127.0.0.1 port 4444 [26/八月/2019:04:12:10 +0000] category=PROTOCOL severity=NOTICE msgID=org.opends.messages.protocol.276 msg=Started listening for new connections on LDAPS Connection Handler 127.0.0.1 port 1636 [26/八月/2019:04:12:10 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.135 msg=The Directory Server has started successfully [26/八月/2019:04:12:10 +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 ```

By Michael Schwartz staff 25 Aug 2019 at 11:40 p.m. CDT

Michael Schwartz gravatar
You probably need to add the attribute to OpenDJ. see the Gluu docs about adding custom schema

By Xuejiao Zhang user 26 Aug 2019 at 1:33 a.m. CDT

Xuejiao Zhang gravatar
@Michael.Schwartz I have added the attributes exactly following the Gluu Doc. That's why I fetl strange. ``` [root@localhost ~]# cat /opt/opendj/config/schema/77-customAttributes.ldif dn: cn=schema objectClass: top objectClass: ldapSubentry objectClass: subschema cn: schema attributeTypes ( 1.3.6.1.4.1.48710.1.3.1003 NAME 'RoleEntitlement' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Gluu - AWS Assume Role' ) attributeTypes ( 1.3.6.1.4.1.48710.1.3.1004 NAME 'RoleSessionName' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Gluu - AWS Assume Role Session Name' ) objectclass ( 1.3.6.1.4.1.48710.1.4.101 NAME 'gluuCustomPerson' SUP ( top ) AUXILIARY MAY ( telephoneNumber $ mobile $ RoleEntitlement $ RoleSessionName ) X-ORIGIN 'Gluu - Custom persom objectclass' ) [root@localhost ~]# ```

By William Lowe staff 26 Aug 2019 at 1:38 a.m. CDT

William Lowe gravatar
OK, please open a new ticket with steps to reproduce, and the steps you've taken to troubleshoot. We will take a look.

By Xuejiao Zhang user 26 Aug 2019 at 2:52 a.m. CDT

Xuejiao Zhang gravatar
@William.Lowe Sure, thanks. Here is the new ticket. https://support.gluu.org/single-sign-on/7410/failed-to-create-attributes-in-the-gluu-web-u/ By the way, I think we can close the ticket but I don't know how.