Torsten Landschoff wrote:
I am deeply sorry, but I have to report 2.2.23 hitting the same problem for me.
How can this be? I thought all those bugs were elimated in 2.2 using db4.2?
I thought so as well. Did you use a DB_CONFIG file suited for your setup?
Yes, of course.
I am thinking along 8MB of caches or something.
#txn_checkpoint 128 15 1 set_cachesize 0 252428800 0 set_lk_max_objects 100000 set_lk_max_locks 100000 set_lg_regionmax 1048576 set_lg_max 8388608 set_lg_bsize 2097152 set_lg_dir /var/lib/ldap/logs/ #set_lk_detect DB_LOCK_DEFAULT set_tmp_dir /tmp/ #set_flags DB_TXN_NOSYNC #set_flags DB_TXN_NOT_DURABLE
Those enourmous amounts of possible locks have been set, after one of my replicas complained about being out of locks and the openldap-ML suggested increasing this number. Since I really need those servers, I went a little over the top with this value.
(txn_checkpoint does not work, I don't know why. bdb4.2 does not recognize it.)
Grüße, S°
-- Sven Hartge -- professioneller Unix-Geek und alltime Nerd Meine Gedanken im Netz: http://sven.formvision.de/blog/
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
