<div dir="ltr">Thanks for the suggestion,<div><br></div><div>I tried running: <span style="font-size:12.8000001907349px">gluster --log-level=WARNING volume info </span><div><span style="font-size:12.8000001907349px">but it did not modify the log level of cli.log. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">I read the comment to the patch 9383, did I interpret it correctly that it says cli.log logs at all levels regardless of any options? </span></div><div><span style="font-size:12.8000001907349px"> </span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 7, 2015 at 12:01 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/07/2015 03:25 PM, Kaushal M wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You have to provide the log-level option to the `gluster` command<br>
directly, as in `gluster --log-level=WARNING volume info`.<br>
<br>
I don't know how or why the log level of CLI defaults to TRACE. It<br>
used to be INFO earlier, but some it has changed to TRACE. I need to<br>
investigate this further.<br>
<br>
</blockquote>
<br></span>
We need a backport of [1] to release-3.6.<br>
<br>
-Vijay<br>
<br>
[1] <a href="http://review.gluster.org/9383" target="_blank">http://review.gluster.org/9383</a><br>
<br>
</blockquote></div><br></div>