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
We are on the right track, I have tried so many things I need to reload
the system to reset the default config for everything. Our 14.04 systems
run rpc.statd but not all the other nfs stuff. So maybe enabling that
service will be a work around, that is it will cause rpcbind to start.
I will need
I re-installed the lasted 16.04 beta. Be default the rpc-statd service
is not enabled, I enabled and rebooted, same problem rpcbind does not
start and neither does the nis service. If I manualy start with
systemctl start rpc-statd then rpcbind and rpcbind.statd start. If I
systemctl start nis it
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
Public bug reported:
did apt-get update/upgrade March 16, 2016
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
rpcbind does not start on boot, tried various systemd debugging steps
with no clues. After boot systemctl start rpcbind works. There is a
Meant to type "ypbind", so I installed nfs-kernel-server and now rpcbind
and ypbind start. Hate to install nfs-kernel-server on all our desktops
and servers that do not need it but they do need ypbind. Thanks for your
help.
--
You received this bug notification because you are a member of Ubuntu
We use nis ybind which is started out of /etc/init.d/nis which fails
because rpcbind is not running.
--
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:
rpcbind does not
rpcbind.socket is active, nis fails to start because it cannot contact
the rpcbind server so I guess it is not using the socket to communicate.
Reading the ypbind and ypbind.conf man pages does not have any info or
options on registering with rpcbind.
root@tophat:~# systemctl status
This may help if you have this issue with ypbind trying to start and the
network not up yet:
Use IP addreses in /etc/yp.conf
for example:
domain your_nis_domain server 10.10.123.123
If the network is not up, ypbind starts and cannot reslove the hostname in
yp.conf and dies.
If you supply an
The problem is with NetworkManager. If the system boots with ifup and DHCP
ypbind starts fine.
That is uncomment the iface etho line in /etc/network/interfaces and make sure
the following entry is in /etc/NetworkManager/NetworkManager.conf so that
NetworkManager does not control the interface:
I confirmed this bug on 4 systems. Here is the output from
/var/log/upstart/ypbind.log:
Setting NIS domainname to: sunrize
No NIS server and no -broadcast option specified.
Add a NIS server to the /etc/yp.conf configuration file,
or start ypbind with the -broadcast option.
Binding to YP server
Public bug reported:
root@tophat:/tmp# lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
root@tophat:/var/tmp# apt-cache policy nis
nis:
Installed: 3.17-32ubuntu4
Candidate: 3.17-32ubuntu4
Version table:
*** 3.17-32ubuntu4 0
500
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/993259
Title:
ypbind does not start on boot
To manage notifications about this bug go to:
13 matches
Mail list logo
