I can't access Gluu UI

By: Joseph Ssebagala user 14 Mar 2021 at 7:15 p.m. CDT

4 Responses
Joseph Ssebagala gravatar
### Deployment environment * Ubuntu 20.4 VM running on Proxmox (Qemu virt) * Mem 4G * CPU 2 * Storage 80G ### Expected Result Access to the web UI ### Actual results At first I was getting a 503. That's error, I rebooted Then `Oops, Something wrong happened` ### Some service status - running successfully ``` root@gluu:~# service apache2 status ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-03-14 18:53:59 EDT; 3s ago Docs: https://httpd.apache.org/docs/2.4/ Process: 2783 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 2787 (apache2) CGroup: /system.slice/apache2.service ├─2787 /usr/sbin/apache2 -k start ├─2788 /usr/sbin/apache2 -k start └─2789 /usr/sbin/apache2 -k start Mar 14 18:53:59 gluu systemd[1]: Starting The Apache HTTP Server... Mar 14 18:53:59 gluu systemd[1]: Started The Apache HTTP Server. root@gluu:~# root@gluu:~# root@gluu:~# service oxauth status ● oxauth.service - Oxauth service Loaded: loaded (/lib/systemd/system/oxauth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-03-14 18:41:43 EDT; 17min ago Process: 555 ExecStart=/opt/dist/scripts/oxauth start (code=exited, status=0/SUCCESS) Main PID: 607 (java) CGroup: /system.slice/oxauth.service └─607 /opt/jre/bin/java -server -Xms128m -Xmx512m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/oxauth -Dlog.base=/> Mar 14 18:40:42 gluu oxauth[555]: . Mar 14 18:40:42 gluu oxauth[607]: 2021-03-14 22:40:42.141:INFO::main: Console stderr/stdout captured to /opt/gluu/jetty/oxauth/logs/2021_03_14.jetty.log Mar 14 18:41:12 gluu oxauth[555]: . . . . . . . Mar 14 18:41:12 gluu oxauth[607]: WARNING: An illegal reflective access operation has occurred Mar 14 18:41:12 gluu oxauth[607]: WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/opt/jetty-9.4/temp/jetty-localho> Mar 14 18:41:12 gluu oxauth[607]: WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1 Mar 14 18:41:12 gluu oxauth[607]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Mar 14 18:41:12 gluu oxauth[607]: WARNING: All illegal access operations will be denied in a future release Mar 14 18:41:43 gluu oxauth[555]: . . . . . . . OK Sun Mar 14 18:41:43 EDT 2021 Mar 14 18:41:43 gluu systemd[1]: Started Oxauth service. root@gluu:~# service casa status ● casa.service - Casa service Loaded: loaded (/lib/systemd/system/casa.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-03-14 18:43:24 EDT; 16min ago Process: 818 ExecStart=/opt/dist/scripts/casa start (code=exited, status=0/SUCCESS) Main PID: 956 (java) CGroup: /system.slice/casa.service └─956 /opt/jre/bin/java -server -Xms128m -Xmx154m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/casa -Dlog.base=/op> Mar 14 18:41:43 gluu systemd[1]: Starting Casa service... Mar 14 18:41:52 gluu casa[818]: Starting Jetty: . . Mar 14 18:41:52 gluu casa[956]: 2021-03-14 22:41:52.722:INFO::main: Logging initialized @8352ms to org.eclipse.jetty.util.log.StdErrLog Mar 14 18:41:58 gluu casa[818]: . Mar 14 18:41:58 gluu casa[956]: 2021-03-14 22:41:58.501:INFO::main: Console stderr/stdout captured to /opt/gluu/jetty/casa/logs/2021_03_14.jetty.log Mar 14 18:43:24 gluu casa[818]: . . . . . . . . . . . . . . . . . . . . OK Sun Mar 14 18:43:24 EDT 2021 Mar 14 18:43:24 gluu systemd[1]: Started Casa service. root@gluu:~# service identity status ● identity.service - Identity service Loaded: loaded (/lib/systemd/system/identity.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-03-14 18:44:43 EDT; 17min ago Process: 820 ExecStart=/opt/dist/scripts/identity start (code=exited, status=0/SUCCESS) Main PID: 950 (java) CGroup: /system.slice/identity.service └─950 /opt/jre/bin/java -server -Xms128m -Xmx769m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/identity -Dlog.base> Mar 14 18:41:58 gluu identity[820]: . Mar 14 18:41:58 gluu identity[950]: 2021-03-14 22:41:58.835:INFO::main: Console stderr/stdout captured to /opt/gluu/jetty/identity/logs/2021_03_14.jetty.log Mar 14 18:43:34 gluu identity[820]: . . . . . . . . . . . . . . . . . . . . . . . Mar 14 18:43:34 gluu identity[950]: WARNING: An illegal reflective access operation has occurred Mar 14 18:43:34 gluu identity[950]: WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/opt/jetty-9.4/temp/jetty-local> Mar 14 18:43:34 gluu identity[950]: WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1 Mar 14 18:43:34 gluu identity[950]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Mar 14 18:43:34 gluu identity[950]: WARNING: All illegal access operations will be denied in a future release Mar 14 18:44:43 gluu identity[820]: . . . . . . . . . . . . . . . . OK Sun Mar 14 18:44:43 EDT 2021 Mar 14 18:44:43 gluu systemd[1]: Started Identity service. ``` I also noticed some jetty(jboss) related issues on `oxAuth` and `indentity`. ``` Mar 14 18:43:34 gluu identity[950]: WARNING: An illegal reflective access operation has occurred Mar 14 18:43:34 gluu identity[950]: WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/opt/jetty-9.4/temp/jetty-local> Mar 14 18:43:34 gluu identity[950]: WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1 Mar 14 18:43:34 gluu identity[950]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations Mar 14 18:43:34 gluu identity[950]: WARNING: All illegal access operations will be denied in a future release ``` Please let me know if there's something more I should provide. #### A couple of things I had missed * Status: Failed #### Scim ``` ● scim.service - scim service Loaded: loaded (/lib/systemd/system/scim.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-03-14 18:41:48 EDT; 3h 25min ago Process: 822 ExecStart=/opt/dist/scripts/scim start (code=exited, status=1/FAILURE) Mar 14 18:41:43 gluu systemd[1]: Starting scim service... Mar 14 18:41:48 gluu scim[822]: Starting Jetty: FAILED Sun Mar 14 18:41:48 EDT 2021 Mar 14 18:41:48 gluu systemd[1]: scim.service: Control process exited, code=exited, status=1/FAILURE Mar 14 18:41:48 gluu systemd[1]: scim.service: Failed with result 'exit-code'. Mar 14 18:41:48 gluu systemd[1]: Failed to start scim service. ``` #### journalctl -xe ``` -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit fido2.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Mar 14 22:05:01 gluu systemd[1]: fido2.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit fido2.service has entered the 'failed' state with result 'exit-code'. Mar 14 22:05:01 gluu systemd[1]: Failed to start fido2 service. -- Subject: A start job for unit fido2.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit fido2.service has finished with a failure. -- -- The job identifier is 358 and the job result is failed. Mar 14 22:11:18 gluu systemd[1]: Starting scim service... -- Subject: A start job for unit scim.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit scim.service has begun execution. -- -- The job identifier is 405. Mar 14 22:11:22 gluu scim[9553]: Starting Jetty: FAILED Sun Mar 14 22:11:22 EDT 2021 Mar 14 22:11:22 gluu systemd[1]: scim.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit scim.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Mar 14 22:11:22 gluu systemd[1]: scim.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit scim.service has entered the 'failed' state with result 'exit-code'. Mar 14 22:11:22 gluu systemd[1]: Failed to start scim service. -- Subject: A start job for unit scim.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit scim.service has finished with a failure. -- -- The job identifier is 405 and the job result is failed. Mar 14 22:14:50 gluu systemd[1]: Starting scim service... -- Subject: A start job for unit scim.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit scim.service has begun execution. -- -- The job identifier is 452. Mar 14 22:14:54 gluu scim[9732]: Starting Jetty: FAILED Sun Mar 14 22:14:54 EDT 2021 Mar 14 22:14:54 gluu systemd[1]: scim.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit scim.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Mar 14 22:14:54 gluu systemd[1]: scim.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit scim.service has entered the 'failed' state with result 'exit-code'. Mar 14 22:14:54 gluu systemd[1]: Failed to start scim service. -- Subject: A start job for unit scim.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit scim.service has finished with a failure. -- -- The job identifier is 452 and the job result is failed. ``` #### Fido2 ``` ● fido2.service - fido2 service Loaded: loaded (/lib/systemd/system/fido2.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-03-14 18:40:42 EDT; 3h 22min ago Process: 554 ExecStart=/opt/dist/scripts/fido2 start (code=exited, status=1/FAILURE) Mar 14 18:40:37 gluu systemd[1]: Starting fido2 service... Mar 14 18:40:42 gluu fido2[554]: Starting Jetty: FAILED Sun Mar 14 18:40:42 EDT 2021 Mar 14 18:40:42 gluu systemd[1]: fido2.service: Control process exited, code=exited, status=1/FAILURE Mar 14 18:40:42 gluu systemd[1]: fido2.service: Failed with result 'exit-code'. Mar 14 18:40:42 gluu systemd[1]: Failed to start fido2 service. ``` #### journalctl -xe ``` -- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit systemd-tmpfiles-clean.service has begun execution. -- -- The job identifier is 307. Mar 14 18:54:55 gluu systemd[1]: systemd-tmpfiles-clean.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state. Mar 14 18:54:55 gluu systemd[1]: Finished Cleanup of Temporary Directories. -- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit systemd-tmpfiles-clean.service has finished successfully. -- -- The job identifier is 307. Mar 14 19:17:02 gluu CRON[3649]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 14 19:17:02 gluu CRON[3651]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 14 19:17:02 gluu CRON[3649]: pam_unix(cron:session): session closed for user root Mar 14 19:41:45 gluu systemd[1]: Starting Daily apt download activities... -- Subject: A start job for unit apt-daily.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apt-daily.service has begun execution. -- -- The job identifier is 311. Mar 14 19:41:53 gluu systemd[1]: apt-daily.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit apt-daily.service has successfully entered the 'dead' state. Mar 14 19:41:53 gluu systemd[1]: Finished Daily apt download activities. -- Subject: A start job for unit apt-daily.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apt-daily.service has finished successfully. -- -- The job identifier is 311. Mar 14 20:17:01 gluu CRON[5672]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 14 20:17:01 gluu CRON[5673]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 14 20:17:01 gluu CRON[5672]: pam_unix(cron:session): session closed for user root Mar 14 21:17:01 gluu CRON[7644]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 14 21:17:01 gluu CRON[7645]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 14 21:17:01 gluu CRON[7644]: pam_unix(cron:session): session closed for user root Mar 14 22:04:56 gluu systemd[1]: Starting fido2 service... -- Subject: A start job for unit fido2.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit fido2.service has begun execution. -- -- The job identifier is 358. Mar 14 22:05:01 gluu fido2[9263]: Starting Jetty: FAILED Sun Mar 14 22:05:01 EDT 2021 Mar 14 22:05:01 gluu systemd[1]: fido2.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit fido2.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Mar 14 22:05:01 gluu systemd[1]: fido2.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit fido2.service has entered the 'failed' state with result 'exit-code'. Mar 14 22:05:01 gluu systemd[1]: Failed to start fido2 service. -- Subject: A start job for unit fido2.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit fido2.service has finished with a failure. -- -- The job identifier is 358 and the job result is failed. ```
Gluu 4.2.3 Ubuntu 20.4
closed

