there is a error with starting nfs-server
top of page
RUGGEDBOARD
FORUM
Solutions to your doubts are just one click away. Just select the appropriate category and ask questions. You can also reply to the answers you are already aware.
NFS error here,
NFS error here,
4 comments
Like
4 Comments
bottom of page
Open doors of opportunities by visiting the platform of careerbooster. You will also the best writing services there, that too all for free. Highly recommended to everybody out there!
install "nfs-kernel-server nfs-common" packages and try and please share your script file vidmate w3toys/instagram
The post discusses most commonly occurring NFS issues in Linux and how to resolve them.
1. Error: “Server Not Responding”
The Network File System (NFS) client and server communicate using Remote Procedure Call (RPC) messages over the network. Both the host->client and client->host communication paths must be functional. Use common tools such as ping, traceroute or tracepath to verify that the client and server machines can reach each other. If not, examine the network interface card (NIC) settings using either ifconfig or ethtool to verify the IP settings.
The NFS file system also reports “server not responding” when a heavy server or network loads cause the RPC message responses to time out. Use the “timeo=N” mount option on the client to increase the timeout. Check “man mount” for more information.
2. Error: “No route to host”
The “no route to host” error can be reported when the client attempts to mount an NFS file system, even if the client can successfully ping the server:
# mount NFS-Server:/data /data_remote
mount: mount to NFS server 'NFS-Server' failed: System Error: No route to host.
This can be caused by the RPC messages being filtered by either the host firewall, the client firewall, or a network switch. Verify if a firewall is active and if NFS traffic is allowed. Normally nfs is using port 2049. As a quick test one can switch the firewall off by:
3. Error: “mount clntudp_create: RPC: Port mapper failure – RPC: Unable to receive”
The Linux NFS implementation requires that both the NFS service and the portmapper (RPC) service be running on both the client and the server. Check it like this:
4. Error: “NFS Stale File Handle”
A program uses the open(2) system call to access an NFS file in the same way the application opens a local file. This system call returns a file descriptor, or “handle”, that the program subsequently uses in I/O commands to identify the file to be manipulated.
5. Error: “Access Denied” or “Permission Denied”
Check the export permissions for the NFS file system. You can do this from the client:
# showmount -e server_name
or from server:
# exportfs -a
If you see unexpected export permissions, check the /etc/exports file on the server. Make sure there is no syntax error such as space between the permitted host and the permissions.
Hope this helps
Please install "nfs-kernel-server nfs-common" packages and try and please share your script file once.