By: Ha Ro user 18 Dec 2017 at 7:35 p.m. CST

4 Responses
Ha Ro gravatar
Still fairly new to Gluu, so your patience appreciated. When upgraded from older version to 3.1.1, it borked the dev server. So I completely deep removed the newer and older versions of Gluu, deep removes. Then fresh install. That all seemed to okay. Then logged in and began filling in the values under Configuration > Organization Configuration and other areas. Maybe I made the wrong selection because after saving those changes, and then making a full server reboot, I can no longer login through the website: " Problem accessing /identity/home.htm. Reason:Service Unavailable" Reading through your search results, I think I tracked down the failing service as the idp service. Everything else appears to be starting okay. But I do not understand the output from Gluu well enough to make heads or tails about what to fix, or how to fix it at his stage. identity, oxauth, and oxauth-rp appear to all be running okay (I believe). service idp start Starting Jetty: . . . . . . . . . . . . . . FAILED Tue Dec 19 01:32:32 UTC 2017 Setup: VM: 4 cpus, 8 GB ram. Ubuntu 16.04.03 LTS. Gluu 3.1.1. Here is output info that is hopefully helpful: root@au1:/opt/gluu/jetty/idp# date Tue Dec 19 01:27:07 UTC 2017 root@au1:/opt/gluu/jetty/idp# ls -l total 20 -rw-r--r-- 1 jetty jetty 99 Dec 19 01:19 idp.state drwxr-xr-x 2 jetty jetty 4096 Dec 19 01:17 logs -rw-r--r-- 1 jetty jetty 4852 Dec 18 05:42 start.ini drwxr-xr-x 2 jetty jetty 4096 Dec 18 05:42 webapps cat idp.state STARTING org.eclipse.jetty.server.Server@2ef9b8bc STARTED org.eclipse.jetty.server.Server@2ef9b8bc root@au1:/opt/gluu/jetty/idp# ############################### /opt/gluu/jetty/idp/logs# cat 2017_12_19.stderrout.log 2017-12-19 01:17:38.258:INFO:oejs.Server:main: jetty-9.3.15.v20161220 2017-12-19 01:17:38.292:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:///opt/gluu/jetty/idp/webapps/] at interval 1 2017-12-19 01:17:45.039:INFO:oeja.AnnotationConfiguration:main: Scanning elapsed time=6015ms 2017-12-19 01:17:45.088:INFO:idp:main: No Spring WebApplicationInitializer types detected on classpath 2017-12-19 01:17:45.244:WARN:oejs.SecurityHandler:main: ServletContext@o.e.j.w.WebAppContext@57baeedf{/idp,file:///opt/jetty-9.3/temp/jetty-localhost-8086-idp.war-_idp-any-5382246284066801683.dir/webapp/,STARTING}{/idp.war} has uncovered http methods for path: /* 2017-12-19 01:17:45.439:INFO:idp:main: Initializing Spring root WebApplicationContext 2017-12-19 01:19:21.105:INFO:idp:main: Initializing Spring FrameworkServlet 'idp' 2017-12-19 01:19:21.658:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@57baeedf{/idp,file:///opt/jetty-9.3/temp/jetty-localhost-8086-idp.war-_idp-any-5382246284066801683.dir/webapp/,AVAILABLE}{/idp.war} 2017-12-19 01:19:21.680:INFO:oejs.AbstractConnector:main: Started ServerConnector@2becfd4c{HTTP/1.1,[http/1.1]}{localhost:8086} 2017-12-19 01:19:21.680:INFO:oejs.Server:main: Started @104233ms #############################3 cat start.ini # --------------------------------------- # Module: logging --module=logging ## Logging Configuration ## Configure jetty logging for default internal behavior STDERR output # -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog ## Configure jetty logging for slf4j # -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.Slf4jLog ## Configure jetty logging for java.util.logging # -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.JavaUtilLog ## Logging directory (relative to $jetty.base) # jetty.logging.dir=logs ## Whether to append to existing file # jetty.logging.append=false ## How many days to retain old log files # jetty.logging.retainDays=90 ## Timezone of the log timestamps # jetty.logging.timezone=GMT # --------------------------------------- # Module: server --module=server ### ThreadPool configuration ## Minimum number of threads # jetty.threadPool.minThreads=10 ## Maximum number of threads # jetty.threadPool.maxThreads=200 ## Thread idle timeout (in milliseconds) # jetty.threadPool.idleTimeout=60000 ### Common HTTP configuration ## Scheme to use to build URIs for secure redirects # jetty.httpConfig.secureScheme=https ## Port to use to build URIs for secure redirects # jetty.httpConfig.securePort=8443 ## Response content buffer size (in bytes) # jetty.httpConfig.outputBufferSize=32768 ## Max response content write length that is buffered (in bytes) # jetty.httpConfig.outputAggregationSize=8192 ## Max request headers size (in bytes) # jetty.httpConfig.requestHeaderSize=8192 ## Max response headers size (in bytes) # jetty.httpConfig.responseHeaderSize=8192 ## Whether to send the Server: header # jetty.httpConfig.sendServerVersion=true ## Whether to send the Date: header # jetty.httpConfig.sendDateHeader=false ## Max per-connection header cache size (in nodes) # jetty.httpConfig.headerCacheSize=512 ## Whether, for requests with content, delay dispatch until some content has arrived # jetty.httpConfig.delayDispatchUntilContent=true ## Maximum number of error dispatches to prevent looping # jetty.httpConfig.maxErrorDispatches=10 ## Maximum time to block in total for a blocking IO operation (default -1 is to use idleTimeout on progress) # jetty.httpConfig.blockingTimeout=-1 ### Server configuration ## Whether ctrl+c on the console gracefully stops the Jetty server # jetty.server.stopAtShutdown=true ## Timeout in ms to apply when stopping the server gracefully # jetty.server.stopTimeout=5000 ## Dump the state of the Jetty server, components, and webapps after startup # jetty.server.dumpAfterStart=false ## Dump the state of the Jetty server, components, and webapps before shutdown # jetty.server.dumpBeforeStop=false # --------------------------------------- # Module: http --module=http ### HTTP Connector Configuration ## Connector host/address to bind to # jetty.http.host=0.0.0.0 ## Connector port to listen on # jetty.http.port=8080 ## Connector idle timeout in milliseconds # jetty.http.idleTimeout=30000 ## Connector socket linger time in seconds (-1 to disable) # jetty.http.soLingerTime=-1 ## Number of acceptors (-1 picks default based on number of cores) # jetty.http.acceptors=-1 ## Number of selectors (-1 picks default based on number of cores) # jetty.http.selectors=-1 ## ServerSocketChannel backlog (0 picks platform default) # jetty.http.acceptorQueueSize=0 ## Thread priority delta to give to acceptor threads # jetty.http.acceptorPriorityDelta=0 ## HTTP Compliance: RFC7230, RFC2616, LEGACY # jetty.http.compliance=RFC7230 # --------------------------------------- # Module: http-forwarded --module=http-forwarded ### ForwardedRequestCustomizer Configuration # jetty.httpConfig.forwardedOnly=false # jetty.httpConfig.forwardedProxyAsAuthority=false # jetty.httpConfig.forwardedHeader=Forwarded # jetty.httpConfig.forwardedHostHeader=X-Forwarded-Host # jetty.httpConfig.forwardedServerHeader=X-Forwarded-Server # jetty.httpConfig.forwardedProtoHeader=X-Forwarded-Proto # jetty.httpConfig.forwardedForHeader=X-Forwarded-For # jetty.httpConfig.forwardedHttpsHeader=X-Proxied-Https # jetty.httpConfig.forwardedSslSessionIdHeader=Proxy-ssl-id # jetty.httpConfig.forwardedCipherSuiteHeader=Proxy-auth-cert # --------------------------------------- # Module: deploy --module=deploy # Monitored directory name (relative to $jetty.base) # jetty.deploy.monitoredDir=webapps # - OR - # Monitored directory path (fully qualified) # jetty.deploy.monitoredPath=/var/www/webapps # Defaults Descriptor for all deployed webapps # jetty.deploy.defaultsDescriptorPath=${jetty.base}/etc/webdefault.xml # Monitored directory scan period (seconds) # jetty.deploy.scanInterval=1 # Whether to extract *.war files # jetty.deploy.extractWars=true # --------------------------------------- # Module: jsp --module=jsp Appreciate any suggestions. Cheers!

