#558 Enable Tomcat access log.
Closed: Fixed None Opened 9 years ago by edewata.

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:

  • stop server instance[[br]]for example: systemctl stop pki-tomcatd@pki-tomcat.service
  • go to server instance etc location[[br]]for example: /etc/pki/pki-tomcat
  • edit server.xml by removing comment tags from around AccessLog section[[br]]
     -  <!--
        <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"/>
  • start server instance[[br]]for example: systemctl start pki-tomcatd@pki-tomcat.service
  • check server instance log directory[[br]]for example: /var/lib/pki/pki-tomcat/logs[[br]]for presence of localhost_access_log.<date>.txt files

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.

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)

5 years ago

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.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata