diff options
authorSantosh Kumar Pradhan <>2014-04-24 12:55:05 +0530
committerVijay Bellur <>2014-04-26 20:00:55 -0700
commit3b40a553f466aa3d671efc2ae892215bebaa4c7b (patch)
parent6a188c6b2c95d16c1bb6391c9fcb8ef808c2141b (diff)
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 <> Reviewed-on: Reviewed-by: Niels de Vos <> Tested-by: Gluster Build System <> Reviewed-by: Rajesh Joseph <>
1 files changed, 4 insertions, 2 deletions
diff --git a/xlators/nfs/server/src/nlm4.c b/xlators/nfs/server/src/nlm4.c
index 042cfeba1..4d0083fe2 100644
--- a/xlators/nfs/server/src/nlm4.c
+++ b/xlators/nfs/server/src/nlm4.c
@@ -974,8 +974,10 @@ nlm4_establish_callback (void *csarg)
if (port == 0) {
- gf_log (GF_NLM, GF_LOG_ERROR, "Unable to get NLM port of the "
- "client. Is the firewall running on client?");
+ gf_log (GF_NLM, GF_LOG_ERROR,
+ "Unable to get NLM port of the client."
+ " Is the firewall running on client?"
+ " OR Are RPC services running (rpcinfo -p)?");
goto err;