You have to provide the log-level option to the `gluster` command directly, as in `gluster --log-level=WARNING volume info`. I don't know how or why the log level of CLI defaults to TRACE. It used to be INFO earlier, but some it has changed to TRACE. I need to investigate this further. ~kaushal On Thu, May 7, 2015 at 2:56 PM, Eric Mortensen <eric@xxxxxxxxxxx> wrote: > Sorry, I am running 3.6.2 > > On Thu, May 7, 2015 at 11:08 AM, Eric Mortensen <eric@xxxxxxxxxxx> wrote: >> >> Hi >> >> Running 3.6.3 >> >> My cli.log fills up with debug and trace info. I have run these commands >> on the server: >> >> gluster volume set gsfiles diagnostics.brick-log-level WARNING >> gluster volume set gsfiles diagnostics.client-log-level WARNING >> >> I am running glusterd like this: >> >> /usr/sbin/glusterd --no-daemon --log-level WARNING >> >> None of these seem to have any effect, as cli.log is still flooded with >> debug and trace info. >> >> Do I need to do anything else? >> >> Thanks, >> Eric >> >> >> > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
