You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/01/16 02:30:34 UTC

[jira] [Commented] (TS-3303) tcpinfo: Log file can get closed when disk is full

    [ https://issues.apache.org/jira/browse/TS-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279658#comment-14279658 ] 

ASF subversion and git services commented on TS-3303:
-----------------------------------------------------

Commit 49a2c805ac0d5032de9c1fb35766e49bb18960e8 in trafficserver's branch refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=49a2c80 ]

TS-3303 tcpinfo: we can close the log file object multiple times


> tcpinfo: Log file can get closed when disk is full
> --------------------------------------------------
>
>                 Key: TS-3303
>                 URL: https://issues.apache.org/jira/browse/TS-3303
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Plugins
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 5.3.0
>
>
> It's unfortunate, but it seems that TSTextLogObjectWrite() returns TSError for both "disk full" and "write failed". I think, but not 100% sure, that this can trip us to delete the log object more than once, due to a race condition in the code.
> My suggestion is to just not close the log object, but hope that we the log rotation / cleanup code will free up disk space, such that future log writes succeeds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)