Bug 961197

Summary:	glusterd fails to read from the nfs socket every 3 seconds if all volumes are set nfs.disable
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.1	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:31 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 Joe Julian 2013-05-09 05:43:03 UTC

Description of problem:
I was seeing the following message every three seconds in the glusterd log:
[2013-05-08 22:33:08.195180] I [socket.c:1798:socket_event_handler] 0-transport: disconnecting now

When I attached to glusterd in gdb and broke at socket.c:1798 I printed *this. It turns out it was reporting that info on the same identifier every time, in this case: /tmp/4efb008e4e433ff7735a5a76111461d1.socket

After enabling nfs for one volume, the nfs service started and created that socket.

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


How reproducible:
Every time

Steps to Reproduce:
1. create a volume, myvol
2. gluster volume set myvol nfs.disable on
3. within a few seconds that info line should be logged.
  
Actual results:
glusterd keeps trying to communicate with the glusterfs nfs instance

Expected results:
glusterd should have closed the socket when it killed the service

Additional info:

Comment 1 Niels de Vos 2014-11-27 14:54:25 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.