Control: tag -1 moreinfo
On Mon, Feb 29, 2016 at 03:57:30PM +0100, Thomas Otto wrote:
ldapmodify -Z -h ldaptest1
...
dn: olcDatabase={3}hdb,cn=config
changetype: modify
replace: olcDbConfig
olcDbConfig: # Note: most DB_CONFIG settings will take effect only upon
rebuilding
olcDbConfig: # the DB environment.
olcDbConfig: #
olcDbConfig: # one 0.25 GB cache
olcDbConfig: #set_cachesize 0 268435456 1
olcDbConfig: set_cachesize 1 0 1
olcDbConfig: # Data Directory
olcDbConfig: #set_data_dir db
olcDbConfig: # Transaction Log settings
olcDbConfig: set_lg_regionmax 262144
olcDbConfig: set_lg_bsize 2097152
olcDbConfig: #set_lg_dir logs
olcDbConfig: # delete Transaction Logs:
olcDbConfig: set_flags DB_LOG_AUTOREMOVE
olcDbConfig: # Note that if the log files are removed automatically, recovery
after
olcDbConfig: # a catastrophic failure is likely to be impossible.
olcDbConfig: # http://wiki.zimbra.com/wiki/OpenLDAP_Performance_Tuning_5.0
olcDbConfig: # db5.1_stat -c -h /var/lib/ldap/logs
olcDbConfig: set_lk_max_locks 60000
olcDbConfig: set_lk_max_objects 25000
olcDbConfig: set_lk_max_lockers 1500
modifying entry "olcDatabase={3}hdb,cn=config"
ldap_modify: Other (e.g., implementation specific) error (80)
additional info: failed to reopen database, rc=22
I performed the same modification on a new install of slapd
2.4.40+dfsg-1+deb8u2, and did not observe a crash.
What was the olcDbConfig value prior to this change?
What sort of load was slapd under at the time? From the name, I guess
this might be an accesslog database?
I don't know for sure whether it's relevant, but for completeness: do
you have other hdb databases, and what do their configs look like?
If you can think of any other information that might help reproduce the
crash, please mention it.
thanks,
Ryan
