Eric Mortensen
2015-May-07 09:08 UTC
[Gluster-users] changing gluster client log level - no effect
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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150507/a086792b/attachment.html>
Eric Mortensen
2015-May-07 09:26 UTC
[Gluster-users] changing gluster client log level - no effect
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 > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150507/41e0b10d/attachment.html>