Tweaking LDAP parameters
Matthew Newton
mcn4 at leicester.ac.uk
Wed Apr 13 16:58:15 CEST 2016
On Wed, Apr 13, 2016 at 02:46:23PM +0000, A.L.M.Buxey at lboro.ac.uk wrote:
> you already have '0' for LDAP timeouts....so no connections
> should be killed off... the LDAP connection pool should be as
> many as our servers (number of threads) - but the other thing to
> look at is number of LDAP connections you are allowed....and how
The following from the original message looks weird to me
On Wed, Apr 13, 2016 at 10:12:27AM +0100, David Hartburn wrote:
> Tue Apr 12 15:14:48 2016 : Info: rlm_ldap (ldap): Deleting connection (40122)
> Tue Apr 12 15:14:48 2016 : Info: rlm_ldap (ldap): 2 of 2 connections in use.
> Need more spares
...
> pool {
> start = 16
> min = 8
> max = ${thread[pool].max_servers}
> spare = 16
Not sure why it's closing down the connections to get less than 8.
But probably more in the full logs. "radiusd -lfx stdout" might
help to get debug logs while threaded. Or radmin as mentioned
before.
Matthew
--
Matthew Newton, Ph.D. <mcn4 at le.ac.uk>
Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>
More information about the Freeradius-Users
mailing list