Bug 1426557

Summary:	flooding of "dict is NULL" logging
Product:	[Community] GlusterFS	Reporter:	Daniel <fua82-redhat>
Component:	index	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.9	CC:	bugs, pkarampu, ravishankar
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 12:31:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel 2017-02-24 09:58:49 UTC

Description of problem:

Following log entries flood the log file:

[2017-02-24 09:48:44.529162] W [dict.c:1241:dict_foreach_match] (-->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(dict_foreach_match+0x65) [0x7f51f77236f5] -->/usr/lib/x86_64-linux-gnu/glusterfs/3.9.1/xlator/features/index.so(+0x3140) [0x7f51f0410140] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(dict_foreach_match+0xe1) [0x7f51f7723771] ) 0-dict: dict|match|action is NULL [Invalid argument]


Version-Release number of selected component (if applicable):
3.9.1


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I have read the previous reports to this bug. In checked for the lines mentioned in the following comment from Anuradha: https://bugzilla.redhat.com/show_bug.cgi?id=1313567#c6. The lines 

    option xattrop-pending-watchlist trusted.afr.VOLNAME-    <--------(1)
    option xattrop-dirty-watchlist trusted.afr.dirty      <--------(2)

are missing in my vol-Files.

Can/Should I add them manually to the vol files? Or is there another way to fix this?

Best regards
Daniel

Comment 1 Kaushal 2017-03-08 12:31:30 UTC

This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1].

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.

[1]: https://www.gluster.org/community/release-schedule/