+++ This bug was initially created as a clone of Bug #1222065 +++ Description of problem: When Gluster/NFS is disabled with the volume option nfs.disable=true, GlusterD fills its own logs with the following messages: [2015-05-15 16:25:34.826068] W [socket.c:642:__socket_rwv] 0-nfs: readv on /var/run/gluster/2feeb86ac1b9bb2039781dcb18de449b.socket failed (Invalid argument) [2015-05-15 16:25:37.826562] W [socket.c:3059:socket_connect] 0-nfs: Ignore failed connection attempt on /var/run/gluster/2feeb86ac1b9bb2039781dcb18de449b.socket, (No such file or directory) These lines are repeated every 3 seconds. Version-Release number of selected component (if applicable): 3.7.0 How reproducible: 100% Steps to Reproduce: 1. create and start a volume 2. gluster volume set $VOLUME nfs.disable true 3. tail -f /var/log/glusterfs/etc-glusterfs-glusterd.vol.log Actual results: Logs fill rapidly. Expected results: No log messages, this is intentional. Additional info: Reported by Manu: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10956 --- Additional comment from Anand Avati on 2015-06-02 00:24:04 EDT --- COMMIT: http://review.gluster.org/10963 committed in release-3.7 by Kaushal M (kaushal) ------ commit efdb183c62be68f1a371237d1caac4347288f538 Author: Krishnan Parthasarathi <kparthas> Date: Tue May 19 14:48:01 2015 +0530 glusterd: fix repeated connection to nfssvc failed msgs ... and disable reconnect timer on rpc_clnt_disconnect. Root Cause ---------- gluster-NFS service wouldn't be started if there are no started volumes that have nfs service enabled for them. Before this fix we would initiate a connect even when the gluster-NFS service wasn't (re)started. Compounding that glusterd_conn_disconnect doesn't disable reconnect timer. So, it is possible that the reconnect timer was in execution when the timer event was attempted to be removed. Change-Id: Iadcb5cff9eafefa95eaf3a1a9413eeb682d3aaac BUG: 1222065 Signed-off-by: Krishnan Parthasarathi <kparthas> Reviewed-on: http://review.gluster.org/10830 Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Gaurav Kumar Garg <ggarg> Reviewed-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/10963 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Emmanuel Dreyfus <manu>
Downstream patch link : https://code.engineering.redhat.com/gerrit/#/c/49655/
Tested with RHGS 3.1 Nightly build - glusterfs-3.7.1-6 Performed the following test : 1. Created a volume and started it 2. Disabled NFS on the volume No warning/error messages are seen in glusterd log file
Doc text verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html