[389-users] Re: enabled account policy plugin and incrace changelog db size

the server1:

dn: cn=ldap1-ldap2,cn=replica,cn=dc\3Dsagliknet\2Cdc\3Dsaglik\2Cdc\3Dgov\2Cdc\
 3Dtr,cn=mapping tree,cn=config
objectClass: top
objectClass: nsDS5ReplicationAgreement
description: ldap1 -> ldap2
cn: ldap1-ldap2
nsDS5ReplicaRoot: dc=sagliknet,dc=saglik,dc=gov,dc=tr
nsDS5ReplicaHost: 172.16.54.181
nsDS5ReplicaPort: 389
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaTransportInfo: LDAP
nsDS5ReplicaBindMethod: SIMPLE
nsDS5ReplicaCredentials: {AES********
nsds5replicareapactive: 0
nsds5replicaLastUpdateStart: 20170526084327Z
nsds5replicaLastUpdateEnd: 19700101000000Z
nsds5replicaChangesSentSinceStartup:: MToxMjE2MTE0Mi8xNDUg
nsds5replicaLastUpdateStatus: Error (0) Replica acquired successfully: Increme
 ntal update started
nsds5replicaUpdateInProgress: TRUE
nsds5replicaLastInitStart: 20170522184342Z
nsds5replicaLastInitEnd: 20170522184404Z
nsds5replicaLastInitStatus: 0 Total update succeeded


the other server2:

dn: cn=mhrsldap2-mhrsldap1,cn=replica,cn=dc\3Dsagliknet\2Cdc\3Dsaglik\2Cdc\3Dg
 ov\2Cdc\3Dtr,cn=mapping tree,cn=config
objectClass: top
objectClass: nsDS5ReplicationAgreement
description: mhrsldap2 => mhrsldap1
cn: mhrsldap2-mhrsldap1
nsDS5ReplicaRoot: dc=sagliknet,dc=saglik,dc=gov,dc=tr
nsDS5ReplicaHost: 172.16.54.180
nsDS5ReplicaPort: 389
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaTransportInfo: LDAP
nsDS5ReplicaBindMethod: SIMPLE
nsDS5ReplicaCredentials: *************
nsds50ruv: {replicageneration} 55dc8a41000000010000
nsds50ruv: {replica 1 ldap://mhrsldap1.localdomain:389} 55dd9ef0000000010000 5
 91976c7001500010000
nsds50ruv: {replica 2 ldap://mhrsldap2.localdomain:389} 55df0ea1000000020000 5
 91976c3008800020000
nsruvReplicaLastModified: {replica 1 ldap://mhrsldap1.localdomain:389} 0000000
 0
nsruvReplicaLastModified: {replica 2 ldap://mhrsldap2.localdomain:389} 0000000
 0
nsds5replicareapactive: 0
nsds5replicaLastUpdateStart: 20170522184536Z
nsds5replicaLastUpdateEnd: 19700101000000Z
nsds5replicaChangesSentSinceStartup:: Mjo3NDkzMDg4LzAgMDozMC8wIA==
nsds5replicaLastUpdateStatus: Error (0) Replica acquired successfully: Increme
 ntal update started
nsds5replicaUpdateInProgress: TRUE
nsds5replicaLastInitStart: 19700101000000Z
nsds5replicaLastInitEnd: 19700101000000Z

2017-05-26 11:36 GMT+03:00 Alparslan Ozturk <alparslan.ozturk@gmail.com>:

Hi William,
number of change very big. what I am doing wrong ?

2017-05-26 2:44 GMT+03:00 William Brown <wibrown@redhat.com>:

On Thu, 2017-05-25 at 13:24 -0400, Mark Reynolds wrote:
>
> On 05/25/2017 03:23 AM, Alparslan Ozturk wrote:
> > Hi,
> >
> > two 389-ds running with multimaster replication. and dbbackup size
> > 66MB but when I have enabled "account policy plugin" for tracing
> > lastlogintime of users.

> >
> >
> > How can I fix the changelog db size problem.
>
> I just wrote this wiki page to address this changelog size issue:
>
> http://www.port389.org/docs/389ds/FAQ/changelog-trimming.html
>

Check your RUV's too.

The changelog only trims entries that are both *fully resolved* on all
masters and where the time / size has past.

So if you have a master that is not accepting updates, no matter your
trim settings, the changelog will grow continually until that master is
resolved to a sane state.

I hope that helps,

--
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane