On 04Jul25 06:25+0000, Windl, Ulrich wrote:
Too bad: I also noticed that syncrepl RefeshAndPersist connections are not shown in the connection monitor (or I was unable to find those).
Check for entry with oc olmSyncReplInstance on the database which has syncrepl configured. The setting 'monitoring' in the database section defaults to on.
This results in my case: ``` # Consumer 001, Database 1, Databases, Monitor dn: cn=Consumer 001,cn=Database 1,cn=Databases,cn=Monitor objectClass: olmSyncReplInstance structuralObjectClass: olmSyncReplInstance cn: Consumer 001 creatorsName: cn=monadm,cn=Monitor modifiersName: cn=monadm,cn=Monitor createTimestamp: 20250701104800Z modifyTimestamp: 20250701104800Z olmSRProviderURIList: ldap://10.88.0.2 olmSRConnection: IP=10.88.0.1:49602 olmSRSyncPhase: Persist olmSRNextConnect: 00000101000000Z olmSRLastConnect: 20250701104820Z olmSRLastContact: 20250704045546Z olmSRLastCookieRcvd: rid=001,sid=038,csn=20250704045546.696674Z#000000#038#000 000 olmSRLastCookieSent: rid=001,sid=037,csn=20231117084531.264299Z#000000#001#000 000;20231113122043.351289Z#000000#002#000000;20240618124202.786940Z#000000#03 7#000000;20250701094202.306893Z#000000#038#000000 entryDN: cn=Consumer 001,cn=Database 1,cn=Databases,cn=Monitor subschemaSubentry: cn=Subschema hasSubordinates: FALSE ```
slapd 2.6.9
Cheers,