This has solved the issue for me also.
Ubuntu 16.04 with rpcbind 0.2.3-0.2- apt updated on March 21st 15:15 GMT.
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind
I'd like to confirm that on Ubuntu 16.04 the following allowed rpcbind to start
on fresh bootup:
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
Doing this forces rpcbind to start on boot and then nis starts
correctly:
# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from
/etc/systemd/system/multi-user.target.wants/rpcbind.service to
/lib/systemd/system/rpcbind.service
--
You received this bug notification
IMHO if the rpcbind service is enabled it should just start at boot time
and not have to be self activated.
Found this but no real good solution.
"Regression: rpcbind doesn't start at boottime on systemd controlled
machines."
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167
** Bug
** Changed in: nis (Ubuntu)
Status: New => Triaged
** Changed in: rpcbind (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title: