I saw a few "Running ..." log entries from the docker support code but
they seem to be all from VLOG(1) calls while for some reason the code
that does the actual "docker run" call uses LOG(INFO) and that does not
seem to come out by default, or I don't see it. But I'll try on ...

On 09/08/16 11:38, haosdent wrote:
> Hi, @Hendrik You could see INFO log when running Mesos Agent in
> default level. Some docker run logs may exist in the stdout/stderr of
> executor.
>
> On Tue, Aug 9, 2016 at 12:27 PM, Hendrik Haddorp
> <hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>> wrote:
>
>     I would like to see the "docker run" trace from
>     https://github.com/apache/mesos/blob/master/src/docker/docker.cpp
>     <https://github.com/apache/mesos/blob/master/src/docker/docker.cpp>
>     line 811.
>     What verbosity level does INFO map to?
>
>     On 09/08/16 05:06, Charles Allen wrote:
>     > Which glog are you trying to capture? You can set the verbosity
>     level
>     > with the environment variable GLOG_v
>     >
>     > And you can also set it through things like Spark. So if you want a
>     > lot of ZK chatter at the mesos level in your spark logs, add
>     >
>     > spark.executorEnv.GLOG_v=9
>     >
>     > to your spark context
>     >
>     > On Mon, Aug 8, 2016 at 2:53 PM Hendrik Haddorp
>     > <hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>
>     <mailto:hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>>>
>     wrote:
>     >
>     >     Hi,
>     >
>     >     the Mesos code contains log statements using LOG(INFO) and
>     >     VLOG(1), for
>     >     example. So far I found that Mesos is using the Google Logging
>     >     Library.
>     >     Looking in the logs I only seem to be able to find output
>     from VLOG
>     >     statements. What do I need to do to get the output from the LOG
>     >     statements? Where would I typically find the output? I'm
>     using CentOS
>     >     7.2 and found the output so far in the files below
>     /var/log/mesos.
>     >
>     >     thanks,
>     >     Hendrik
>     >
>
>
>
>
> -- 
> Best Regards,
> Haosdent Huang

Reply via email to