Bug 1222378

Summary:	GlusterD fills the logs when the NFS-server is disabled
Product:	[Community] GlusterFS	Reporter:	krishnan parthasarathi <kparthas>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	amukherj, bugs, kaushal, manu, ndevos, smohan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10956
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1222065	Environment:
Last Closed:	2016-06-16 13:03:00 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:
Bug Depends On:
Bug Blocks:	1222065

Description krishnan parthasarathi 2015-05-18 04:51:39 UTC

+++ 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

Comment 1 Anand Avati 2015-05-19 11:44:59 UTC

REVIEW: http://review.gluster.org/10830 (glusterd: fix repeated connection to nfssvc failed msgs) posted (#1) for review on master by Krishnan Parthasarathi (kparthas)

Comment 2 Anand Avati 2015-05-20 05:35:28 UTC

REVIEW: http://review.gluster.org/10830 (glusterd: fix repeated connection to nfssvc failed msgs) posted (#2) for review on master by Krishnan Parthasarathi (kparthas)

Comment 3 Anand Avati 2015-05-20 07:05:34 UTC

REVIEW: http://review.gluster.org/10830 (glusterd: fix repeated connection to nfssvc failed msgs) posted (#3) for review on master by Krishnan Parthasarathi (kparthas)

Comment 4 Anand Avati 2015-05-20 13:08:51 UTC

REVIEW: http://review.gluster.org/10830 (glusterd: fix repeated connection to nfssvc failed msgs) posted (#4) for review on master by Krishnan Parthasarathi (kparthas)

Comment 5 Anand Avati 2015-05-28 04:26:09 UTC

REVIEW: http://review.gluster.org/10830 (glusterd: fix repeated connection to nfssvc failed msgs) posted (#5) for review on master by Atin Mukherjee (amukherj)

Comment 6 Anand Avati 2015-05-28 08:58:50 UTC

COMMIT: http://review.gluster.org/10830 committed in master by Kaushal M (kaushal) 
------
commit 8461bf0b5008a3ddcc7b675caa9aa7c3d6473048
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: 1222378
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/10830
    Tested-by: NetBSD Build System
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Gaurav Kumar Garg <ggarg>
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: Kaushal M <kaushal>

Comment 9 Niels de Vos 2016-06-16 13:03:00 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user