Red Hat Bugzilla – Bug 977497
gluster spamming with E [socket.c:2788:socket_connect] 0-management: connection attempt failed (Connection refused) when nfs daemon is off
Last modified: 2015-12-01 11:45:32 EST
Description of problem:
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log is being spammed with
E [socket.c:2788:socket_connect] 0-management: connection attempt failed (Connection refused) when nfs daemon is off.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.turn off nfs for this volume
tons of E [socket.c:2788:socket_connect] 0-management: connection attempt failed (Connection refused)
no spam in logs
*** This bug has been marked as a duplicate of bug 976750 ***
Setting release version to 3.4.1 and priority to high as gluster's nfs daemon has quite high memory impact yet if you turn it off it spams logs too much.
REVIEW: http://review.gluster.org/6293 (mgmt/glusterd: Spawn nfs only if it is enabled on at least one volume) posted (#2) for review on master by Vijay Bellur (firstname.lastname@example.org)
This seems to have been fixed in master and release-3.5, at least I can not reproduce this with those versions.
Lukas, do you need this in a 3.4 based version, or are you happy to have it in a 3.5 one?
I need it in release-3.4
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.
This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "email@example.com".
If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life.
If this bug still exists in a later release please reopen this and change the version or open a new bug.