[
https://issues.apache.org/jira/browse/TS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123986#comment-15123986
]
Daniel Xu commented on TS-4159:
-------------------------------
There was a change made in TS-306 that redirects stdout and stderr to
traffic.out if TS is started by traffic_cop. traffic_cop adds the flags
"-bind_stdout /opt/ats/var/log/traffic.out -bind_stderr
/opt/ats/var/log/traffic.out" to the traffic_manager process, which then adds
the same flags to the traffic_server process, which finally redirects stdout
and stderr to traffic.out.
> ATS 6.1.0 does not log to stdout when not started from shell
> ------------------------------------------------------------
>
> Key: TS-4159
> URL: https://issues.apache.org/jira/browse/TS-4159
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Luca Bruno
> Labels: regression
> Fix For: 6.2.0
>
>
> I have a plugin that uses printf() to print some notice messages. Then my ATS
> is started by systemd with just `ExecStart=/usr/bin/traffic_manager`.
> With ATS 6.0.0 I could see the printf() from my plugin with journalctl.
> That's because the stdout of the service is connected to the journal.
> With ATS 6.1.0 the plugin output is not shown anymore with journalctl.
> However, starting `traffic_manager` from the shell actually shows the plugin
> output.
> No file under the log directory contains the plugin output.
> That makes me think there has been some change in 6.1.0 like: "if it's not a
> tty, close stdout", or something like that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
