NFS mount fails with message "rpc.statd is not running"
This document (7009756) is provided subject to the disclaimer at the end of this document.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Nov 7 19:00:59 [servername] rpcbind: cannot get local address for udp: Servname not supported for ai_socktype
Nov 7 19:00:59 [servername] rpcbind: cannot get local address for tcp: Servname not supported for ai_socktype
Nov 7 19:00:59 [servername] rpcbind: cannot get local address for udp6: Servname not supported for ai_socktype
Nov 7 19:00:59 [servername] rpcbind: cannot get local address for tcp6: Servname not supported for ai_socktype
sunrpc 111/tcp rpcbind # SUN Remote Procedure Call
sunrpc 111/udp rpcbind # SUN Remote Procedure Call
After making changes to /etc/services, restart rpcbind in client with command "rcrpcbind restart" and test your mount again.
The file /etc/services had been incorrectly modified and the word "rpcbind" was missing from "sunrpc" lines.
To verify rpc.statd is registered on the nfs client, issue command "rpcinfo -p". The service name "status"corresponds to the rcp.statd process so a couple of "status"lines should be listed:
[sles]:~ # rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 56130 status
100024 1 tcp 52733 status
100021 1 udp 47174 nlockmgr
100021 3 udp 47174 nlockmgr
100021 4 udp 47174 nlockmgr
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7009756
- Creation Date: 16-Nov-2011
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com