[ https://issues.apache.org/jira/browse/TS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627437#comment-14627437 ]
Ryo Okubo commented on TS-3749: ------------------------------- [~cqian] you can reproduce it by following procedures: 1. Enable error logging {noformat} CONFIG proxy.config.log.logging_enabled INT 3 {noformat} 2. Triger any event which causes logging error. When ATS responds "502 Cannot find server.", error log may be recorded. So setting a noexistent origin server to remap.config is a easy way. {noformat} $ echo "map / http://nonexistent.com/" > /path/to/remap.config $ curl -s -o /dev/null http://localhost/ {noformat} 3. Confirm error logs. {noformat} $ tailf /path/to/logfile_dir/error.log If loggins is working, you can show error logs. {noformat} > Error log isn't recorded > ------------------------ > > Key: TS-3749 > URL: https://issues.apache.org/jira/browse/TS-3749 > Project: Traffic Server > Issue Type: Bug > Components: Logging > Reporter: Ryo Okubo > Assignee: Crystal Qian > Priority: Blocker > Fix For: 6.1.0 > > > error.log has not been recorded after TS-1985. Enabling error logging and > specifying a format of error.log depended on pre-defined log format but this > logic was eliminated on the issue. > Error logging works fine when I tried to revert > [5c2b032fb9f8f05ae7be1794a3103140ffe7d07e|https://github.com/apache/trafficserver/commit/5c2b032fb9f8f05ae7be1794a3103140ffe7d07e]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)