Bug 1090782

Summary: nfs: some vague message in logs
Product: [Community] GlusterFS Reporter: santosh pradhan <spradhan>
Component: nfsAssignee: Niels de Vos <ndevos>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-bugs, saujain, shaines, vagarwal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1006772 Environment:
Last Closed: 2014-11-11 08:30:42 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: 1006772    
Bug Blocks:    

Comment 1 santosh pradhan 2014-04-24 07:24:40 UTC

Modify the log message saying that:

("Unable to get NLM port of the client."
 " Is the firewall running on client?"
 " OR Are RPC services running (rpcinfo -p)?");

Talked to Saurabh (QE wjho filed the BZ) before fixing the message. He okayed this.

Comment 2 Anand Avati 2014-04-24 07:35:04 UTC
REVIEW: http://review.gluster.org/7544 (gNFS: Log properly for pmap_getport() fail in NLM) posted (#1) for review on master by Santosh Pradhan (spradhan)

Comment 3 Anand Avati 2014-04-27 03:01:02 UTC
COMMIT: http://review.gluster.org/7544 committed in master by Vijay Bellur (vbellur) 
------
commit 3b40a553f466aa3d671efc2ae892215bebaa4c7b
Author: Santosh Kumar Pradhan <spradhan>
Date:   Thu Apr 24 12:55:05 2014 +0530

    gNFS: Log properly for pmap_getport() fail in NLM
    
    In NLM callback path, if pmap_getport() FAILs, it just log the error
    message saying "Is firewall running on the client". It may happen
    that RPC services are not running e.g. "rpcbind" is not running or
    nlockmgr (NLM) is not registered with portmapper which all can be
    checked using "rpcinfo -p" command.
    
    FIX:
    Modify the log message to include the later case mentioned
    above.
    
    Change-Id: If422275b2ab59d1e974a6caa37132f31e9a34329
    BUG: 1090782
    Signed-off-by: Santosh Kumar Pradhan <spradhan>
    Reviewed-on: http://review.gluster.org/7544
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 6 Niels de Vos 2014-09-22 12:38:42 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 7 Niels de Vos 2014-11-11 08:30:42 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users