[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: slapadd and attribute value length limit
Howard Chu wrote:
Judging from the error message you
received, since the BDB library ran out of memory you may be able to
resolve this by increasing your BDB cache size. Also you may get some
more explicit information from BDB if you enable debugging (-d1) while
running slapadd.
I tried this. Cache size wasn't the problem. The gotcha:
bdb(o=mentata.com): Lock table is out of available locks
So now with DB_CONFIG:
set_lg_dir /var/log/openldap
set_lg_max 104857600
set_lg_bsize 26214400
set_lk_max_locks 2000
set_lk_max_lockers 2000
set_lk_max_objects 2000
# set_cachesize 0 20971520 1
set_cachesize 0 419430400 1
set_flags DB_TXN_NOSYNC
Now the load completes fine in under an hour. Much better than loading
just the english with slapadd and then using ldapmodify LDIFs for each
additional language (hours plural).
I know Quanah might add that I should now recomment:
#set_flags DB_TXN_NOSYNC
Already done, along with the cache switch. Would I need this many
locks/lockers in a runtime scenario, or should I comment out those as well?
Jon Roberts
www.mentata.com
Using RH 9, OL 2.2.5, BDB 4.2.52. I am updating my gospel example, but
when I run:
# slapadd -l gospel.ldif
I get
slapadd: could not add entry
dn="gospid=GVMattC14V15,ou=Gospel,ou=Expressions,o=mentata.com"
(line=9405): txn_aborted! Cannot allocate memory (12)
and DB_CONFIG is
set_lg_dir /var/log/openldap
set_lg_max 104857600
set_lg_bsize 26214400
set_cachesize 0 10485760 1
As you can see, it loads a number of verses fine. It seems to get
stuck on the longer ones. What do I need to change (besides OS and OL
version :) ) to get this data loaded and indexed?