Monday, June 7, 2021

[389-users] Re: Can't locate CSN - replica issue

Gasp, I suspect the problem seems to be here. In the agreements I see

dn: cn=it 2--\3E1,cn=replica,cn=c\3Dit,cn=mapping tree,cn=config
objectClass: top
objectClass: nsds5replicationagreement
cn: it 2-->1
cn: it 2--\>1
nsDS5ReplicaRoot: c=it
description: it 2-->1
nsDS5ReplicaPort: 389
nsDS5ReplicaBindMethod: simple
nsDS5ReplicaTransportInfo: LDAP
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsds50ruv: {replicageneration} 60704f730000c3500000
nsds50ruv: {replica 50001 ldap://} 607424dd0000c3510
000 60ba18fb0000c3510000
nsds50ruv: {replica 50000 ldap://} 6074264a0000c3500000 6
nsds50ruv: {replica 50002 ldap://} 607426410000c3520
000 60ba19050000c3520000
nsruvReplicaLastModified: {replica 50001 ldap://} 00
nsruvReplicaLastModified: {replica 50000 ldap://} 0000000
nsruvReplicaLastModified: {replica 50002 ldap://} 00
nsds5replicareapactive: 0
nsds5replicaLastUpdateStart: 20210604124542Z
nsds5replicaLastUpdateEnd: 20210604124542Z
nsds5replicaChangesSentSinceStartup:: NTAwMDI6NC8wIA==

The replica ID 50000 corresponds to the server, the first host installed in a set of three multimaster servers. The balancer host is As suggested by dscreate I put the balancer host in the parameter "full_machine_name" for all LDAP servers. For a reason which I don't know the full_machine_name (the load balancer host) has been written in the ruv in place of the fqdn of the machine host containing the dirsrv installation. In this case, in place of

I suspect that if I reinstall all servers with their hostname in "full_machine_name" I resolve my issue.

Any idea?

Thank you very much
389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam on the list, report it:

No comments:

Post a Comment