Oxauth UI 503 Error - Opendj won't start

By: Danielle Keeling user 14 Oct 2022 at 1:46 p.m. CDT

2 Responses
Danielle Keeling gravatar
##Expected behavior Ability to log into Oxauth UI ##Actual behavior 503. That's an error. The service you requested is not available at this time. Please try later again. ##Minimized example I'm not quite sure what I'm supposed to add here but I reviewed and performed the steps in the following tickets: https://support.gluu.org/outages/9042/503-error/ https://support.gluu.org/installation/5864/ldap-password/ https://support.gluu.org/identity-management/10615/oops-something-wrong-happened/ I've narrrowed down the issue to this message in the logs during startup: Oct 14 18:06:28 gts0001 start-ds[613]: [14/Oct/2022:18:06:28 +0000] category=EXTENSIONS severity=NOTICE msgID=221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: localhost Everytime I run start-ds it hangs and then times out. root@gts0001:~# service opendj status ● opendj.service - OpenDJ Directory Service Loaded: loaded (/etc/systemd/system/opendj.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-10-14 18:11:15 UTC; 5min ago Process: 564 ExecStart=/opt/opendj/bin/start-ds (code=exited, status=2) Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 677 (Cleaner-7) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 678 (Cleaner-8) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 679 (Checkpointer) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 680 (StatCapture) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 906 (LDAP Connection) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 918 (SIGTERM handler) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 919 (Directory Serve) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Killing process 921 (LDAP Connection) with signal SIGKILL. Oct 14 18:11:15 gts0001 systemd[1]: opendj.service: Failed with result 'exit-code'. Oct 14 18:11:15 gts0001 systemd[1]: Failed to start OpenDJ Directory Service. I updated my /etc/hosts file to include my static ip address and my FQDN. What am I missing? All of the other services start successfully: ldap@gts0001:/opt/opendj/bin$ service apache2 status && service oxauth status && service identity status ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-10-14 18:01:15 UTC; 36min ago Docs: https://httpd.apache.org/docs/2.4/ Process: 99 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 132 (apache2) CGroup: /system.slice/apache2.service ├─132 /usr/sbin/apache2 -k start ├─138 /usr/sbin/apache2 -k start └─139 /usr/sbin/apache2 -k start Oct 14 18:01:15 gts0001 systemd[1]: Starting The Apache HTTP Server... Oct 14 18:01:15 gts0001 apachectl[124]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 3.230.225.77. Set the 'ServerName' directive globally to suppress this message Oct 14 18:01:15 gts0001 systemd[1]: Started The Apache HTTP Server. ● oxauth.service - Oxauth service Loaded: loaded (/lib/systemd/system/oxauth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-10-14 18:06:51 UTC; 30min ago Process: 457 ExecStart=/opt/dist/scripts/oxauth start (code=exited, status=0/SUCCESS) Main PID: 483 (java) CGroup: /system.slice/oxauth.service └─483 /opt/jre/bin/java -server -Xms128m -Xmx1864m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/oxauth -Dlog.base=/opt/gluu/jetty/oxauth -Dpython.home=/opt/jython -Djetty.home=/opt/jetty -Djetty.b> Oct 14 18:06:07 gts0001 oxauth[483]: 2022-10-14 18:06:07.793:INFO::main: Logging initialized @754ms to org.eclipse.jetty.util.log.StdErrLog Oct 14 18:06:08 gts0001 oxauth[483]: 2022-10-14 18:06:08.161:INFO::main: Console stderr/stdout captured to /opt/gluu/jetty/oxauth/logs/2022_10_14.jetty.log Oct 14 18:06:15 gts0001 oxauth[457]: . . Oct 14 18:06:15 gts0001 oxauth[483]: WARNING: An illegal reflective access operation has occurred Oct 14 18:06:15 gts0001 oxauth[483]: WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/opt/jetty-9.4/temp/jetty-localhost-8081-oxauth_war-_oxauth-any-4118972478567405148/webapp/WEB-INF/lib/weld-core> Oct 14 18:06:15 gts0001 oxauth[483]: WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1 Oct 14 18:06:15 gts0001 oxauth[483]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Oct 14 18:06:15 gts0001 oxauth[483]: WARNING: All illegal access operations will be denied in a future release Oct 14 18:06:51 gts0001 oxauth[457]: . . . . . . . . OK Fri Oct 14 18:06:51 UTC 2022 Oct 14 18:06:51 gts0001 systemd[1]: Started Oxauth service. ● identity.service - Identity service Loaded: loaded (/lib/systemd/system/identity.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-10-14 18:07:35 UTC; 34min ago Process: 738 ExecStart=/opt/dist/scripts/identity start (code=exited, status=0/SUCCESS) Main PID: 764 (java) CGroup: /system.slice/identity.service └─764 /opt/jre/bin/java -server -Xms128m -Xmx2796m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/identity -Dlog.base=/opt/gluu/jetty/identity -Dpython.home=/opt/jython -Dorg.eclipse.jetty.server.Re> Oct 14 18:06:51 gts0001 identity[764]: 2022-10-14 18:06:51.903:INFO::main: Logging initialized @541ms to org.eclipse.jetty.util.log.StdErrLog Oct 14 18:06:52 gts0001 identity[764]: 2022-10-14 18:06:52.215:INFO::main: Console stderr/stdout captured to /opt/gluu/jetty/identity/logs/2022_10_14.jetty.log Oct 14 18:07:00 gts0001 identity[738]: . . Oct 14 18:07:00 gts0001 identity[764]: WARNING: An illegal reflective access operation has occurred Oct 14 18:07:00 gts0001 identity[764]: WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/opt/jetty-9.4/temp/jetty-localhost-8082-identity_war-_identity-any-264007073378687847/webapp/WEB-INF/lib/weld> Oct 14 18:07:00 gts0001 identity[764]: WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1 Oct 14 18:07:00 gts0001 identity[764]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Oct 14 18:07:00 gts0001 identity[764]: WARNING: All illegal access operations will be denied in a future release Oct 14 18:07:35 gts0001 identity[738]: . . . . . . . . OK Fri Oct 14 18:07:35 UTC 2022 Oct 14 18:07:35 gts0001 systemd[1]: Started Identity service. This is my /etc/hosts file: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters 3.230.225.77 gts0001
Gluu 4.2.3 Ubuntu 20.04
closed

