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:
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.