thr3ads.net - Gluster users - [Gluster-users] cli.log logging level [Apr 2015]

If this information is useful, please help other people find it:
Share via:

Gabriele Paggi

2015-Apr-20 08:35 UTC

[Gluster-users] cli.log logging level

Hi,

I have a working distributed-replicated setup with two bricks.
On both nodes the cli.log file fills up with:

[2015-04-20 08:26:06.023184] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023209] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023219] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023229] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023238] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023249] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023260] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023271] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023283] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023293] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023302] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023312] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023321] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023331] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023340] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0

And its size averages 600-800MB a day.
I assume the D in the log line stands for DEBUG. Is it there a way to lower
logging level so that only WARN and higher get logged?

I already have these two options set for my volume:

Options Reconfigured:
diagnostics.brick-log-level: WARNING
diagnostics.client-log-level: WARNING

Thanks!

-- 
Gabriele
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150420/f7f3bce2/attachment.html>

Gaurav Garg

2015-Apr-20 08:42 UTC

head link

[Gluster-users] cli.log logging level

Hi Gabriele,

you can set cli log level by providing option while executing command. for eg
(volume status command).

#gluster --log-level=DEBUG/INFO/etc...  volume status.

hope it will work.

Thank you....

Regards
~Gaurav

----- Original Message -----
From: "Gabriele Paggi" <gabriele.paggi at gmail.com>
To: "gluster-users" <gluster-users at gluster.org>
Sent: Monday, April 20, 2015 2:05:23 PM
Subject: [Gluster-users] cli.log logging level

Hi, 

I have a working distributed-replicated setup with two bricks. 
On both nodes the cli.log file fills up with: 

[2015-04-20 08:26:06.023184] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023209] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023219] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023229] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023238] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023249] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023260] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023271] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023283] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023293] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023302] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023312] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023321] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023331] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0
[2015-04-20 08:26:06.023340] D [registry.c:408:cli_cmd_register] 0-cli:
Returning 0

And its size averages 600-800MB a day. 
I assume the D in the log line stands for DEBUG. Is it there a way to lower
logging level so that only WARN and higher get logged?

I already have these two options set for my volume: 

Options Reconfigured: 
diagnostics.brick-log-level: WARNING 
diagnostics.client-log-level: WARNING 

Thanks! 

-- 
Gabriele 

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Gluster users - Apr 2015 - cli.log logging level

[Gluster-users] cli.log logging level

[Gluster-users] cli.log logging level