Answers

By Mobarak Hosen Shakil staff 15 Mar 2021 at 10:57 a.m. CDT

Copy
Mobarak Hosen Shakil gravatar
I think you are running out of memory. 4GB is not enough to use all of the services you are trying to run. Please see this doc: https://gluu.org/docs/gluu-server/4.2/installation-guide/ Also use below command to check that `opendj` is running or not: ``` service opendj status ``` Thanks & Regards ~ Shakil

By Joseph Ssebagala user 15 Mar 2021 at 2:33 p.m. CDT

Copy
Joseph Ssebagala gravatar
Thanks for your pointer, Shakil. My bad indeed, I missed that piece of the docs. Is there a way to disable some of the services so that they wouldn't affect other services that are required for a minimal installation? I checked and foud that `opendj` wasn't running but was able able to start up successfully. #### Before ``` ● opendj.service - OpenDJ Directory Service Loaded: loaded (/etc/systemd/system/opendj.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sun 2021-03-14 23:17:57 EDT; 16h ago Process: 62 ExecStart=/opt/opendj/bin/start-ds (code=exited, status=0/SUCCESS) Main PID: 417 (code=killed, signal=KILL) Mar 14 18:40:31 gluu start-ds[418]: [14/Mar/2021:22:40:30 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend metric containing 36 entries has started Mar 14 18:40:32 gluu start-ds[418]: [14/Mar/2021:22:40:32 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend userRoot containing 203 entries has started Mar 14 18:40:32 gluu start-ds[418]: [14/Mar/2021:22:40:32 +0000] category=EXTENSIONS severity=NOTICE msgID=221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain nam> Mar 14 18:40:33 gluu start-ds[418]: [14/Mar/2021:22:40:33 +0000] category=CORE severity=NOTICE msgID=135 msg=The Directory Server has started successfully Mar 14 18:40:33 gluu start-ds[418]: [14/Mar/2021:22:40:33 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class or> Mar 14 18:40:35 gluu start-ds[418]: [14/Mar/2021:22:40:35 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on Administration Connector loc> Mar 14 18:40:35 gluu start-ds[418]: [14/Mar/2021:22:40:35 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on LDAPS Connection Handler loc> Mar 14 18:40:37 gluu systemd[1]: Started OpenDJ Directory Service. Mar 14 23:17:57 gluu systemd[1]: opendj.service: Main process exited, code=killed, status=9/KILL Mar 14 23:17:57 gluu systemd[1]: opendj.service: Failed with result 'signal'. ``` #### After ``` ● opendj.service - OpenDJ Directory Service Loaded: loaded (/etc/systemd/system/opendj.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-03-15 15:23:06 EDT; 7s ago Process: 128801 ExecStart=/opt/opendj/bin/start-ds (code=exited, status=0/SUCCESS) Main PID: 128848 (java) CGroup: /system.slice/opendj.service └─128848 /opt/jre/bin/java -server -Xms512m -Xmx1280m -XX:+UseCompressedOops -Dorg.opends.server.scriptName=start-ds org.opends.server.core.DirectoryServer --configFile > Mar 15 15:22:52 gluu start-ds[128849]: [15/Mar/2021:19:22:52 +0000] category=JVM severity=NOTICE msgID=19 msg=JVM Arguments: "-Xms512m", "-Xmx1280m", "-XX:+UseCompressedOops", "-Dorg> Mar 15 15:22:57 gluu start-ds[128849]: [15/Mar/2021:19:22:57 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend site containing 2 entries has started Mar 15 15:22:58 gluu start-ds[128849]: [15/Mar/2021:19:22:58 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend metric containing 37 entries has started Mar 15 15:23:00 gluu start-ds[128849]: [15/Mar/2021:19:23:00 +0000] category=BACKEND severity=NOTICE msgID=513 msg=The database backend userRoot containing 199 entries has started Mar 15 15:23:00 gluu start-ds[128849]: [15/Mar/2021:19:23:00 +0000] category=EXTENSIONS severity=NOTICE msgID=221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain > Mar 15 15:23:02 gluu start-ds[128849]: [15/Mar/2021:19:23:02 +0000] category=CORE severity=NOTICE msgID=135 msg=The Directory Server has started successfully Mar 15 15:23:02 gluu start-ds[128849]: [15/Mar/2021:19:23:02 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class> Mar 15 15:23:04 gluu start-ds[128849]: [15/Mar/2021:19:23:04 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on LDAPS Connection Handler > Mar 15 15:23:04 gluu start-ds[128849]: [15/Mar/2021:19:23:04 +0000] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on Administration Connector > Mar 15 15:23:06 gluu systemd[1]: Started OpenDJ Directory Service. ```

By Mobarak Hosen Shakil staff 18 Mar 2021 at 10:10 a.m. CDT

Copy
Mobarak Hosen Shakil gravatar
If this is the test environment then I would like to suggest for a fresh installation with default setup. But If you want to keep as it is then you have to disable some services. **Apache, oxauth, identity. opendj** these are the default setup for running a Gluu Server. You can disable some services from Gluu GUI. Alternatively using command promt: ``` systemctl disable service-name service service-name disable ``` Regards ~ Shakil

By Mobarak Hosen Shakil staff 26 Mar 2021 at 11:02 a.m. CDT

Copy
Mobarak Hosen Shakil gravatar
please reopen the ticket if required. Regards ~ Shakil

Post an answer