By: Freddie Johnson Jr user 07 Feb 2019 at 5:24 p.m. CST

2 Responses
Freddie Johnson Jr gravatar
Team - I upgraded from 3.1.4 to 3.1.5 following your online documentation. Once finish, I received a 503 server unavailable error. In order to get pass that error, I followed the directions on ticket 6457 which required me to add the startup order within init.d. Then, I could finally get the server to respond with a webpage at /identity but it eventually errors and says login.errorSessionInvalidMessage. I tried clearing my cookies, another browser, and rebooting -- neither worked. Here are the logs I could find of interest within oxtrust_persistence: ``` 2019-02-07 20:27:30,899 INFO [main] [] ( - Attempting to create connection pool: 1 2019-02-07 20:27:35,730 INFO [main] [] ( - Attempting to create connection pool: 1 2019-02-07 20:35:13,156 INFO [main] [] ( - Attempting to create connection pool: 1 2019-02-07 20:35:18,205 INFO [main] [] ( - Attempting to create connection pool: 2 2019-02-07 20:35:23,207 INFO [main] [] ( - Attempting to create connection pool: 3 2019-02-07 20:35:28,209 INFO [main] [] ( - Attempting to create connection pool: 4 2019-02-07 20:35:33,211 INFO [main] [] ( - Attempting to create connection pool: 5 2019-02-07 20:35:38,213 INFO [main] [] ( - Attempting to create connection pool: 6 2019-02-07 20:35:43,216 ERROR [main] [] ( - Failed to create connection pool with properties: {certsDir=/etc/certs, pythonModulesDir=/opt/gluu/python/libs,, ssl.trustStoreFile=/etc/certs/opendj.pkcs12, bindPassword=REDACTED, oxpassport_ConfigurationEntryDN=ou=oxpassport,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu,, oxasimba_ConfigurationEntryDN=ou=oxasimba,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu, oxtrust_ConfigurationEntryDN=ou=oxtrust,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu, connection.max-age-time-millis=1800000, oxidp_ConfigurationEntryDN=ou=oxidp,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu, oxauth_ConfigurationEntryDN=ou=oxauth,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu, servers=localhost:1636, ssl.trustStorePin=t6p6MN7jQfco, confDir=,, certificateAttributes=userCertificate, ssl.trustStoreFormat=pkcs12, connection.max-wait-time-millis=20000, bindDN=cn=directory manager, useSSL=true, binaryAttributes=objectGUID, maxconnections=10, oxcas_ConfigurationEntryDN=ou=oxcas,ou=configuration,inum=@!0333.D1F7.8BE2.9474!0002!9178.AFE4,ou=appliances,o=gluu} com.unboundid.ldap.sdk.LDAPException: An error occurred while attempting to connect to server localhost:1636: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server localhost/ ConnectException(message='Connection refused (Connection refused)', trace='socketConnect( / doConnect( / connectToAddress( / connect( / connect( / connect( / connect( / connect( / run(', revision=24201)') at com.unboundid.ldap.sdk.LDAPConnection.connect( ~[unboundid-ldapsdk-3.2.0.jar:3.2.0] at com.unboundid.ldap.sdk.LDAPConnection.connect( ~[unboundid-ldapsdk-3.2.0.jar:3.2.0] at com.unboundid.ldap.sdk.LDAPConnection.connect( ~[unboundid-ldapsdk-3.2.0.jar:3.2.0] at com.unboundid.ldap.sdk.LDAPConnection.<init>( ~[unboundid-ldapsdk-3.2.0.jar:3.2.0] at com.unboundid.ldap.sdk.SingleServerSet.getConnection(SingleServerSet. ``` Before the upgrade, I was using OpenDJ as the standard LDAP store and authenticated to the UI using Active Directory (auth_ldap_server) -- everything worked fine including syncing with AD into local OpenDJ database. Also running with 8GB of ram as well. Looking forward to your feedback. Freddie

By Mohib Zico staff 17 Feb 2019 at 12:06 a.m. CST

Mohib Zico gravatar
Hi Freddie, Seems like some issues with 'localhost:1636' connection. Can you please check what's happening in OpenDJ logs?

By Freddie Johnson Jr user 17 Feb 2019 at 10:23 p.m. CST

Freddie Johnson Jr gravatar
Unfortunately, I wiped the the installation and went with another solution to meet our testing deadline but here's the last image I took before wiping trying to access the local OpenDJ instance: I tried following the instructions to change the authentication mode back to the default but I ran into a few issues until eventually wiping. First, I needed to pass the useSSL flag and change the port number to the 1636 which was different in the FAQ documentation. I couldn't get pass the invalid credentials prompt even though it was a direct copy and paste of the initial password I used during setup and testing. Either way, looking forward to your feedback. We may consider GLUU in the future if the other solution doesn't pan out and we can get pass those hurdles. Thanks for the support! Freddie