Yes. New changes have been sent to other replicas. Only rid=129 is stuck until restart; after that, it catches up. Limits are set to unlimited for the replication dn.
limits dn.exact="uid=syncrepladmin,ou=RepAdmin,dc=georgetown,dc=edu" time.soft=unlimited time.hard=unlimited size.soft=unlimited size.hard=unlimited
Thanks, Suresh
On Wed, Mar 5, 2025 at 5:41 AM Ondřej Kuzník ondra@mistotebe.net wrote:
On Tue, Mar 04, 2025 at 11:27:21AM -0500, Suresh Veliveli wrote:
Not for rid=129.
Feb 27 11:59:53 aaa-prod-master-1 slapd[155194]: conn=3685651 op=1
syncprov_sendresp: cookie=rid=129,csn=20250227165948.741563Z#000000#000#000000
Feb 27 11:59:53 aaa-prod-master-1 slapd[155194]: conn=3685651 op=1
syncprov_sendresp: cookie=rid=129,csn=20250227165948.748550Z#000000#000#000000
Feb 27 23:07:07 aaa-prod-master-1 slapd[693294]: conn=8478 op=1
syncprov_sendresp: cookie=rid=129,csn=20250228040634.365834Z#000000#000#000000
For other replicas: Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1129 op=1
syncprov_sendresp: cookie=rid=245,csn=20250227165924.192557Z#000000#000#000000
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1129 op=1
syncprov_sendresp: sending LDAP_SYNC_MODIFY, dn=uid=mbw86,ou=people,dc=georgetown,dc=edu
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=3554242 op=1
syncprov_sendresp: cookie=rid=143,csn=20250227165918.446243Z#000000#000#000000
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=3554242 op=1
syncprov_sendresp: sending LDAP_SYNC_MODIFY, dn=uid=res128,ou=people,dc=georgetown,dc=edu
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1155 op=1
syncprov_sendresp: cookie=rid=247,csn=20250227165921.534510Z#000000#000#000000
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1155 op=1
syncprov_sendresp: sending LDAP_SYNC_MODIFY, dn=uid=jh2526,ou=people,dc=georgetown,dc=edu
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1127 op=1
syncprov_sendresp: cookie=rid=644,csn=20250227165917.751851Z#000000#000#000000
Feb 27 12:00:00 aaa-prod-master-1 slapd[155194]: conn=1127 op=1
syncprov_sendresp: sending LDAP_SYNC_MODIFY, dn=uid=mpssim,ou=people,dc=georgetown,dc=edu
I can't see any errors or anything interesting in here, but is there anything newer than 20250227165948.748550Z#000000#000#000000 that's sent to the other replicas before you restarted the provider - is rid=129 the only one that got stuck? Can't find the relevant bits in the configuration you've posted so far, are you sure the replication identity has their limits (time and size limits) set to unlimited?
Thanks,
-- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP