[Bugs] [Bug 1199944] New: readv on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed when NFS is disabled

[bugzilla at redhat.com]

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

            Bug ID: 1199944
           Summary: readv on
                    /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket
                    failed when NFS is disabled
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: kparthas at redhat.com
          Reporter: kparthas at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    kparthas at redhat.com,
                    nico-redhat-bugzilla at schottelius.org,
                    uli.zumbuhl at gmx.ch
        Depends On: 1199936



+++ This bug was initially created as a clone of Bug #1199936 +++

Description of problem:
Every 3 seconds there is the following warning which gets logged:

[2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv
on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed (Invalid argument)

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

How reproducible:
Simply disable NFS on all your volumes


Steps to Reproduce:
1. disable NFS on your volumes using "gluster volume set volname nfs.disable
on"
2.
3.

Actual results:
[2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv
on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed (Invalid argument)

Expected results:
No warning in the log file

Additional info:
see http://www.gluster.org/pipermail/gluster-users/2015-March/020964.html

--- Additional comment from  on 2015-03-09 06:16:03 EDT ---

Having the same issue, it fills up the logfiles quickly & adds quite a lot
verbosity, which makes it hard to detect the "real" problems.

Just my 2 Rappen

--- Additional comment from krishnan parthasarathi on 2015-03-09 06:37:30 EDT
---

Root cause analysis
-------------------

glusterd would reconfigure node level services like gluster-nfs when volume
options are modified via volume-set or volume-reset commands. It is important
to know that glusterd maintains a unix domain socket connection with all the
daemon that it manages. 

When a user disables NFS access to a GlusterFS volume using "nfs.disable"
option, the gluster-nfs process is reconfigured/restarted. glusterd tries to
connect to the unix domain socket corresponding to gluster-nfs process. In this
case, it's likely that the user just disabled NFS access to the last volume in
the cluster. This implies gluster-nfs daemon wouldn't be running. At this point
gluster-nfs daemon's volfile wouldn't contain any volume in it and therefore it
shuts itself down. But glusterd has gone past the point where it could have and
avoided spawning it or connecting to it. This results in the log messages as
mentioned in bug synopsis. The log messages repeat because our rpc
implementation attempts a reconnect once in 3 seconds by default.

This problem may also be observed when a user restarts her glusterd possibly
after a software upgrade.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1199936
[Bug 1199936] readv on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket
failed when NFS is disabled
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=D3vhQCCQrp&a=cc_unsubscribe