Bug 1522591 - Modify glusterd log print level to Warning, glusterfsd and glustefs process log output level has not been modified.
Summary: Modify glusterd log print level to Warning, glusterfsd and glustefs process l...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-06 04:10 UTC by FengJunLiu
Modified: 2018-11-20 04:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-20 04:55:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description FengJunLiu 2017-12-06 04:10:31 UTC
Description of problem:
Modify glusterd log print level to Warning, glusterfsd and glustefs process log output level has not been modified.
glusterd.log print level becomes a Waring
but,cli.log, cmd_history.log, quotad.log output level remains the Info.

I want to know how to change the other processes of log output level, such as glusterfsd process and glusterfs process.

Thank you very much!

Comment 1 Amar Tumballi 2018-10-12 17:57:37 UTC
[root@localhost gfapi]# gluster volume set help | grep log-level
Option: diagnostics.brick-log-level
Description: Changes the log-level of the bricks
Option: diagnostics.client-log-level
Description: Changes the log-level of the clients
Option: diagnostics.brick-sys-log-level
Description: Gluster's syslog log-level
Option: diagnostics.client-sys-log-level
Description: Gluster's syslog log-level


Use `brick-log-level` option to set the log level. there is no loglevel setting to cli, but you can do `alias gluster=gluster --log-level=WARNING` to get CLI log fixed.

Comment 2 Vijay Bellur 2018-11-20 04:55:24 UTC
Closing as the requested information has been provided in comment 1.


Note You need to log in before you can comment on or make changes to this bug.