On Wed, Jul 13, 2016 at 11:02 PM, Atin Mukherjee <amukherj at redhat.com>
wrote:
>
>
> On Thu, Jul 14, 2016 at 8:02 AM, David Gossage <
> dgossage at carouselchecks.com> wrote:
>
>> M, David Gossage <dgossage at carouselchecks.com> wrote:
>>
>>> Is their a way to reduce logging of informational spam?
>>>
>>> /var/log/glusterfs/bricks/gluster1-BRICK1-1.log is now 3GB over
past few
>>> days
>>>
>>> [2016-07-14 00:54:35.267018] I [dict.c:473:dict_get]
>>> (-->/lib64/libglusterfs.so.0(default_getxattr_cbk+0xac)
[0x7fcdc396dcbc]
>>>
-->/usr/lib64/glusterfs/3.7.11/xlator/features/marker.so(marker_getxattr_cbk+0xa7)
>>> [0x7fcdafde5917] -->/lib64/libglusterfs.so.0(dict_get+0xac)
>>> [0x7fcdc395e0fc] ) 0-dict: !this || key=() [Invalid argument]
>>> [2016-07-14 00:54:35.272945] I [dict.c:473:dict_get]
>>> (-->/lib64/libglusterfs.so.0(default_getxattr_cbk+0xac)
[0x7fcdc396dcbc]
>>>
-->/usr/lib64/glusterfs/3.7.11/xlator/features/marker.so(marker_getxattr_cbk+0xa7)
>>> [0x7fcdafde5917] -->/lib64/libglusterfs.so.0(dict_get+0xac)
>>> [0x7fcdc395e0fc] ) 0-dict: !this || key=() [Invalid argument]
>>>
>>
>
> @Mani, Is this something which get logged in a normal scenario? I doubt.
>
>
I did find a bug report about it presumably being fixed in 3.8.
I also currently have a node down which may be triggering them.
>>>
>> Believe I found it
>>
>> gluster volume set testvol diagnostics.brick-log-level WARNING
>>
>>
>>
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Configuring_the_Log_Level.html
>>
>>
>> *David Gossage*
>>> *Carousel Checks Inc. | System Administrator*
>>> *Office* 708.613.2284
>>>
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
>>
>
>
>
> --
>
> --Atin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160714/9a436658/attachment.html>