[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Critical extension and Internal (implementation specific) errors

--On Sunday, November 13, 2005 8:01 PM -0200 Daniel Kobayashi Imori <daniel@bastion.com.br> wrote:


I wrote a script that add and modify entries, using ldapadd and ldapmodify

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

"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