Bug 209752

Summary:	net/glusterfs: readv on /var/run/gluster/<something>.socket failed (Attribute not found)
Product:	Ports & Packages	Reporter:	Niklaas Baudet von Gersdorff <me>
Component:	Individual Port(s)	Assignee:	freebsd-ports-bugs (Nobody) <ports-bugs>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	craig001, w.schwarzenfeld
Priority:	---	Keywords:	needs-qa
Version:	Latest	Flags:	craig001: maintainer-feedback+
Hardware:	Any
OS:	Any
URL:	https://bugzilla.redhat.com/show_bug.cgi?id=1199936

Description Niklaas Baudet von Gersdorff 2016-05-25 16:07:32 UTC

Hello,

on a vanilla install of net/glusterfs I get an error as written in the summary every three seconds in the log file. It looks exactly like what was mentioned in a bug report upstream:

https://bugzilla.redhat.com/show_bug.cgi?id=1199936

The only difference is that I haven't changed anything in regard of NFS.

So, I'm wondering whether the fix on upstream made it into the port?

Best,

Niklaas

Comment 1 Niklaas Baudet von Gersdorff 2016-05-27 22:03:25 UTC

I just realised, if I set

gluster volume set vol1 nfs.disable off

and subsequently

gluster volume set vol1 nfs.disable on

the log messages cease.

Comment 2 craig001 2016-06-02 20:22:16 UTC

Thanks for bringing this to my attention, I'll try and replicate it and push upstream in the comming week.  I am also planning on updating the port to the latest glusterfs version.

Comment 3 Niklaas Baudet von Gersdorff 2016-06-03 08:32:51 UTC

Thanks for following up on this. FWIW, I am no longer sure how that is related to the bug I linked to from upstream. There, the bug will occur if one disables NFS; in this case though, it will occur if one *enables* NFS.

Comment 4 Walter Schwarzenfeld 2018-01-13 20:11:58 UTC

Glusterfs has now version 3.11.1. I think this overcome by events and could be closed.

Comment 5 Walter Schwarzenfeld 2018-03-03 11:51:26 UTC

Should fixed with 3.6.3
http://lists.gluster.org/pipermail//gluster-users/2015-April/021669.html

I close here, cause of no feedback. Should there still problems with newer versions, please open a new PR.