Description
Andy Morgan 6:17 PM
On the subject of logging... There are access logs being written inside the container at /opt/tomee/logs/. These are caused by the access log valve in /opt/tomee/conf/server.xml. That should be turned off or redirected somehow so that we don't write logs inside the container.
Paul Caskey 6:32 PM
I'm working on fixing this same thing for the shib IdP. In that case, they'll be sent to stdout using the mkfifo thing that we do in other places...
Andy Morgan 8:05 PM
will we end up with some double-logging? I'm already getting the Apache access log in the container output, like this:
httpd;access_log;local;local;172.17.0.1 - morgan [14/May/2020:16:36:30 -0700] "GET /grouper/grouperUi/app/UiV2Group.addMemberFilter?groupId=3d04bb336ce44219b879af488207a680&name=&start=0 HTTP/1.1" 200 35 "https://grouper.local.iam.oregonstate.edu/grouper/grouperUi/app/UiV2Main.index?operation=UiV2Group.viewGroup&groupId=3d04bb336ce44219b879af488207a680" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:76.0) Gecko/20100101 Firefox/76.0"
Paul Caskey 9:51 PM
Good point. There's no httpd for shib. Perhaps for grouper, it should just be turned off.
New
Paul Caskey 9:55 PM
I think we'd just need to comment out lines 157-159 of this file: https://github.internet2.edu/docker/grouper/blob/master/container_files/tomee/conf/server.xml
GitHub EnterpriseGitHub Enterprise
docker/grouper
Grouper Docker images. Contribute to docker/grouper development by creating an account on GitHub.
3 replies
Last reply today at 8:17 AMView thread
I think we'd just need to comment out lines 157-159 of this file: https://github.internet2.edu/docker/grouper/blob/master/container_files/tomee/conf/server.xml
GitHub EnterpriseGitHub Enterprise
docker/grouper
Grouper Docker images. Contribute to docker/grouper development by creating an account on GitHub.
3 replies
Carey Black 12 hours ago
I am not sure that is always wise.....
It is also possible to use "only tomee" in the container too.
So if not "apache" then no logs? (edited)
Carey Black 12 hours ago
Maybe I could suggest another env var to enable/disable logs when the thing in question is "on"?
so
GROUPER_RUN_APACHE='true' implies GROUPER_APACHE_LOG='true'
and a deployer could choose to turn it off with an env setting.
and
GROUPER_RUN_APACHE='false'
forces
GROUPER_APACHE_LOG='false'
Sane for the "GROUPER_RUN_TOMEE" env var.
Paul Caskey 3 hours ago
seems like a good idea to me!