[
https://issues.apache.org/jira/browse/MESOS-8512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366000#comment-16366000
]
Andrew Schwartzmeyer commented on MESOS-8512:
---------------------------------------------
Tests here: https://reviews.apache.org/r/65624/
Waiting on reviews.
> Fetcher doesn't log it's stdout/stderr properly to the log file
> ---------------------------------------------------------------
>
> Key: MESOS-8512
> URL: https://issues.apache.org/jira/browse/MESOS-8512
> Project: Mesos
> Issue Type: Bug
> Environment: Windows 10
> Reporter: Jeff Coffler
> Assignee: Andrew Schwartzmeyer
> Priority: Major
> Labels: fetcher, libprocess, stout, windows
>
> The fetcher doesn't log it's stdout or stderr to the task's output files as
> it does on Linux. This makes it extraordinarily difficult to diagnose fetcher
> failures (bad URI, or permissions problems, or whatever).
> It does not appear to be a glog issue. I added output to the fetcher via cout
> and cerr, and that output didn't show up in the log files either. So it
> appears to be a logging capture issue.
> Note that the container launcher, launched from
> src/slave/containerizer/mesos/launcher.cpp, does appear to log properly.
> However, when launching the fetcher itself from
> src/slave/containerizer/fetcher.cpp (FetcherProcess::run), logging does not
> happen properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
