Currently the Tomcat access log is disabled in server.xml. It should be enabled by default.
http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Access_Log_Valve
An upgrade script might be required.
How to enable Tomcat access log:
systemctl stop pki-tomcatd@pki-tomcat.service
server.xml
AccessLog
- <!-- <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/> - --> to receive <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
systemctl start pki-tomcatd@pki-tomcat.service
/var/lib/pki/pki-tomcat/logs
localhost_access_log.<date>.txt
IRC discussion concluded that enabling Tomcat access log by default may not be a best thing to do.[[br]]Access errors are already reported through catalina.out log.[[br]]We will farther discuss subject of logging to figure out right balance.[[br]]In the mean time, manual procedure to enable Tomcat access log is offered in comment:7.
catalina.out
attachment enable-tomcat-access-log.patch
git push Counting objects: 13, done. Delta compression using up to 4 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 643 bytes, done. Total 7 (delta 5), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/pki.git 0e625c6..618be8b master -> master
Metadata Update from @edewata: - Issue assigned to awnuk - Issue set to the milestone: 10.1 - 10/13 (October)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1128
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.