Gluster users - Nov 2013 - Disabling NFS causes E level errors in nfs.log (bug 976750)

Hello,

according to the bug 976750 
(https://bugzilla.redhat.com/show_bug.cgi?id=976750) problem with 
repeating error messages:
[2013-11-13 17:16:11.888894] E [socket.c:2788:socket_connect] 
0-management: connection attempt failed (Connection refused)

in case when nfs is disabled on all volumes was suppose to be solved in 
3.4.1. We're using the version glusterfs-server-3.4.1-3.el6.x86_64 and 
we are still seeing this problem. Also according to release notes 
(https://github.com/gluster/glusterfs/blob/release-3.4/doc/release-notes/3.4.1.md)
seems that this issue is still present.

Will the fix be part of 3.4.2?

Thanks in advance
-- 
Emir Imamagic
SRCE - University of Zagreb University Computing Centre, www.srce.unizg.hr
Emir.Imamagic at srce.hr, tel: +385 1 616 5809, fax: +385 1 616 5559

On 11/13/2013 10:50 PM, Emir Imamagic wrote:
> Hello,
>
> according to the bug 976750
> (https://bugzilla.redhat.com/show_bug.cgi?id=976750) problem with
> repeating error messages:
> [2013-11-13 17:16:11.888894] E [socket.c:2788:socket_connect]
> 0-management: connection attempt failed (Connection refused)
Which log file contains this message? Is this the glusterd log?
>
> in case when nfs is disabled on all volumes was suppose to be solved in
> 3.4.1. We're using the version glusterfs-server-3.4.1-3.el6.x86_64 and
> we are still seeing this problem. Also according to release notes
>
(https://github.com/gluster/glusterfs/blob/release-3.4/doc/release-notes/3.4.1.md)
> seems that this issue is still present.
The fix for bug 976750 was to exit NFS process if nfs was disabled on 
all volumes. If the glusterd log file contains this message, then it 
seems like a different bug.

-Vijay