Re: Upgrade to 2.4.35 Causes Instability, Errors

[Tim Gustafson <tjg@ucsc.edu>]

> When you say you upgraded, what all did you do?  Did you only upgrade the
> openldap binaries?  From what openldap release to what release?  Did your
> upgrade also change the version of BDB?  What version of BDB were you on?
> What one are you on now?  What does your DB_CONFIG file look like?  What
> does your db_stat -c usage show for locks/lockers/lock objects etc?

We're running FreeBSD.  I did a minor OS update from 8.2 to 8.4, and
then rebuilt all my ports using "portmaster".  We're using
db46-4.6.21.4 both before and after the upgrade.  DB_CONFIG is as
follows:

set_cachesize 0 67108864 1
set_flags DB_LOG_AUTOREMOVE

The output of "db_stat-4.6 -c" is:

116     Last allocated locker ID
0x7fffffff      Current maximum unused locker ID
9       Number of lock modes
1000    Maximum number of locks possible
1000    Maximum number of lockers possible
1000    Maximum number of lock objects possible
16      Number of current locks
24      Maximum number of locks at any one time
105     Number of current lockers
111     Maximum number of lockers at any one time
16      Number of current lock objects
22      Maximum number of lock objects at any one time
4144507 Total number of locks requested
4144491 Total number of locks released
0       Total number of locks upgraded
36      Total number of locks downgraded
38      Lock requests not available due to conflicts, for which we waited
0       Lock requests not available due to conflicts, for which we did not wait
0       Number of deadlocks
0       Lock timeout value
0       Number of locks that have timed out
0       Transaction timeout value
0       Number of transactions that have timed out
712KB   The size of the lock region
13666   The number of region locks that required waiting (0%)

--

Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A