Another instance where replication is stuck and not recovering. # requesting: contextCSN contextCSN: *20241229135907.725117Z#000000#000#000000* aaa-prod-aws-10:2636 # requesting: contextCSN contextCSN:* 20241228185913.665451Z#000000#000#000000*
*Log info:* Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: do_syncrep2: rid=650 cookie=rid=650,csn=20241228185913.665451Z#000000#000#000000 Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: syncrepl_entry: rid=650 LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_MODIFY) csn=20241228185913.665451Z#000000#000#000000 tid 0x7f26ee5fd640 Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: slap_queue_csn: queueing 0x7f26e0dcee50 20241228185913.665451Z#000000#000#000000 Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: slap_graduate_commit_csn: removing 0x7f26e0dcee50 20241228185913.665451Z#000000#000#000000 Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: slap_queue_csn: queueing 0x7f26e0f34360 20241228185913.665451Z#000000#000#000000 Dec 28 13:59:21 aaa-prod-aws-10 slapd[1161864]: slap_graduate_commit_csn: removing 0x7f26e0f34360 20241228185913.665451Z#000000#000#000000 Nothing gets logged about replication after the above. Am I missing something? Regards, Suresh On Sat, Dec 28, 2024 at 10:05 AM Suresh Veliveli < [email protected]> wrote: > Any thoughts? > > Thanks, > suresh > > On Tue, Dec 24, 2024 at 10:41 AM Suresh Veliveli < > [email protected]> wrote: > >> This is another instance where replication stops. >> >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_MODIFY) >> csn=20241223060050.594465Z#000000#000#000000 tid 0x7f5aed0fb640 >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> be_search (0) >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> uid=xxxx,ou=People,dc=georgetown,dc=edu >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> be_modify uid=xxxxx,ou=People,dc=georgetown,dc=edu (0) >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_message_to_entry: >> rid=143 DN: uid=xxxxx,ou=People,dc=georgetown,dc=edu, UUID: >> db41232e-527d-103f-995c-4344349468b5 >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_MODIFY) >> csn=20241223060104.603554Z#000000#000#000000 tid 0x7f5aed0fb640 >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> be_search (0) >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> uid=yyyyy,ou=People,dc=georgetown,dc=edu >> Dec 23 01:01:23 aaa-prod-aws-3 slapd[1182444]: syncrepl_entry: rid=143 >> be_modify uid=yyyy,ou=People,dc=georgetown,dc=edu (0) >> >> No "syncrep_" messages were logged after the above. >> >> Regards, >> Suresh >> >> On Mon, Dec 23, 2024 at 2:42 PM Quanah Gibson-Mount <[email protected]> >> wrote: >> >>> >>> >>> --On Friday, December 20, 2024 5:46 PM -0500 Suresh Veliveli >>> <[email protected]> wrote: >>> >>> > >>> > I do have these but no syncrepl_sync. >>> > >>> > >>> > Dec 12 08:59:30 aaa-prod-gcp-9 slapd[4165]: syncrepl_message_to_entry: >>> > rid=129 DN: uid=xxxx,ou=xxxx,dc=georgetown,dc=edu, UUID: >>> > 37387976-3ae0-103f-94fc-3b4be3361dc7 >>> > Dec 12 08:59:30 aaa-prod-gcp-9 slapd[4165]: syncrepl_entry: rid=129 >>> > LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_MODIFY) >>> > csn=20241212135921.652395Z#000000#000#000000 tid 0x7f671b7fe640 >>> >>> Yes sorry, that was a typo on my end. >>> >>> "syncrepl_" sync messages. Specifically you want to see the ones that >>> have >>> "be_" in them, but not "be_search". I.e., be_add, be_modify, etc. They >>> show the result of the operation, something like: >>> >>> syncrepl_entry: rid=100 be_modify <DN> (<result code>) >>> >>> --Quanah >>> >>> >> >> -- >> Suresh Veliveli >> Sr. UNIX Systems Engineer >> Georgetown University >> University Information Services | Security Infrastructure and >> Policy-Identity and Collaboration >> 202-262-6676 (cell) | 202-687-3108 (work) >> > >
