Description of problem: add a message with the conn ID and conn->linger_time in the replication session connection's conn_start_linger event ldap/servers/plugins/replication/repl5_connection.c conn_start_linger(Repl_Connection *conn) near the call to slapi_eq_once_rel() } else { conn->linger_active = PR_TRUE; conn->linger_event = slapi_eq_once_rel(linger_timeout, conn, now + conn->linger_time); conn->status = STATUS_LINGERING; } PR_Unlock(conn->lock); } Version-Release number of selected component (if applicable): RHDS-11 389-ds-base-1.4.3.31-11 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: ==> /var/log/dirsrv/slapd-test/errors <== [07/May/2023:16:57:42.519436852 -0400] - DEBUG - NSMMReplicationPlugin - conn_start_linger -agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389) - Beginning linger on the connection [07/May/2023:16:57:42.519844457 -0400] - DEBUG - NSMMReplicationPlugin - repl5_inc_run - agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389): State: sending_updates -> wait_for_changes ==> /var/log/dirsrv/slapd-test/access <== [07/May/2023:16:58:42.142693600 -0400] conn=21 op=19 UNBIND [07/May/2023:16:58:42.143338818 -0400] conn=21 op=19 fd=84 closed error - U1 ==> /var/log/dirsrv/slapd-test/errors <== [07/May/2023:16:58:42.526376736 -0400] - DEBUG - NSMMReplicationPlugin - linger_timeout - agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389) - Linger timeout has expired on the connection [07/May/2023:16:58:42.526964276 -0400] - DEBUG - NSMMReplicationPlugin - close_connection_internal - agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389) - Disconnected from the consumer
forgot the agreement name information from agmt_get_long_name(conn->agmt) would also be nice to have in such a message.