Re: cli.log logging level

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>
To: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Monday, April 20, 2015 2:05:23 PM
Subject:  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@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux