Re: ldapsearch: erratic "Time limit exceeded" errors

[D.M.Lewney@sussex.ac.uk (Dave Lewney)]

Jean Jordaan wrote:
> Hi
>
> Most of the time, ldapsearch timeouts whenever I try a search. Sometimes
> it works. Here is a session show it working, and immediately thereafter
> not working:
>
> """
> blommie www.feko.info # /etc/init.d/slapd restart
>  * Stopping ldap-server...                          [ ok ]
>  * Starting ldap-server...                          [ ok ]
> blommie www.feko.info # ldapsearch -x  -b 
> "dc=upfrontsystems,dc=co,dc=za" '(sn=Courtois)'
> version: 2
>
> #
> # filter: (sn=Courtois)
> # requesting: ALL
> #
>
> # ContactPerson_315, Customer_160, creme, upfrontsystems, co, za
> dn: 
> oid=ContactPerson_315,oid=Customer_160,dc=creme,dc=upfrontsystems,dc=co,dc
>  =za
> givenName: Pierre Courtois
> [...]
>
> blommie www.feko.info # ldapsearch -x -l 0  -b 
> "dc=upfrontsystems,dc=co,dc=za" '(uid=ContactPerson_315)'
> version: 2
>
> #
> # filter: (uid=ContactPerson_315)
> # requesting: ALL
> #
>
> # search result
> search: 2
> result: 3 Time limit exceeded
>
> # numResponses: 1
> """
>
> I am specifying "-l 0" on the commandline, to lift any timelimit. I
> don't set a timelimit in slapd.conf either. What could be going wrong?
> Should I post the result with "-d'-1'"?

Hi,

At a guess you haven't built any indexes for (at least) sn and uid. See 
slapindex (8c).

Dave
--
Dave Lewney
Principal Systems Programmer, Computing Service
University of Sussex, Brighton BN1 9QJ. Tel: 01273 678354 Fax: 01273 271956