[Date Prev][Date Next]
Re: Critical extension and Internal (implementation specific) errors
Thanks Quanah. I'll test different number of threads, beginning with 8,
and post the result in this list.
About DB_CONFIG file, I didn't create... I'll rtfm and create one. :)
However, are there some parameters or values that can increase the
performance and maybe solve the problem?
On Sun, 2005-11-13 at 17:15 -0800, Quanah Gibson-Mount wrote:
> --On Sunday, November 13, 2005 8:01 PM -0200 Daniel Kobayashi Imori
> <email@example.com> wrote:
> > Hi,
> > I wrote a script that add and modify entries, using ldapadd and ldapmodify
> > commands.
> > There are many entries, up to 300, mix to add and modify in sequence.
> > The problem is that sometimes (not regular interval), some entries are not
> > added or modified, just one of the following messages appears:
> > ldap_bind: Critical extension is unavailable
> > ldap_add: Internal (implementation specific) error (80)
> > Is a performance problem?
> > I'm using openldap stable 20051018 and Berkeley DB 4.2.52 with patches 1,
> > 2, 3, and 4. Both packages compiled with no specific parameter, just
> > --prefix.
> > "threads 100" and "allow bind_v2" are the only general options included in
> > default configuration and there are many databases (BDB) with no different
> > options to default, just some access entries.
> I suggest re-evaluating your "threads" option. In general, increasing the
> number of threads is detrimental to the server. "threads 8" actually tends
> to run optimally on multiple operating systems and hardware I've tested.
> Also, did you set up a DB_CONFIG file?
> Quanah Gibson-Mount
> Principal Software Developer
> ITSS/Shared Services
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
Daniel Kobayashi Imori