pod调度到集群中某node节点失败
2019-01-12 本文已影响11人
进击云原生
![](https://img.haomeiwen.com/i9134763/634c6525535ea559.png)
![](https://img.haomeiwen.com/i9134763/b92a42441fae9bfa.png)
![](https://img.haomeiwen.com/i9134763/1a4875f2a3404301.png)
Fixing rpc.statd is not running but is required for remote locking
If you come across this error while attempting to mount an NFS filesystem it means that the statd process is not running.
mount -a -t nfs
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
Here’s how to fix the rpc.statd is not running error on el6
First, ensure that rpcbind is running and that it is set to start on boot
/etc/init.d/rpcbind start
Starting rpcbind: [ OK ]
chkconfig rpcbind on
Then, start the nfslock service
/etc/init.d/nfslock start
Starting NFS statd: [ OK ]
chkconfig nfslock on
That’s it. You should now be able to mount your nfs filesystem.
参考自:
https://backdrift.org/fixing-rpc-statd-running-required-remote-locking