Hi Noriko,
There are three MMR replicating servers. It's one
month of uptime and the servers wanted to trim the
replication log. Here is what i've found in error log
on each of them :
1st server:
[18/Jun/2015:08:04:31 +0200] - libdb: BDB2055 Lock
table is out of available lock entries
May not matter, but could you please try increasing the
value of this db config parameter? The default value is
10000.
dn: cn=config,cn=ldbm
database,cn=plugins,cn=config
nsslapd-db-locks: 10000
Ok. I've increased nsslapd-db-locks to 20000 and reduced
nsslapd-changelogcompactdb-interval to 3600 in
cn=changelog5,cn=config to see the changelog free event more
frequently. No change. I have still :
[19/Jun/2015:10:36:46 +0200] - libdb: BDB2055 Lock table
is out of available lock entries
[19/Jun/2015:10:36:46 +0200] NSMMReplicationPlugin -
changelog program - _cl5CompactDBs: failed to compact
a45fa684-f28d11e4-af27aa63-5121b7ef; db error - 12 Cannot
allocate memory
[18/Jun/2015:08:04:31 +0200] NSMMReplicationPlugin
- changelog program - _cl5CompactDBs: failed to
compact a45fa684-f28d11e4-af27aa63-5121b7ef; db error
- 12 Cannot allocate memory
I don't thing there is any problem even if the DBs are not
compacted. It was introduced just to release the free pages
in the db files. But I'd also like to learn why the compact
fails with ENOMEM here.
Ok, thanks.