Bug 720814
| Summary: | Mounting multiple NFSv4 exports from same server results in can't create tcp rpc_clnt to server on NFSv4 server | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Anthony Messina <amessina> | ||||||
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | bfields, jlayton, steved | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-07 18:39:43 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Anthony Messina
2011-07-12 20:31:25 UTC
"WARNING: can't create tcp rpc_clnt to server linux-ws2.messinet.com for user with uid 0: RPC: Remote system error - Permission denied" A network trace might be helpful, as would any errors logged on the client around the same time. However, this isn't a fatal error, as you've noticed. It means the server is failing to establish a callback path to the client, so that delegations will be turned off. (In reply to comment #1) > "WARNING: can't create tcp rpc_clnt to server linux-ws2.messinet.com for user > with uid 0: RPC: Remote system error - Permission denied" > > A network trace might be helpful, as would any errors logged on the client > around the same time. On the clients, I experience zero errors at mount time. Ok, I'll try to do a trace. Any recommendations on how to do so? I haven't had to trace NFSv4 traffic before. > However, this isn't a fatal error, as you've noticed. It means the server is > failing to establish a callback path to the client, so that delegations will be > turned off. That's what I though. It seems with NFSv4, I would only mount the root of the export, then somehow bind mount or symlink the /home and /mnt/koji directories, but after Googling and attempting, neither of these options seems to work. Ok, I tried this: tcpdump -s1536 -w /tmp/dump tcp and host linux-ws2.messinet.com and not port 10050 and not port 80 and not port 25 I will attach the dump. Created attachment 512526 [details]
tcpdump on NFSv4 server
I also tried setting options nfs callback_tcpport=801 for nfs, opening up port 801 on the client and ensuring that the server is allowed via tcp_wrappers, but I still get the following on the server when the client mounts the second and third exports: rpc.gssd[20615]: DEBUG: port already set to 57973 (In reply to comment #3) > Ok, I tried this: > tcpdump -s1536 -w /tmp/dump tcp and host linux-ws2.messinet.com and not port > 10050 and not port 80 and not port 25 > > I will attach the dump. tcpdump does not have NFSv4 support. Please use wireshark. yum install wireshark tshark -w /tmp/data.pcap host linux-ws2.messinet.com and not port 10050 and not port 80 and not port 25 bzip2 /tmp/data.pcap Created attachment 515370 [details] Wireshark capture as requested during the client boot This capture was taken AFTER the upgrade to https://admin.fedoraproject.org/updates/nfs-utils-1.2.4-1.fc15 This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |