By: Anthony Kamau user 20 Mar 2017 at 8:37 p.m. CDT

9 Responses
Anthony Kamau gravatar

I've read the other 503 Service Unavailable ticket and I'm surprised to see that on my installation, there's no tomcat installed. Yet, after initial installation, the GLUU control panel/interface displayed without error. After a reboot though, I can't seem to get out of this 503 error.

Below are links to requested info (barring the tomcat stuff):

Hopefully we can determine the issue soon.

Regards, ak.

Update

Workaround - hopefully this helps the next user with the same issue!

TL;DR

login to chroot environment
cd /etc/init.d
./identity stop
./oxauth stop
./solserver stop
./idp stop
./idp start
./solserver start
./oxauth start
./identity start

By Sahil Arora staff 20 Mar 2017 at 10:17 p.m. CDT

Sahil Arora gravatar

Hi Anthony,

Jetty replaces Tomcat as servlet container in Gluu 3.0 version. Please run "service identity restart" and share error from logs under /opt/gluu/jetty/identity/

By Anthony Kamau user 21 Mar 2017 at 4:59 a.m. CDT

Anthony Kamau gravatar

Thanks for quick response, Sahil.

However, as per your request, it looks like I don't have an identity service - what could have gone wrong?

# service identity restart
Failed to restart identity.service: Unit identity.service not found.

The odd thing is that it worked soon after installation. In any case, if you need to troubleshoot the issue via something like TeamViewer, I'm more than willing to make that happen on my end.

Regards, ak.

By Anthony Kamau user 21 Mar 2017 at 5:09 a.m. CDT

Anthony Kamau gravatar

Wait a sec - just discovered that there's such a service in the chroot env:

# service gluu-server-3.0.1 login
gluu-server-3.0.1 is running...
logging in...
root@gluusvr:~# service identity restart
Stopping Jetty: start-stop-daemon: warning: failed to kill 10671: No such process
1 pids were not killed
No process in pidfile '/var/run/identity.pid' found running; none killed.
OK
Starting Jetty: . . . . . . . OK Tue Mar 21 10:04:42 UTC 2017
root@gluusvr:~# 

Why would it not start automatically?

However, despite that, it still doesn't bring up the web console. But the error has changed to something alluding to a rewrite gone wrong:

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept cookies.

Will post logs tomorrow morning.

Regards, ak.

By Anthony Kamau user 21 Mar 2017 at 2:56 p.m. CDT

Anthony Kamau gravatar

Good morning.

I've gone to the logs directory /opt/gluu/jetty/identity/logs and seen several log files in there. Any particular one you'd like to see or all of them?:

root@gluusvr:/opt/gluu/jetty/identity/logs# ls -al
total 3564
drwxr-xr-x 2 jetty jetty    4096 Mar 21 21:09 .
drwxr-xr-x 7 jetty jetty    4096 Mar 21 21:09 ..
-rw-r--r-- 1 jetty jetty   79183 Mar  3 16:53 2017_03_03.stderrout.log
-rw-r--r-- 1 jetty jetty  632438 Mar 21 21:16 2017_03_21.stderrout.log
-rw-r--r-- 1 jetty jetty  954340 Mar 21 21:09 2017_03_21.stderrout.log.100920635
-rw-r--r-- 1 jetty jetty   75420 Mar  3 16:52 oxtrust-2017-03-03-1.log
-rw-r--r-- 1 jetty jetty 1574571 Mar 21 21:16 oxtrust.log
-rw-r--r-- 1 jetty jetty       0 Mar  3 16:43 oxtrust_apachehc.log
-rw-r--r-- 1 jetty jetty     154 Mar  3 16:43 oxtrust_cache_refresh-2017-03-03-1.log
-rw-r--r-- 1 jetty jetty     308 Mar 21 21:09 oxtrust_cache_refresh.log
-rw-r--r-- 1 jetty jetty       0 Mar  3 16:43 oxtrust_cache_refresh_python.log
-rw-r--r-- 1 jetty jetty     157 Mar  3 16:43 oxtrust_persistence-2017-03-03-1.log
-rw-r--r-- 1 jetty jetty     314 Mar 21 21:09 oxtrust_persistence.log
-rw-r--r-- 1 jetty jetty    4876 Mar  3 16:53 oxtrust_persistence_ldap_statistics-2017-03-03-1.log
-rw-r--r-- 1 jetty jetty  280037 Mar 22 06:53 oxtrust_persistence_ldap_statistics.log
-rw-r--r-- 1 jetty jetty       0 Mar  3 16:43 oxtrust_script.log
-rw-r--r-- 1 jetty jetty     282 Mar 21 21:09 start.log

Regards, ak.

By Sahil Arora staff 21 Mar 2017 at 5:19 p.m. CDT

Sahil Arora gravatar

Please check for any errors in oxtrust.log. also, make sure firewall is not blocking 80,443 ports.

By Anthony Kamau user 22 Mar 2017 at 4:15 a.m. CDT

Anthony Kamau gravatar

Apologies for late response - got busy with other priorities.

I deleted all the logs files so you can see exactly what is happening upon reboot. Before reboot however, I did a server upgrade - apt dist-upgrade - to ensure I wasn't missing some security patches. I then stopped Gluu service and rebooted the server. Upon login, the Gluu service had to be started manually. I then logged into the chroot environment and also manually started the identity service. Below are the logfiles that were then created:

# ls -AlS /opt/gluu-server-3.0.1/opt/gluu/jetty/identity/logs/
total 748
-rw-r--r-- 1 998 998 369758 Mar 22 19:52 2017_03_22.stderrout.log
-rw-r--r-- 1 998 998 366411 Mar 22 19:52 oxtrust.log
-rw-r--r-- 1 998 998  11040 Mar 22 20:14 oxtrust_persistence_ldap_statistics.log
-rw-r--r-- 1 998 998    157 Mar 22 19:51 oxtrust_persistence.log
-rw-r--r-- 1 998 998    154 Mar 22 19:51 oxtrust_cache_refresh.log
-rw-r--r-- 1 998 998     94 Mar 22 19:50 start.log
-rw-r--r-- 1 998 998      0 Mar 22 19:50 oxtrust_apachehc.log
-rw-r--r-- 1 998 998      0 Mar 22 19:50 oxtrust_cache_refresh_python.log
-rw-r--r-- 1 998 998      0 Mar 22 19:50 oxtrust_script.log

Here are pastebin links to non-empty logs:

Regards, ak.

Edit: Forgot to mention that I'm still getting the latter error:

Firefox:
========

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept cookies.

Chrome:
=======
This page isn’t working

gluusvr.DOMAIN.com redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS

No internal firewall so ports are not blocked. I'm not blocking any cookies either as both browsers allude to.

By Aliaksandr Samuseu staff 23 Mar 2017 at 9:56 a.m. CDT

Aliaksandr Samuseu gravatar

Hi, Anthony.

After a reboot though, I can't seem to get out of this 503 error.

Please check this post. There is a bug (it will be fixed in 3.0.2) which prevents some services from starting when the box/whole Gluu service is restarted. You need to manually start/restart some services after moving in the container.

By Anthony Kamau user 23 Mar 2017 at 2:36 p.m. CDT

Anthony Kamau gravatar

Thanks Aliaksandr.

All fixed.

It might be a good idea to circulate this amongst your support team so it is the first thing tried as opposed to collecting so much data when there's a known workaround.

Any idea when 3.0.2 is coming out?

Regards, ak.

By Sahil Arora staff 28 Mar 2017 at 10:08 p.m. CDT

Sahil Arora gravatar

Thanks Anthony, we are closing this issue. Please check build roadmap here