You are not logged in.
Hello,
I have an issue since I've updated my system a couple of days ago.
NFS and autofs doesn't automount my nfs share.
[manager@univers ~]$ sudo systemctl start rpc-statd.service
Job for rpc-statd.service failed. See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
[manager@univers ~]$ sudo systemctl status rpc-statd.service
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since lun 2015-02-09 12:42:35 EST; 1min 45s ago
Process: 4407 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE)
fév 09 12:42:35 univers rpc.statd[4408]: Version 1.3.2 starting
fév 09 12:42:35 univers rpc.statd[4408]: Flags: TI-RPC
fév 09 12:42:35 univers rpc.statd[4408]: Running as root. chown /var/lib/nfs to choose different user
fév 09 12:42:35 univers rpc.statd[4408]: failed to create RPC listeners, exiting
fév 09 12:42:35 univers systemd[1]: rpc-statd.service: control process exited, code=exited status=1
fév 09 12:42:35 univers systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
fév 09 12:42:35 univers systemd[1]: Unit rpc-statd.service entered failed state.
fév 09 12:42:35 univers systemd[1]: rpc-statd.service failed.
[manager@univers ~]$
Any idea?
Thank you.
Pitou!
Last edited by Pitou (2015-02-10 17:37:20)
Offline
Would also like help with this, getting the same error as above.
Thanks
Sam
Offline
exact same problem here.
FWIW when i try to mount, I get:
```
~ ❯❯❯ sudo mount readynas:/c/shared-storage ~/nas-direct
[sudo] password for dieter:
Job for rpc-statd.service failed. See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
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
```
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Exactly the same problem here. I ended up reverting nfs-utils to 1.3.1-1 so I could continue connecting to nfsv3
Offline
@skunktrader,
Could you tell me how you proceeded to revert back to nfs-utils 1.3.1-1. I never did that before.
Any procedure, tutorial you can point me out?
Thank you very much.
Pitou!
Offline
@Pitou: Search the wiki
https://wiki.archlinux.org/index.php/Do … g_packages
Last edited by runical (2015-02-10 08:42:13)
Offline
Hi,
got the same problem this morning. Errors at boot and impossibility to load nfs-server.
I didn't need to downgrade nfs-utils, just to re-enable rpcbind and reboot. Don't know why it has been disabled !
Everything works fine now.
Offline
What you need is to start rpcbind, I have also stumbled upon this problem and I suppose the service files should include a dependency on rpcbind.
The wiki says to start rpcbind manually (and on every boot) but I suppose this might get fixed upstream eventually.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Thanks SubS0, re-enabling the rpcbind service and rebooting did solve the problem for me as well.
Pitou!
Offline
Thanks SubS0, re-enabling the rpcbind service and rebooting did solve the problem for me as well.
Pitou!
Worked here too. Specifically:
sudo systemctl enable rpcbind.socket
sudo systemctl restart rpcbind.service
sudo mount -a
Thanks
Offline
Just updated my system and encountered this problem too, so it's not been fixed yet.
Had to run:
systemctl enable rpcbind
systemctl start rpcbind
systemctl start nfs-server
Although, that middle step may not be necessary.
Offline
Fantastic! Do anyone know why this happens?
Offline
is it fixed for you guys? i encounter the same problem
Offline
@spychodelics,
Did you try the solutions mentioned in this thread? Since this is a solved thread, I would ask you to open a new one.
Offline
Yes, i tried the solutions but it didnt work. I moved to SMB for now since i needed that too. Thank you.
Offline