Re: RE24 testing call (OpenLDAP 2.4.34)

[Bill MacAllister <whm@stanford.edu>]

--On February 22, 2013 4:01:00 AM -0800 Howard Chu <hyc@symas.com> wrote:

>> slapadd -q /etc/ldap/slapd.d -b dc=stanford,dc=edu -l ./db-ldif.0
>> "#########             46.37% eta 07m12s elapsed          06m13s spd
>> 1.9 M/s 51272d39 => mdb_idl_insert_keys: c_put id failed: MDB_TXN_FULL:
>> Transaction has too many dirty pages - transaction too big (-30788)
>> 51272d39 => mdb_tool_entry_put: index_entry_add failed: err=80
>> 51272d39 => mdb_tool_entry_put: txn_aborted! Internal error (80)
>> slapadd: could not add entry
>> dn="suRegID=a9a6183ae77011d183712436000baa77,cn=people,dc=stanford,dc=ed
>> u" (line=17741844): txn_aborted! Internal error (80) *#########
>> 46.43% eta 07m11s elapsed          06m13s spd   1.9 M/s Closing DB...
>> 
>> Not sure what to do about that.  Any suggestions?
> 
> That's pretty odd, if this same LDIF already loaded successfully on
> another machine. Generally I'd interpret this error to mean you have a
> lot of indexing defined and some entry is generating a lot of index
> values. But that doesn't seem true if you're using the same config as
> another machine.
> 
> You can probably get past this error by tweaking back-mdb/tools.c but
> again, it makes no sense that you run into this problem on one machine
> but not on another, with identical config. (in tool_entry_open change
> writes_per_commit to 500 from the current value of 1000.)

Rebuilt the debian packages and the load now completes.  I am able to 
start the server and query it.  Maybe the writes_per_commit should be 
exposed to the user on the slapadd command line?

The server shutdown is really, really slow.  Mentioed it to Quanah and 
he thought it was related to the number of indexes.  I am still having 
some issues with the init script, but I need to do some more testing to 
understand what is going on.

Bill

-- 

Bill MacAllister
Infrastructure Delivery Group, Stanford University