> On 26 Apr 2017, at 19.33, rohan.henry cwjamaica.com
> <rohan.he...@cwjamaica.com> wrote:
> Log and config file attached.
> The user "autoconfig" is considered invalid when .52 the first ldap host
> becomes unreachable even though the other two ldap hosts in the lists were
> working and the user IS a valid user.
Does it work better if you disable HoldServerConnection?
Currently LDAP server failover when queries timeout and multiple hosts
have been defined per AuthBy LDAP2 requires some improvements.
A workaround would be to define new AuthBy LDAP2 stanza for each host.
Tuure Vartiainen <varti...@open.com.au>
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
radiator mailing list