[TS-306] Enable log rotation for diags.log

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.1.0
• Component/s: Logging
• Labels: newbie
• Assignee: Daniel Xu
• Reporter: Miles Libbey
• Created: 19/Apr/10 19:37
• Updated: 04/Feb/16 18:49
• Resolved: 30/Nov/15 19:31

Description

(from yahoo bug 913896)

Original description
by Leif Hedstrom 3 years ago at 2006-12-04 12:42

There might be reasons why this file might get filled up, e.g. libraries used by plugins producing output on STDOUT/STDERR. A few suggestions have been
made, to somehow rotate traffic.out. One possible solution (suggested by Ryan) is to use cronolog (http://cronolog.org/), which seems like a fine idea.

Comment 1
by Joseph Rothrock 2 years ago at 2007-10-17 09:13:24

Maybe consider rolling diags.log as well. -Feature enhancement.

Comment 2
by Kevin Dalley 13 months ago at 2009-03-04 15:32:18

When traffic.out gets filled up, error.log stops filing up, even though rotation is turned on. This is
counter-intuitive. Rotation does not control traffic.out, but a large traffic.out will stop error.log from being
written.

Issue Links

• breaks: TS-4134 Traffic Manager aborts on attempted privilege escalation when non-root.
• duplicates: TS-1420 traffic.out cannot currently be rotated nicely
• is related to: TS-3133 Logging NOTE filling up diags.log
• relates to: TS-4071 Unused mutex Diags::rotate_lock
• relates to: TS-4072 Diagnostic log rolling races
• relates to: TS-2655 about traffic server clients prohibited by ip-allow policy log