Bug 2196052

Summary: RFE errors log NSMMReplicationPlugin connection linger events with conn id
Product: Red Hat Enterprise Linux 9 Reporter: Marc Sauton <msauton>
Component: 389-ds-baseAssignee: LDAP Maintainers <idm-ds-dev-bugs>
Status: NEW --- QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 9.4CC: idm-ds-dev-bugs, musoni, pasik, vashirov
Target Milestone: betaKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marc Sauton 2023-05-07 20:24:16 UTC 
Description of problem:

RFE , add a connection ID in the errors log NSMMReplicationPlugin connection linger events to help troubleshooting, following/identifying the corresponding events in the access log.


Version-Release number of selected component (if applicable):
RHDS 12 and 11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

example:

errors log events:

[07/May/2023:15:35:01.617020405 -0400] - DEBUG - NSMMReplicationPlugin - conn_start_linger -agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389) - Beginning linger on the connection
[07/May/2023:15:36:01.622123998 -0400] - DEBUG - NSMMReplicationPlugin - linger_timeout - agmt="cn=s1-to-s2-exampletest" (permanent-rhds11-s2:389) - Linger timeout has expired on the connection

have to manually match in the access log by time stamp, with a non exact pattern, for example [07/May/2023:15:35:01.617212996 -0400] and [07/May/2023:15:36:02.435956010 -0400] for conn=42 op=6 and conn=42 op=8

[07/May/2023:15:27:40.453976993 -0400] conn=42 fd=84 slot=84 connection from 10.0.100.137 to 10.0.103.105
[07/May/2023:15:27:40.484323435 -0400] conn=42 op=0 BIND dn="cn=replication manager,cn=config" method=128 version=3
[07/May/2023:15:27:40.484754746 -0400] conn=42 op=0 RESULT err=0 tag=97 nentries=0 wtime=0.029170378 optime=0.000431897 etime=0.029601058 dn="cn=replication manager,cn=config"
[07/May/2023:15:27:40.507948089 -0400] conn=42 op=1 SRCH base="" scope=0 filter="(objectClass=*)" attrs="supportedControl supportedExtension"
[07/May/2023:15:27:40.508589297 -0400] conn=42 op=1 RESULT err=0 tag=101 nentries=1 wtime=0.022477029 optime=0.000641655 etime=0.023118029
[07/May/2023:15:27:40.535973648 -0400] conn=42 op=2 SRCH base="" scope=0 filter="(objectClass=*)" attrs="supportedControl supportedExtension"
[07/May/2023:15:27:40.536744738 -0400] conn=42 op=2 RESULT err=0 tag=101 nentries=1 wtime=0.026904879 optime=0.000771261 etime=0.027675231
[07/May/2023:15:27:40.559907034 -0400] conn=42 op=3 EXT oid="2.16.840.1.113730.3.5.12" name="replication-multimaster-extop"
[07/May/2023:15:27:40.574166463 -0400] conn=42 op=3 RESULT err=0 tag=120 nentries=0 wtime=0.019892952 optime=0.014261595 etime=0.034152584
[07/May/2023:15:34:17.794623924 -0400] conn=42 op=4 EXT oid="2.16.840.1.113730.3.5.5" name="replication-multimaster-extop"
[07/May/2023:15:34:47.216486655 -0400] conn=42 op=4 RESULT err=0 tag=120 nentries=0 wtime=30.199080439 optime=29.421865495 etime=59.620944251
[07/May/2023:15:34:51.058638571 -0400] conn=42 op=5 EXT oid="2.16.840.1.113730.3.5.12" name="replication-multimaster-extop"
[07/May/2023:15:34:51.069490280 -0400] conn=42 op=5 RESULT err=0 tag=120 nentries=0 wtime=0.000093755 optime=0.010857674 etime=0.010949685
[07/May/2023:15:35:01.617212996 -0400] conn=42 op=6 EXT oid="2.16.840.1.113730.3.5.5" name="replication-multimaster-extop"
[07/May/2023:15:35:01.620282313 -0400] conn=42 op=6 RESULT err=0 tag=120 nentries=0 wtime=10.547142333 optime=0.003073251 etime=10.550214077
[07/May/2023:15:36:02.435956010 -0400] conn=42 op=8 UNBIND
[07/May/2023:15:36:02.436429948 -0400] conn=42 op=8 fd=84 closed error - U1


Expected results:
yes

Additional info: