[
https://issues.apache.org/jira/browse/TS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106067#comment-13106067
]
Leif Hedstrom commented on TS-955:
----------------------------------
Right. That happens because the write on the log doesn't seem to get flushed.
And therefore the text log file is never created, so the test to read the log
fails (since the filevdoesnt exist).
> TS-168 breaks regressions for TextLog
> -------------------------------------
>
> Key: TS-955
> URL: https://issues.apache.org/jira/browse/TS-955
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.1.1
> Reporter: Leif Hedstrom
> Assignee: Zhao Yongming
> Priority: Critical
> Fix For: 3.1.1
>
>
> With the fixes from TS-168, the logging regressions can fail if you run the
> traffic_server -R 1 more than once. The first run always succeeds, but the
> 2nd and subsequent run can fail. What seems to happen is that the (small) log
> is not flushed, and the log is not created until the first flush happens. So,
> everything looks like it works, up until we (5s after log creation) try to
> read the log. The log then doesn't exist, and the regression in
> log_test_handler() fails (since, the file can't be open nor read).
> I've tracked this down to the commit for TS-168, and also traced through the
> test in gdb, and as far as I can tell, the flush never happens, which means
> the log write never happens, and hence, the log file creation never happens
> either.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
