Shilen Patel 5:31 PM
|
It's a little strange to see the shib config reloaded on the WS container every now and then. Not a problem but made me wonder for a second if I was looking at the wrong place :slightly_smiling_face:Chris Hyzer 5:33 PM
|
is shibd running on ws container????
|
5:33
|
shouldnt be i think...Shilen Patel 5:33 PM
|
no but i think since the apache config is there, it'll reload the shib config at some interval.Chris Hyzer 5:33 PM
|
apache config shouldnt be there either
|
5:33
|
which apache config is there?
|
5:33
|
and what is your docker run command?Shilen Patel 5:34 PM
|
this /etc/httpd/conf.d/shib.conf
|
New
|
5:34
|
seems to cause this:
|
shibd;native.log;;;2020-05-01 17:15:00 INFO Shibboleth.Config : loaded XML resource (/etc/shibboleth/shibboleth2.xml)
|
5:36
|
docker run --log-driver json-file --log-opt max-size=50m --log-opt max-file=20 -e TZ=America/New_York -e GROUPER_MAX_MEMORY='3g' --restart always --detach --mount type=bind,src=/srv/grouperContainer/logs/grouper-ws-logs,dst=/opt/grouper/logs --name grouper-ws --publish 8443:443 my-grouper-2.5:latest wsChris Hyzer 5:38 PM
|
we can fix that soon.
|
5:38
|
in your dockerfile for now you could remove that if you likeShilen Patel 5:38 PM
|
nah, not hurting anything so i'll just wait
|
Bug
Minor