You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
nis configuration broken on Debian 10 (nis >= nis_3.17.1-2) #709
On Debian 10 the ypbind doesn't support the -no-dbus option anymore so the service fails to start since this option is specified in the configuration file roles/nis/templates/etc/default/nis.j2
Removing the option from the YPBINDARGS line makes the client start correctly on the worker nodes.
On the master node no configuration is deployed hence /etc/yp.conf is left untouched. This defaults to the broadcast mode which seems to be broken too (unknown reason): "broadcast: RPC: Timed out"
Specifying the server in the yp.conf file on the server solves the issue and the service starts correctly also there so deploying this configuration also on the server should be considered.
Thank you for your comment that I followed and added a few more lines to make it successful on Ubuntu 20.04.
yp.conf on master does not need to be configured.
Here is my solution:
Fix IP address
Due to network manger, the ip get wrong configuration. Then, you can change by using the ansible_host variable from host config.
2.Remove ypbindargs as you said:
It can not load on the correct ypserv after these step, you could restart theses service by modifying on ypserv.yml
In the future, I will try to implement for ldap with more security.
Activity
nttg8100 commentedon Jan 22, 2023
Thank you for your comment that I followed and added a few more lines to make it successful on Ubuntu 20.04.
yp.conf on master does not need to be configured.
Here is my solution:
Due to network manger, the ip get wrong configuration. Then, you can change by using the ansible_host variable from host config.
2.Remove ypbindargs as you said:
In the future, I will try to implement for ldap with more security.