You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Daniel Xu (JIRA)" <ji...@apache.org> on 2016/09/28 21:39:20 UTC
[jira] [Comment Edited] (TS-4399) Management API breaks diagnostic
log rotation
[ https://issues.apache.org/jira/browse/TS-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530955#comment-15530955 ]
Daniel Xu edited comment on TS-4399 at 9/28/16 9:39 PM:
--------------------------------------------------------
[~jamespeach]: We can't remove {{-tsArgs}} and **only** use {{proxy.config.proxy_binary_opts}} because the Records subsystem (ie. {{REC_readString()}}) is initialized after we want to write output to diagnostic logs.
I agree this is a bug. I think it would be easy to do a quick and dirty fix, but I also think there's room for a better solution. We should think about it in conjunction with TS-4400. See my comment [over here|https://issues.apache.org/jira/browse/TS-4400?focusedCommentId=15530928&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15530928].
was (Author: danobi):
[~jamespeach]: We can't remove {{-tsArgs}} and **only** use {{proxy.config.proxy_binary_opts}} because the Records subsystem (ie. {{REC_readString()}} is initialized after we want to write output to diagnostic logs.
I agree this is a bug. I think it would be easy to do a quick and dirty fix, but I also think there's room for a better solution. We should think about it in conjunction with TS-4400. See my comment [over here|https://issues.apache.org/jira/browse/TS-4400?focusedCommentId=15530928&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15530928].
> Management API breaks diagnostic log rotation
> ---------------------------------------------
>
> Key: TS-4399
> URL: https://issues.apache.org/jira/browse/TS-4399
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging, Management API
> Reporter: James Peach
> Assignee: Daniel Xu
> Fix For: 7.1.0
>
>
> Start up Traffic Server:
> {code}
> 0 26950 1 0 10:13AM ?? 0:00.01 /opt/ats/bin/traffic_cop
> -2 26951 26950 0 10:13AM ?? 0:00.02 /opt/ats/bin/traffic_manager --bind_stdout /opt/ats/var/log/trafficserver/traffic.out --bind_stderr /opt/ats/var/log/trafficserver/traffic.out
> -2 26952 26951 0 10:13AM ?? 0:00.08 /opt/ats/bin/traffic_server -M --bind_stdout /opt/ats/var/log/trafficserver/traffic.out --bind_stderr /opt/ats/var/log/trafficserver/traffic.out --httpport 8080:fd=12
> {code}
> Now restart it using {{traffic_line -S}} followed by {{traffic_line -U}}:
> {code}
> 0 26950 1 0 10:13AM ?? 0:00.01 /opt/ats/bin/traffic_cop
> -2 26951 26950 0 10:13AM ?? 0:00.05 /opt/ats/bin/traffic_manager --bind_stdout /opt/ats/var/log/trafficserver/traffic.out --bind_stderr /opt/ats/var/log/trafficserver/traffic.out
> -2 26967 26951 0 10:13AM ?? 0:00.12 /opt/ats/bin/traffic_server -M --httpport 8080:fd=20
> {code}
> Note that we lost the {{\--bind_stdout}} and {{\--bind_stderr}} options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)