Answers

By Michael Schwartz Account Admin 14 Oct 2022 at 2:56 p.m. CDT

Copy
Michael Schwartz gravatar
You did not follow the instructions, which clearly say don't use `localhost` as the FQDN

By Danielle Keeling user 17 Oct 2022 at 2:05 a.m. CDT

Copy
Danielle Keeling gravatar
I updated the /etc/hosts file and am still getting these errors in the logs when trying to start the OpenDJ server: [17/Oct/2022:06:43:35 +0000] category=CORE severity=NOTICE msgID=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) [17/Oct/2022:06:43:36 +0000] category=PROTOCOL severity=NOTICE msgID=277 msg=Stopped listening for new connections on LDAPS Connection Handler 0.0.0.0 port 1636 [17/Oct/2022:06:43:36 +0000] category=PROTOCOL severity=NOTICE msgID=277 msg=Stopped listening for new connections on LDAP Connection Handler 0.0.0.0 port 1389 [17/Oct/2022:06:43:36 +0000] category=PROTOCOL severity=NOTICE msgID=277 msg=Stopped listening for new connections on Administration Connector 0.0.0.0 port 4444 [17/Oct/2022:06:43:39 +0000] category=BACKEND severity=NOTICE msgID=370 msg=The backend userRoot is now taken offline [17/Oct/2022:06:43:39 +0000] category=CORE severity=NOTICE msgID=203 msg=The Directory Server is now stopped This is my /etc/hosts file: 127.0.0.1 gts0001 3.230.225.77 gts0001.kubecost-gluu-test.com gts0001 #The following lines are desirable for IPV6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters What am I missing?

Post an answer