Large amount of users in Directory causes timeouts on client login.
>From: firstname.lastname@example.org [email@example.com] on behalf of Gerrard Geldenhuis [Gerrard.Geldenhuis@betfair.com]
>Sent: 21 July 2010 16:37
>To: General discussion list for the 389 Directory server project.
>Subject: Re: [389-users] Large amount of users in Directory causes timeouts on client login.
>>> Any thoughts or steering in the right direction would be appreciated.
>>> The documentation states a few default indexes that gets created and I would have thought that these would be adequate for effectively finding a user in a >>larger database.
>running logconv.pl has turned up empty handed no recommendations or problems. I can do a ldapsearch from the client which turns up all of the neccesary >information. nscd is not running so can't interfere. It looks like a client problem. I am digging further...
Problem turns out to be simple, the authenticator user that we used to bind to the directory runs into a adminLimitExceeded when looking at a tcpdump. I could also recreate the problem by doing the search from the command line. The solution I think will be to either implement some additional filtering when doing a search or increasing the search limit for this user. This same limit does not exist for the cn=Directory Manager user.
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.
389 users mailing list