[
https://issues.apache.org/jira/browse/TS-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059835#comment-14059835
]
David Carlin commented on TS-2925:
----------------------------------
Perhpas that explains my original comment, where I had hosts that had long been
switched to ascii mode, but squid.blog remained on the host. Log space
threshold was reached and it deleted all of the *.old log files, but kept
squid.blog? I am assuming log space threshold doesn't remove
squid.blog/squid.log only the *.old ones.
This has caused some space consumption issues for us, but there is a simple
workaround (delete the old binary log files). The primary annoyance is that
things don't start failing until long after the change is made.
> Changing logging mode breaks log rotation
> -----------------------------------------
>
> Key: TS-2925
> URL: https://issues.apache.org/jira/browse/TS-2925
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 4.0.2
> Reporter: David Carlin
> Assignee: Bryan Call
> Priority: Minor
> Labels: yahoo
> Fix For: sometime
>
>
> If you run a server with a logging mode of binary, traffic server
> automatically creates logs with .blog appended.
> If you then switch to ascii mode, it automatically starts appending .log but
> leaves squid.blog on the disk indefinitely. This eats up space that would
> otherwise be available for logging/log rotation activity. ATS seems to
> rotate out all of the old binary logs except 'squid.blog'.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
