Learn how to resolve the Mount NFS Protocol Not Supported error in Kubernetes. Our NFS Support team is here to help you with your questions and concerns.
Mount NFS Protocol Not Supported Kubernetes | Fixes
Recently, one of our clients ran into trouble while experimenting with Kubernetes and NFS volume claims. Fortunately, our experts were able to set them back on track in no time.
Today, we are going to dive into a real-world scenario where deploying a Replication Controller ran into a ContainerCreating status as well as a mysterious error in the minion’s journal.
Join us as we explore the problem and walk through various solutions to get the Kubernetes setup back on track.
The Challenge
When we try to deploy the Replication Controller, the container enters a ContainerCreating status. Additionally, the journal of the minion displays this error related to NFS mounting:
Jan 12 14:27:32 node-01 kubelet[1529]: Output: mount.nfs: requested NFS version or transport protocol is not supported
Jan 12 14:27:32 node-01 kubelet[1529]: E0226 14:27:32.908756 1529 kubelet.go:1383] Unable to mount volumes for pod “node-manager-eemi2_default”: exit status 32; skipping pod
Jan 12 14:27:32 node-01 kubelet[1529]: E0226 14:27:32.923297 1529 pod_workers.go:112] Error syncing pod 0e66affa-dc79-11e5-89b3-080027f84891, skipping: exit status 32
Jan 12 14:27:32 node-01 kubelet[1529]: E0226 14:27:32.904931 1529 mount_linux.go:103] Mount failed: exit status 32
Solutions Explored
- NFS Server Service Status:
In one case, the nfs-server.service status was disabled. Activating the service resolved the problem.
- NFS Mount Version Configuration:
Another solution is to configure the NFS server. We have to add an entry in /etc/nfsmount.conf with Defaultvers=4. This will fix the NFS version issue. In other words, the Mount NFS Protocol Not Supported error will be fixed.
- Export Rule Misconfiguration:
Another customer faced this error due to an export misconfiguration. Our experts had to change the export rule to include specific IP addresses (e.g., /nfs 192.168.13.0/24). This restored connectivity and resolved the problem.
- Debugging with rpcdebug:
Interestingly, debugging the issue with rpcdebug didn’t yield results in one case. However, our experts dealt with this by capturing traffic on the NFS server and analyzing the dump. Here, the issue was due to NFS reply xid and Auth Bogus Credentials. Adjusting the export rule fixed the problem.
- Mounting with NFS Version 3:
Another solution is to mount with NFS version 3. We can use this command:
% mount -vvvv -t nfs -o vers=3 nfs-server:/share /mnt/nfs
Let us know in the comments if the above troubleshooting tips helped you out.
[Need assistance with a different issue? Our team is available 24/7.]
Conclusion
In brief, our Support Experts demonstrated how to resolve the Mount NFS Protocol Not Supported error in Kubernetes.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
0 Comments