Hello folks,
And thanks Ludovic : the problem was indeed related to an incomplete
index. The trick here was to add a "substring match" on all the field
that are used by sogo when querying the LDAP server.
Regards,
Didier.
Le 14/10/11 16:39, Ludovic Marcotte a écrit :
On 14/10/11 10:20, Didier Belhomme wrote:
I'm also experiencing slow LDAP query, but in my case it seems to be
related to a specific configuration of 389-DS (aka Fedora Directory
Server, aka RedHat Directory Server).
In our case, the test ldap server is running well (although it's a
small virtual machine) whereas ou production server (running on a much
more healthier system with 16 GB RAM) is a dog, taking sometimes 10
times more times to answer the same query :-/ (and yes, the data are
the same).
Did anyone experienced problems with the very latest version of 389-DS
(ie 389-ds-1.2.1-1.el5) on RedHat EL 5 (64bit) ? Any clue about this
will be very appreciated...
You have to make sure some attributes queried by SOGo are well indexed,
like:
givenName
cn
mail
sn
Your problem is only related to proper LDAP indexing.
Regards,
--
Didier Belhomme
FUNDP - SIU
Gestionnaire Systemes Unix/GNU/Linux
E-mail: [email protected]
Tel : +32 81 72 50 25
Fax : +32 81 72 50 23
--
[email protected]
https://inverse.ca/sogo/lists
