Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ERRO] [node4] [Driver] [grpc] rpc error: code = Internal desc = mount failed: exit status 32 #16

Closed
gofman8 opened this issue Jan 5, 2020 · 4 comments

Comments

@gofman8
Copy link

gofman8 commented Jan 5, 2020

hi! I am trying to mount pv to pod with help of NFS dynamic provisioning and met problem during mounting process.
Error:
Jan 5 21:13:43.214 [ERRO] [node4] [Driver] [NodePublishVolume()] Failed to mount volume 10.174.65.38:/nfs/pvc-c26498bd-c3c5-4a5a-b946-57b4c1179f55. Error: mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs -o vers=3,tcp 10.x.x.x:/nfs/pvc-c26498bd-c3c5-4a5a-b946-57b4c1179f55 /var/lib/kubelet/pods/ab2eb907-94a5-4dc3-b55c-ebb9bd109d56/volumes/kubernetes.io~csi/pvc-c26498bd-c3c5-4a5a-b946-57b4c1179f55/mount
Output: 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
OS: Centos 7
rpcbind and nfs-utils packages installed.
rpcbind service started

@gofman8
Copy link
Author

gofman8 commented Jan 5, 2020

Thanks. I have found root problem. For Centos 7 this services must be running:
systemctl start nfslock
systemctl start rpc-statd.service

@gofman8 gofman8 closed this as completed Jan 5, 2020
@Aerius42
Copy link

Hi ! I'm trying to do the same but I have this message in the driver:

Error:
Mar 21 02:38:40.992�[31m [ERRO] [node1] [Driver] [NodePublishVolume()] �[0mFailed to mount volume 10.96.138.144:/nfs-csi-tenant/pvc-66bc0aa7-a2df-41f2-9116-f04c5da73500. Error: mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs -o vers=3,tcp 10.x.x.x:/nfs-csi-tenant/pvc-66bc0aa7-a2df-41f2-9116-f04c5da73500 /var/lib/kubelet/pods/83ba7150-6682-4b40-b379-66c0bce5ff47/volumes/kubernetes.io~csi/pvc-66bc0aa7-a2df-41f2-9116-f04c5da73500/mount
Output: mount.nfs: Operation timed out

Mar 21 02:38:40.992�[31m [ERRO] [node1] [Driver] [grpc] �[0mrpc error: code = Internal desc = mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs -o vers=3,tcp 10.x.x.x:/nfs-csi-tenant/pvc-66bc0aa7-a2df-41f2-9116-f04c5da73500 /var/lib/kubelet/pods/83ba7150-6682-4b40-b379-66c0bce5ff47/volumes/kubernetes.io~csi/pvc-66bc0aa7-a2df-41f2-9116-f04c5da73500/mount
Output: mount.nfs: Operation timed out

OS: RHEL7

rpcbind and nfs-utils packages installed.
rpcbind service started

I tried your solution with:
systemctl start nfslock
systemctl start rpc-statd.service
But nothing new happened.

@dyusupov
Copy link
Contributor

firewall is on?

@Aerius42
Copy link

Aerius42 commented Mar 27, 2020

Thank you for your answer, it was indeed a networking problem but not the firewall.
Actually, I had to modify the edgefs-nfs-csi-node in edgefs-nfs-csi-driver.yaml to use the k8s network and see the internal services. I set:
hostNetwork: false

Then, I had the same issue as @SkySonR but the rpcbind was already up on the host but not in the container. So, I add this to its driver:
lifecycle:
postStart:
exec:
command: ["/sbin/rpcbind"]

I don't know why rpcbind didn't start at boot inside the container but that's do the thing. =D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants