[Date Prev][Date Next]
Re: cn=Connection 0,cn=Connections,cn=Monitor?!?
- To: Quanah Gibson-Mount <email@example.com>
- Subject: Re: cn=Connection 0,cn=Connections,cn=Monitor?!?
- From: Michael StrÃder <firstname.lastname@example.org>
- Date: Wed, 01 Feb 2012 19:43:03 +0100
- Cc: email@example.com
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1328121798; l=1439; s=domk; d=stroeder.de; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:CC:To:MIME-Version:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=tPiqbKwppBdDwVYnHTygnNB1/DA=; b=AreVcf9QkK1fBuIo6jRiMUJMYXTjKWfI9BiyxygPiNN+9yFoku5IFx2K1x0uiaVWLsX K+xoswSR3Z8Z89upO6/E8hdSjWirKRjNXCIf+eqlMVgMs4UMTGSIYxuJSEva0qhRGy8zu 1Rn7yW+uIAq8h0Bfr8Dw8LdEqHkFBPkTRVk=
- In-reply-to: <7DE3B19FD9DFF9A698576EB3@[192.168.1.45]>
- References: <4F296C20.firstname.lastname@example.org> <7DE3B19FD9DFF9A698576EB3@[192.168.1.45]>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Firefox/10.0 SeaMonkey/2.7
Quanah Gibson-Mount wrote:
--On Wednesday, February 01, 2012 5:45 PM +0100 Michael StrÃder
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?
IIRC, Connection "0" is a special internal slapd connection, but I don't
recall for what. ;)
While searching for other problems these entries caught my attention. And I'm
wondering why I see this only on a certain OS platform. So knowing what it's
for would be good to narrow down the cause.
If it is showing up twice for search results, then that
would be a bug, but I can't quite tell what exactly it is you're reporting.
Yes, returning two entries with the same DN violates the data model. That's
the issue. Or maybe Connection 0 should never appear at all?
But before writing an ITS I'd like to narrow down things to be able to
reproduce the issue in a minimal test configuration.