Workaround:
 systemctl enable rpcbind.socket
 systemctl restart rpcbind.service
 mount -a

From: https://bbs.archlinux.org/viewtopic.php?pid=1506300#p1506300

(In reply to James Patterson from comment #1)
> Workaround:
>  systemctl enable rpcbind.socket
>  systemctl restart rpcbind.service
>  mount -a
> 
> From: https://bbs.archlinux.org/viewtopic.php?pid=1506300#p1506300

Hmm... in the rpcbind spec file there is the following trigger

%triggerun -- rpcbind > 0.2.2-2.0
/bin/systemctl enable rpcbind.socket

and when the package is initial installed the following happens:
%post
if [ $1 -eq 1 ] ; then
    # Initial installation
    /bin/systemctl enable rpcbind.socket
fi

I wonder why that workaround is needed...

I get the same error message when trying an NFS mount from the command line. System: clean install F22 KDE spin from Live DVD, then updated.

nfs-util version 1.3.2-7.fc22

I tried the rpcbind workaround above and got an intersting looking message, but no joy (not right away, I'll try a restart).

Commands and output:

[jensting@new-host-9 ~]$ sudo systemctl enable rpcbind.socket
Created symlink from /etc/systemd/system/sockets.target.wants/rpcbind.socket to /usr/lib/systemd/system/rpcbind.socket.
[jensting@new-host-9 ~]$ sudo  systemctl restart rpcbind.service
[jensting@new-host-9 ~]$ sudo mount 192.168.1.101:/mnt/BigRz1/BigRz1D/Users/Jens/NFS /mnt/NFS
Job for rpc-statd.service failed. See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
[jensting@new-host-9 ~]$ 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 Fri 2015-05-29 19:59:40 CEST; 10s ago
  Process: 2797 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE)

May 29 19:59:40 new-host-9.home systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
May 29 19:59:40 new-host-9.home systemd[1]: rpc-statd.service: control process exited, code=exited status=1
May 29 19:59:40 new-host-9.home systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
May 29 19:59:40 new-host-9.home systemd[1]: Unit rpc-statd.service entered failed state.
May 29 19:59:40 new-host-9.home systemd[1]: rpc-statd.service failed.
[jensting@new-host-9 ~]$

OK, on a reboot I now get an NFS mount and no error message.

The status is now :

[jensting@new-host-9 ~]$ 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: active (running) since Fri 2015-05-29 20:06:09 CEST; 45s ago
  Process: 2493 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=0/SUCCESS)
 Main PID: 2494 (rpc.statd)
   CGroup: /system.slice/rpc-statd.service
           └─2494 /usr/sbin/rpc.statd --no-notify

May 29 20:06:09 new-host-9.home systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
May 29 20:06:09 new-host-9.home rpc.statd[2494]: Version 1.3.2 starting
May 29 20:06:09 new-host-9.home rpc.statd[2494]: Flags: TI-RPC
May 29 20:06:09 new-host-9.home systemd[1]: Started NFS status monitor for NFSv2/3 locking..

We got hit by this bug as well: The autofs service has errors as described above and we can't mount any of our NFSv3 servers.  The workaround solved our problems:
systemctl enable rpcbind.socket
systemctl restart rpcbind.service
I hope this bug gets fixed ASAP.

(In reply to Ole Holm Nielsen from comment #5)
> We got hit by this bug as well: The autofs service has errors as described
> above and we can't mount any of our NFSv3 servers.  The workaround solved
> our problems:
> systemctl enable rpcbind.socket
> systemctl restart rpcbind.service
> I hope this bug gets fixed ASAP.

Did you do an upgrade to f22 or a clean install?

That's a clean install of FC22.

(In reply to Ole Holm Nielsen from comment #7)
> That's a clean install of FC22.

Ok... then I wonder why this %post script didn't work
%post
if [ $1 -eq 1 ] ; then
    # Initial installation
    /bin/systemctl enable rpcbind.socket
fi

At least the bug seems to be reproducible by several sites.  It seems inevitable that $1 is not equal to 1 (whatever that means).

*** Bug 1201876 has been marked as a duplicate of this bug. ***

rpcbind-0.2.3-0.1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/rpcbind-0.2.3-0.1.fc22

Package rpcbind-0.2.3-0.1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rpcbind-0.2.3-0.1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-9764/rpcbind-0.2.3-0.1.fc22
then log in and leave karma (feedback).

rpcbind-0.2.3-0.1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

This problem exists in Fedora 21 as well.  I just finished a clean install including nfs-utils and couldn't get NFS mounts to work until I did

$ systemctl enable rpcbind.socket
$ systemctl start rpcbind.socket

Cheers!  -Tyson

Hi all,

Just to bring some further attention to this. Updating some CentOS 7 systems today I came across the same problem. Same fix applies. For some reason the rpcbind.socket service is disabled and stopped after install...

Further info:

CentOS 7.1.1503

Updated to 

CentOS 7.2.1511.

Cheers,

Morgan