https://bugs.openldap.org/show_bug.cgi?id=10293
--- Comment #14 from Ondřej Kuzník <[email protected]> --- On Thu, Nov 20, 2025 at 07:58:35PM +0000, [email protected] wrote: > In this context, I extracted the following line from a log from Slave-1A at > Vitality as an example. Please help me understand what I am supposed to take > away from this line that doesn't indicate that the syncrepl process is > handling > modification of something. > --- > 2025-01-13T12:28:44.007990+00:00 ip-10-105-13-212 slapd[54734]: > syncrepl_message_to_op: rid=001 be_modify > uid=refer_mgr,ou=specialusers,dc=vitality,dc=co,dc=uk (0) I have put the patch up as a merge request here: https://git.openldap.org/openldap/openldap/-/merge_requests/821 As an example, the log message above might look like this instead: 2025-01-13T12:28:44.007990+00:00 ip-10-105-13-212 slapd[54734]: rid=001 SYNC ENTRY dn="uid=refer_mgr,ou=specialusers,dc=vitality,dc=co,dc=uk" state=1 cookie=20250113122000.654321Z#000000#001#000000 etime=0.123456 result=processed As proposed, etime is the time it took from decoding the message (entry in this case) to the point it was processed and any changes effected. Regards, -- You are receiving this mail because: You are on the CC list for the issue.
