Bill MacAllister wrote:
--On Thursday, February 21, 2013 07:01:14 PM -0800 Bill MacAllister whm@stanford.edu wrote:
--On Thursday, February 21, 2013 03:24:01 PM -0800 Quanah Gibson-Mount quanah@zimbra.com wrote:
If you know how to build OpenLDAP manually, and would like to participate in testing the next set of code for the 2.4.34 release, please do so.
Generally, get the code for RE24:
Configure & build.
Execute the test suite (via make test) after it is built.
Thanks!
--Quanah
Built debian packages, installed on a master, and loaded the database. This is on debian testing (wheezy). The master looks fine. This is using back-mdb. Load with mdb is much faster than old hdb backends. I will get some real numbers in a day or two.
I am having issues with the slave. Packages install fine. When I start to slapadd load data theeta starts at 5 minutes and just keeps increasing. I killed it after about 15 minutes when the eta hit 25 minutes and was still climbing. Thought it must be something in my configuration and just tried pulling the exact configuration I used to load the master to the slave hardware and got the same results. More debugging to do to try and figure out what is up, but it does not look like a openldap problem. When the load starts to slow down the progress display freezes for 30-60 seconds (a guess, but a while anyway) and then picks up again.
The partition holding the mdb database was initialized as ext4 and mounted with acls turned on. I reinitialized the partition as ext3 and mounted it without acl support. The load of the slave looks more reasonable now. Unfortunately, it did not finish.
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=edu" (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.)