current value of nsslapd-changelogcompactdb-interval is 30 days. we have 10 core servers. Is this value can be configured with the different value for each server? Because recently I experience core crashed because of 'out of available lock entries' and 'db error - 12 Cannot allocate memory' We have 50000 for nsslapd-db-locks and 30 days for nsslapd-changelogcompactdb-interval . 30 days ago, all core servers are restarted for some reason and 30 days later, nsslapd-changelogcompactdb-interval is expired and all server run compactDB. while running compactDB, core server raised error with 'out of available lock entries' and 'db error - 12 Cannot allocate memory' and crashed.
Q1. nsslapd-changelogcompactdb-interval can be configured with different value for each server?
I'd like to add an additional question. while running compactDB in ldap, is the db lock count increased ?
freeipa-users@lists.fedorahosted.org
-
seojeong kim