Re: [ovirt-users] [Gluster-users] op-version for reset-brick (Was: Re: Upgrading HC from 4.0 to 4.1)

On Wed, Jul 5, 2017 at 6:39 PM, Atin Mukherjee <amukherj(a)redhat.com&gt; wrote: What's the best way to set glusterd in debug mode? Can I set this volume, and work on it even if it is now compromised? I ask because I have tried this: [root@ovirt01 ~]# gluster volume get export diagnostics.brick-log-level Option Value ------ ----- diagnostics.brick-log-level INFO [root@ovirt01 ~]# gluster volume set export diagnostics.brick-log-level DEBUG volume set: failed: Error, Validation Failed [root@ovirt01 ~]# While on another volume that is in good state, I can run [root@ovirt01 ~]# gluster volume set iso diagnostics.brick-log-level DEBUG volume set: success [root@ovirt01 ~]# [root@ovirt01 ~]# gluster volume get iso diagnostics.brick-log-level Option Value ------ ----- diagnostics.brick-log-level DEBUG [root@ovirt01 ~]# gluster volume set iso diagnostics.brick-log-level INFO volume set: success [root@ovirt01 ~]# [root@ovirt01 ~]# gluster volume get iso diagnostics.brick-log-level Option Value ------ ----- diagnostics.brick-log-level INFO [root@ovirt01 ~]# Do you mean to run the reset-brick command for another volume or for the same? Can I run it against this "now broken" volume? Or perhaps can I modify /usr/lib/systemd/system/glusterd.service and change in [service] section from Environment="LOG_LEVEL=INFO" to Environment="LOG_LEVEL=DEBUG" and then systemctl daemon-reload systemctl restart glusterd I think it would be better to keep gluster in debug mode the less time possible, as there are other volumes active right now, and I want to prevent fill the log files file system Best to put only some components in debug mode if possible as in the example commands above. Let me know, thanks