Bug 804159 - NLM: Complains of firewall running despite no firewall
Summary: NLM: Complains of firewall running despite no firewall
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Divya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-16 17:18 UTC by Sachidananda Urs
Modified: 2013-07-24 17:49 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:49:10 UTC
Regression: ---
Mount Type: ---
Documentation: DP
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Sachidananda Urs 2012-03-16 17:18:53 UTC
This is possibly due to NAT happening (Have to confirm this yet)...

In that case the log messages have to be more descriptive. Other applications work except for exclusive locks. Basic locking works, but the blocking calls fail.

[2012-03-16 01:53:07.087866] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success
[2012-03-16 01:53:07.088445] E [nlm4.c:891:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client?
[2012-03-16 01:53:37.083484] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success
[2012-03-16 01:53:37.084042] E [nlm4.c:891:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client?
[2012-03-16 01:54:07.077692] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success
[2012-03-16 01:54:07.078286] E [nlm4.c:891:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client?
[2012-03-16 01:54:37.073171] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success
[2012-03-16 01:54:37.073635] E [nlm4.c:891:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client?
[2012-03-16 01:55:07.067772] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success
[2012-03-16 01:55:07.068245] E [nlm4.c:891:nlm4_establish_callback] 0-nfs-NLM: Unable to get NLM port of the client. Is the firewall running on client?
[2012-03-16 01:55:37.105924] E [nlm4.c:493:nsm_monitor] 0-nfs-NLM: clnt_call(): RPC: Success

Comment 1 Krishna Srinivas 2012-03-19 05:38:22 UTC
Explained the problem to sac that the problem was happening because of the NAT router. Gluster NLM server was trying to do portmap query of NLM on the client and failing (gluster NLM server would think that the NAT router is the client - because of NAT'ing). For NLM to work properly there should not be NAT or firewall between the server and the client.

Comment 2 Sachidananda Urs 2012-04-04 07:20:20 UTC
We should be documenting this before closing the bug. I will update the bug and add a pointer to documentation if I can get a pointer.

Till then we can keep the bug as open.

Comment 3 Vijay Bellur 2012-04-27 12:12:46 UTC
Divya,

Can you please confirm if the documentation is complete?

Thanks

Comment 4 Divya 2012-05-04 10:05:55 UTC
I have added it as Known Issue in Release Notes. The updated Release Notes is available at: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2/html/2.0_Release_Notes/chap-2.0_Release_Notes-Test_Chapter.html

Comment 5 Sachidananda Urs 2012-05-21 05:37:42 UTC
Documentation verified.


Note You need to log in before you can comment on or make changes to this bug.