Whenever I try to start an NFS mount I get:

Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23582]: Version 1.3.2 starting
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23582]: Flags: TI-RPC
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23582]: Running as root.  chown /var/lib/nfs to choose different user
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23582]: failed to create RPC listeners, exiting
Feb 12 00:02:19 martin-xps.lico.nl systemd[1]: rpc-statd.service: control process exited, code=exited status=1
Feb 12 00:02:19 martin-xps.lico.nl systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Feb 12 00:02:19 martin-xps.lico.nl systemd[1]: Unit rpc-statd.service entered failed state.
Feb 12 00:02:19 martin-xps.lico.nl systemd[1]: rpc-statd.service failed.
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23584]: Version 1.3.2 starting
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23584]: Flags: TI-RPC
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23584]: Running as root.  chown /var/lib/nfs to choose different user
Feb 12 00:02:19 martin-xps.lico.nl rpc.statd[23584]: failed to create RPC listeners, exiting

I tried to chown /var/lib/nfs to rpc, which just gives me the error minus the "Running as root" line:

Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23773]: Version 1.3.2 starting
Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23773]: Flags: TI-RPC
Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23773]: failed to create RPC listeners, exiting
Feb 12 00:05:09 martin-xps.lico.nl systemd[1]: rpc-statd.service: control process exited, code=exited status=1
Feb 12 00:05:09 martin-xps.lico.nl systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Feb 12 00:05:09 martin-xps.lico.nl systemd[1]: Unit rpc-statd.service entered failed state.
Feb 12 00:05:09 martin-xps.lico.nl systemd[1]: rpc-statd.service failed.
Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23775]: Version 1.3.2 starting
Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23775]: Flags: TI-RPC
Feb 12 00:05:09 martin-xps.lico.nl rpc.statd[23775]: failed to create RPC listeners, exiting

I have tried to reinstall nfs-utils:

$ pacman -R nfs-utils
$ rm -r /var/lib/nfs
$ pacman -S nfs-utils 

It then re-creates the directory with the permission of the root user. I'm not even sure if this error even related to rpc.statd not starting.

I also tried to run rpc.statd -F --no-notify in my shell, but that just exits with code 1. No error, no nothing. There's no verbose or debug flag documented in the manpage.

I also tried to empty my /etc/exports, and my system is up to date (pacman -Syu). I didn't change anything, it just stopped working a few hours ago.

Note that using mount -o nolock /data works; so the rest of the NFS/rpc daemons seem to be fine.

Same problem here, rpc-stad failed since the last update (all my computers had the problem after the update).

To solve the problem I just enabled and started rpcbind:

sudo  systemctl enable   rpcbind.service  # for the next reboot
sudo  systemctl start    rpcbind.service   
sudo  systemctl restart  rpcbind.service
up vote 6 down vote accepted

It would apear that the rpcbind systemd unit files went missing:

$ find /usr/lib/systemd -name 'rpcbind*'
# no output

Reinstalling this solved the issue:

$ pacman -S rpcbind
# [...]

$ find /usr/lib/systemd -name 'rpcbind*
/usr/lib/systemd/system/rpcbind.service
/usr/lib/systemd/system/rpcbind.target
/usr/lib/systemd/system/rpcbind.socket

$ systemd enable rpcbind
$ systemd start rpcbind
$ systemd restart nfs-server

Not sure how these files were missing ... Perhaps a FS corruption issue (?)

The strange thing is that nfsd was still running, but statd wasn't. After a reboot, nfsd also didn't work (because it needs rpcbind). It's almost like these files disappeared while the system was running.

And finally, I can't resist mentioning how the grand systemd doesn't give a clear error message on this (i.e. dependency rpcbind failed to load), and how much easier this would have been to debug with some other systems...

  • Weird. I just experienced exactly the same problem (couldn't mount an NFS3 volume, systemctl start rpc-statd failed with "failed to create RPC listeners, exiting" message.) on an Arch linux system. Installing, enabling, and starting the rpcbind service solved the problem. I wonder if this was previously working as a socket rather than service, but something went wrong somewhere. I unfortunately failed to check a priori if there were any rpcbind.* files in /usr/lib/systemd directory. – pgoetz Apr 27 '16 at 17:36

I've come across some instances where /var/lib/nfs or /var/lib/nfs/statd has been missing, which causes certain NFS daemons to exit with an error code but without printing any message. The fix is simple, just this:

$ sudo mkdir -p /var/lib/nfs/statd

But it's a bit odd that the daemons and systemd service files don't attempt to create the directories or print any error messages about it.

Similarly, I was seeing these errors:

Starting NFS status monitor for NFSv2/3 locking....
Version 1.3.3 starting
Flags: TI-RPC
Failed to access local netconfig database: Netconfig database not found
failed to create RPC listeners, exiting
rpc-statd.service: Control process exited, code=exited status=1
rpc-statd.service: Failed with result 'exit-code'.
Failed to start NFS status monitor for NFSv2/3 locking..

In my case, I'd broken permissions on /etc/netconfig which needs to be world readable (as does /etc/)

Setting the file perms to:

chmod 644 /etc/netconfig

fixed my issue.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.