Hi Andrey,
On 06/18/2015 01:23 AM, Ivanov Andrey (M.) wrote:
Hi,
we are using the branch 1.3.2 on CentOS7 in our production
environment (version 1.3.2.27 with some additional patches
from the git of this branch).
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
[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.
Thanks,
--noriko
2nd server:
[18/Jun/2015:08:10:34 +0200] - libdb: BDB2055 Lock table is
out of available lock entries
[18/Jun/2015:08:10:34 +0200] NSMMReplicationPlugin - changelog
program - _cl5CompactDBs: failed to compact
acb7e184-f28d11e4-9b13d240-c66923c8; db error - 12 Cannot
allocate memory
3rd server:
[18/Jun/2015:08:18:10 +0200] - libdb: BDB2055 Lock table is
out of available lock entries
[18/Jun/2015:08:18:10 +0200] NSMMReplicationPlugin - changelog
program - _cl5CompactDBs: failed to compact
acb7e184-f28d11e4-8067eff8-b1ca763b; db error - 12 Cannot
allocate memory
The changelog itself is not huge :
[root@ldap-ens]# ll -h
/Local/dirsrv/var/lib/dirsrv/slapd-ens/changelogdb/
total 390M
-rw------- 1 ldap ldap 390M Jun 18 10:18
a45fa684-f28d11e4-af27aa63-5121b7ef_5547be40000000010000.db
-rw-r--r-- 1 ldap ldap 0 May 19 08:02
a45fa684-f28d11e4-af27aa63-5121b7ef.sema
-rw------- 1 ldap ldap 30 May 4 20:45 DBVERSION
The server are working correctky, the replication is also
working
What are the potential consequences of this error? How can
we avoid it?
Thank you!
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users