[
https://issues.apache.org/jira/browse/TS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242019#comment-15242019
]
ASF subversion and git services commented on TS-3857:
-----------------------------------------------------
Commit acb3343a568981cb4fa9c9052d01bfbb648a9980 in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=acb3343 ]
Merge pull request #567 from sudheerv/ts-3857
[TS-3857] Change ERROR default to not log into syslogs.
> Suppress a logging related error message to Note to avoid flooding.
> -------------------------------------------------------------------
>
> Key: TS-3857
> URL: https://issues.apache.org/jira/browse/TS-3857
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Reporter: Sudheer Vinukonda
> Assignee: Sudheer Vinukonda
> Labels: yahoo
> Fix For: 6.2.0
>
>
> After upgrading to 5.3.x from 5.0, one of our prod systems ran into an issue
> with disk space filling up due to the flooding of the below error message
> into syslogs.
> {code}
> {0x2aeac59d2700} ERROR: Failed to convert LogBuffer to ascii, have dropped
> (552) bytes
> {code}
> This is an unfortunate sideaffect of the fix made in TS-2940, prior to which,
> the defaults to error setting were not working correctly and ignoring the
> logging to syslog output.
> Also, should we change error defaults to "L" to ensure syslogs are not
> flooded with the fix from TS-2940? Below are the current defaults, which did
> not work correctly prior to TS-2940.
> {code}
> CONFIG proxy.config.diags.output.error STRING SL
> CONFIG proxy.config.diags.output.fatal STRING SL
> CONFIG proxy.config.diags.output.emergency STRING SL
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