By Mohib Zico staff 19 Dec 2017 at 6 a.m. CST

Mohib Zico gravatar
>> Then logged in and began filling in the values under Configuration > Organization Configuration and other areas. What values you inserted there? Generally you don't need to supply any value to run Gluu Server ( until & unless something is really important to inject ).

By Ha Ro user 19 Dec 2017 at 12:52 p.m. CST

Ha Ro gravatar
Entered items such as: - SMTP mail settings - DNS servers - Max log size from 200 MB to 1G - Allowing users to edit their own profile - Organization logo - Cache provider to REDIS STANDALONE (planning to cluster later) - Clicked Add base DN to add: o=zoe From my setup notes I think those were all the changes. The only I can guess might have caused problem? The log file size? The cache provider? the added DN? Something else? Thanks.

By Mohib Zico staff 19 Dec 2017 at 5:04 p.m. CST

Mohib Zico gravatar
>> Clicked Add base DN to add: o=zoe This should be 'o=gluu' all the time because Gluu Server run on 'o=gluu' baseDN. >>> Cache provider to REDIS STANDALONE (planning to cluster later) For cluster we have a complete solution named 'Cluster Manager' soon; which will install cluster 'on the fly'.

By Ha Ro user 19 Dec 2017 at 6:53 p.m. CST

Ha Ro gravatar
What is the purpose of the "Add base DN" feature then? I kept the default o=gluu, but added a second using that interface. What does "soon" mean? We are trying to get Gluu live by early January, and clustering is important. I was just planning to follow the existing cluster directions, but if there is an easier way ready for production by January, I am all for that. Can you point me to information about it? Meanwhile, I gave up and just uninstalled and reinstalled Gluu fresh again, since I hadn't gotten very far with the data entry. Since this is the dev server, I'll leave it default baseDN and memcache for now, but I'll need to start setting up the cluster in a week or so. Cheers!