[Date Prev][Date Next]
Re: Lock table is out of available locks
--On May 9, 2012 9:45:52 AM +0200 Marc Patermann
Quanah Gibson-Mount schrieb (08.05.2012 17:12 Uhr):
--On Tuesday, May 08, 2012 3:41 PM +0200 Marc Patermann
while extending an object by adding a lot of maildrop values, slapd
refused to MOD with err 80:
Can anyone tell me what happens here and what to do about it?
You ran out of locks. Increase them in your DB_CONFIG file.
1000 Maximum number of locks possible
1000 Maximum number of locks at any one time
Does this say the maximum values were actually reached at one time?
Where the other values say that they were not even close the the maximum?
7 Number of current locks
131 Number of current lockers
196 Maximum number of lockers at any one time
8 Number of current lock objects
611 Maximum number of lock objects at any one time
These numbers say what was currently in use, not what the max was (for
There are 3 different buckets: lock objects, lockers, and locks. You ran
out of locks, and were fine on lockers/lock objects. So the only thing you
have to increase is locks. It would probably be wise to increase lock
objects as well, because they were getting fairly close. lockers was
So I have to set like
dbconfig set_lk_max_objects 2000
dbconfig set_lk_max_lockers 2000
dbconfig set_lk_max_locks 2000
in slapd.conf, right?
Correct. As noted above, you probably don't have to increase the lockers
Do I have to rebuild the database by slapcat/rm/slapadd or can these
changes be done by one of the db_* tools?
(While simply restarting slapd does not activate them.)
Stop slapd, remove your existing DB_CONFIG file, and restart slapd should
take care of it.
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration