Kaushal M
2015-May-07 09:55 UTC
[Gluster-users] changing gluster client log level - no effect
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 at appstax.com> wrote:> Sorry, I am running 3.6.2 > > On Thu, May 7, 2015 at 11:08 AM, Eric Mortensen <eric at appstax.com> 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 at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users
Vijay Bellur
2015-May-07 10:01 UTC
[Gluster-users] changing gluster client log level - no effect
On 05/07/2015 03:25 PM, Kaushal M wrote:> 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. >We need a backport of [1] to release-3.6. -Vijay [1] http://review.gluster.org/9383