By: evan gg user 15 May 2020 at 12:16 p.m. CDT

3 Responses
evan gg gravatar
## Description Upon booting the host the container boots as expected and all of the services start without issues. When I attempt to restart the `idp` service though, it won't come up. I've stumbled upon the various (older) issues that mostly mention the boot sequence of the services (e.g. stopping oxTrust, starting `idp` and then getting oxTrust back up again), and I've had no luck with those solutions. I started looking into the issue, and it seemed to me that it's some kind of timeout, maybe the default resources given to the `idp` were insufficient, hence I've bumped the JVM heap size and ran startup command manually: ``` su - jetty -c "/opt/jre/bin/java -server -Xss240m -Xms1g -Xmx2g -XX:MaxMetaspaceSize=1g -XX:MaxGCPauseMillis=4000 -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/idp -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/idp -jar /opt/jetty/start.jar jetty.http.port=8086" ``` As shown in the log files I've attached, startup stops at: ``` 2020-05-15 16:52:27,014 - - DEBUG [net.shibboleth.idp.attribute.filter.spring.BaseFilterParser:169] - Element 'AttributeFilterPolicy' 'id' attribute 'SiteApp1' is mapped to '/AttributeFilterPolicyGroup:ShibbolethFilterPolicy/AttributeFilterPolicy:SiteApp1' 2020-05-15 16:52:27,015 - - DEBUG [net.shibboleth.idp.attribute.filter.spring.impl.AttributeFilterPolicyParser:86] - Parsing configuration for attribute filter policy: SiteApp1 ``` What I noticed is that if that step fails (e.g. I intentionally tweeked `/opt/shibboleth-idp/conf/attribute-filter.xml` to make it fail) the service will boot as expected (although no attributes will be released to the SP, since the parsing of the `attribute-filter` failed. If I had to guess, it's either some special sequence that I have to restart services with (although restarting the container should have fixed that) or there's some kind of cached state that won't let the service start. Otherwise, I have no hint whatsoever, the logs don't indicate what the issue is. ## Things I've tried 1. Restart the whole container: Doesn't help with the issue, still the `idp` service fails. 2. Attempted to find any issues with the `attribute-filter.xml`: It seems valid to me. 3. Skimmed other log files to find related issues. 4. Bumped memory resources in almost all services: No change. ## Additional Information The host machine has: - 8GB RAM - 3 vCPUs - 50 GB storage - Gluu server 4.1.1 - oxShibbolethIDP version: 4.1.1 ## Config files I've attached a zip with: 1. `idp-process.log` 2. `attribute-filter.xml` 3. `jetty/idp/logs/2020_05_15.jetty.log` If you need any additional info let me know.

By Michael Schwartz staff 25 May 2020 at 12:23 p.m. CDT

Michael Schwartz gravatar
Re-assigning to @Sahil.Arora

By Sahil Arora staff 26 May 2020 at 12:46 p.m. CDT

Sahil Arora gravatar
Hi Evan, What are the other components have you installed? and what was initial memory allocated during

By Sahil Arora staff 05 Jun 2020 at 1:11 p.m. CDT

Sahil Arora gravatar
Hi Evan, I'm not able to reproduce this issue at my end. Could you please share the information requested in my previous update? Thanks