HI!
on one platform on various servers I see strange entries in back-monitor (see below). It's an installation of RE24 committ-id 22ee28752e3e0d2a6910a22922fc69befd78578a self-compiled on RHEL 6.2 x86_64 linked to BDB, SASL and OpenSSL shipped with RHEL.
We have two custom overlays in this setup but disabling them did not make this monitor entries disappear.
On my local test system on openSUSE 11.4 x86_64 I don't see this.
Any idea under which condition such monitor entries can appear and where to look in my configuration?
Ciao, Michael.
--------------------------------- snip --------------------------------- dn: cn=Connection 0,cn=Connections,cn=Monitor structuralObjectClass: monitorConnection creatorsName: modifiersName: createTimestamp: 19700101000000Z modifyTimestamp: 19700101000000Z monitorConnectionNumber: 0 monitorConnectionProtocol: 0 monitorConnectionOpsReceived: 0 monitorConnectionOpsExecuting: 0 monitorConnectionOpsPending: 0 monitorConnectionOpsCompleted: 0 monitorConnectionGet: 0 monitorConnectionRead: 0 monitorConnectionWrite: 0 monitorConnectionMask: L monitorConnectionListener: monitorConnectionPeerDomain: unknown monitorConnectionPeerAddress: unknown monitorConnectionLocalAddress: monitorConnectionStartTime: 19700101000000Z monitorConnectionActivityTime: 19700101000000Z entryDN: cn=Connection 0,cn=Connections,cn=Monitor subschemaSubentry: cn=Subschema hasSubordinates: FALSE
dn: cn=Connection 0,cn=Connections,cn=Monitor structuralObjectClass: monitorConnection creatorsName: modifiersName: createTimestamp: 19700101000000Z modifyTimestamp: 19700101000000Z monitorConnectionNumber: 0 monitorConnectionProtocol: 0 monitorConnectionOpsReceived: 0 monitorConnectionOpsExecuting: 0 monitorConnectionOpsPending: 0 monitorConnectionOpsCompleted: 0 monitorConnectionGet: 0 monitorConnectionRead: 0 monitorConnectionWrite: 0 monitorConnectionMask: L monitorConnectionListener: monitorConnectionPeerDomain: unknown monitorConnectionPeerAddress: unknown monitorConnectionLocalAddress: monitorConnectionStartTime: 19700101000000Z monitorConnectionActivityTime: 19700101000000Z entryDN: cn=Connection 0,cn=Connections,cn=Monitor subschemaSubentry: cn=Subschema hasSubordinates: FALSE