It looks like, that there is a problem, when the ldap-client searches
with exponential backoff for the servers:
Following change seems to fix the problem, BUT a rational sounding has
to be changed?
In /etc/ldap.conf:
default Reconnect policy:
bind_policy hard
has to be changed to:
bind_policy soft
then:
In /etc/ldap.conf: -> host ldap01 ldap02 works as expected, and PC
without network-cable boots normal.
** Summary changed:
- hostname lookup broken in ldap.conf
+ bind_policy hard broken in ldap.conf
** Package changed: xorg (Ubuntu) => ldap-auth-client (Ubuntu)
** Summary changed:
- bind_policy hard broken in ldap.conf
+ bind_policy hard broken in ldap.conf in 17.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1732735
Title:
bind_policy hard broken in ldap.conf in 17.10
Status in ldap-auth-client package in Ubuntu:
New
Bug description:
A scripted installation of an ldap-client WORKING in ubuntu 16.04 is broken
in ubuntu 17.10.
In ldap.conf:
host ldap01 ldap02 (was working in 16.04)
has to be replaced with:
host 10.0.0.9 10.0.0.10
otherwise the system stays in an endless loop at boot up!
Change from hostname to ip has to be done with a rescue system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1732735/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
