From owner-freebsd-current@FreeBSD.ORG Sat May 5 19:11:37 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 66D201065672 for ; Sat, 5 May 2012 19:11:37 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 1E3C88FC08 for ; Sat, 5 May 2012 19:11:37 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1SQkOG-0007sW-4d>; Sat, 05 May 2012 21:11:36 +0200 Received: from e178019154.adsl.alicedsl.de ([85.178.19.154] helo=munin.geoinf.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1SQkOG-0003AH-0k>; Sat, 05 May 2012 21:11:36 +0200 Message-ID: <4FA57B5A.8030203@zedat.fu-berlin.de> Date: Sat, 05 May 2012 21:11:22 +0200 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120504 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Bjoern A. Zeeb" , freebsd-current@freebsd.org References: <4FA54D4A.4050703@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 85.178.19.154 Cc: Subject: Re: OpenLDAP 2.4.31 on FreeBSD 10.0-CURRENT/amd64 broken! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2012 19:11:37 -0000 On 05/05/12 20:36, Bjoern A. Zeeb wrote: > On 5. May 2012, at 15:54 , Hartmann, O. wrote: > >> I'm floating like a dead man in the water and I was wondering if someone >> else doesn't face this problem. FreeBSD is said to be run in large >> environments, so at least one should have OpenLDAP as user backend >> running ... > > Ok, I am running the same openldap version on HEAD in production on amd64 and i386. > My HEAD is from about 20120426 1130 UTC and my packages are cleanly build on that > wprld. Here: FreeBSD 10.0-CURRENT #0 r235062: Sat May 5 20:02:26 CEST 2012 I can not say what the last working SVN release tag was, maybe around r234900, I can't say. As I wrote, Thursday last week, ~20120503, a buildworld from 20120502 worked fine. On Thursday 03.05.2012 I did the last source update and buildworld, shutdown the box at home and switched it on on Friday morning before heading to the laboratory - and LDAP failed. At the lab, the box was still working, but I was highly risky in my motivations and recompiled that box with a freshly updates source tree - and it failed, too. I did not follow the tags, sorry. Last I realized flushing into the sources was OpenSSL stuff due to security issues. I use OpenSSL certificates to connect via TLS to the server. There is also usually no core dumped. > > > The differences to what I see with your setups are: > > 1) I am still on db48. > > 2) ? Contrary to you I probably have MALLOC_PRODUCTION set for my builds; > not sure if that makes a difference but if this problem started recently > the jemalloc import could be the cause? You didn't say from when your > last and your latest HEAD was. MALLOC_PRODUCTION is set in /etc/make.conf as well as in /etc/src.conf. /etc/src.conf is this on both failing FBSD 10.0-CUR boxes: WITH_CLANG= YES WITH_CLANG_EXTRAS= YES # WITH_BIND_LARGE_FILE= YES WITH_BIND_SIGCHASE= YES WITH_BIND_LIBS= YES # WITH_IDEA= YES WITH_HESIOD= YES # #WITH_BSD_GREP= YES #WITH_ICONV= YES # WITH_LIBCPLUSPLUS= YES # #WITH_OFED= YES # PORTS_MODULES= x11/nvidia-driver # MALLOC_PRODUCTION= YES Grüße, Oliver > > Gruesse > /bz >