From owner-freebsd-questions@FreeBSD.ORG Sat Sep 30 13:27:55 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C62116A403 for ; Sat, 30 Sep 2006 13:27:55 +0000 (UTC) (envelope-from SRS0=eaBS/VOT=DN=asarian-host.net=admin@asarian-host.net) Received: from mail.asarian-host.net (mail.asarian-host.net [194.109.160.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 401E643D46 for ; Sat, 30 Sep 2006 13:27:54 +0000 (GMT) (envelope-from SRS0=eaBS/VOT=DN=asarian-host.net=admin@asarian-host.net) Received: from anonymizer.asarian-host.net (localhost [127.0.0.1]) (authenticated bits=0) by mail.asarian-host.net (8.13.5/8.13.5) with ESMTP id k8UDRqHM044768 for ; Sat, 30 Sep 2006 15:27:52 +0200 (CEST) (envelope-from admin@asarian-host.net) From: Mark Received-SPF: pass (asarian-host.net: 127.0.0.1 is authenticated by a trusted mechanism) receiver=anonymizer.asarian-host.net; client-ip=127.0.0.1; envelope-from=; helo=clientrunner.asarian-host.net; Message-Id: <200609301327.k8UDRmkD044758@asarian-host.net> Date: Sat, 30 Sep 2006 13:27:52 GMT X-Authenticated-Sender: admin@asarian-host.net X-Trace: gdHayhvyCSz56VA7B/hDpj2Mx5Wcyc1/ZR7tvTsrbmquJsSGS32AqTdJEz7+l6GI X-Complaints-To: abuse@asarian-host.net X-Abuse-Info: Please be sure to forward a copy of ALL headers, otherwise we are unable to process your complaint Organization: Asarian-host To: "'FreeBSD-Questions Questions'" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Auth: Asarian-host PGP signature iQEVAwUARR5w2DFqW1BleBN9AQFETAf7BaSv/AlpOu4mp+Or/pHi2Z4pZDezdNGh R7cCgfN6JH5RZPI0fkc+MCyR0LpwTpHyyG1jFe7WiPIfcWl4leqcWRAJpl+B44WK 1Mzo1mxiePQ33uJHDhNjdRxs67hJF+bbRjagiDGmyA44jfaVMGnxSHOABrLfuXdc j9bE4yvc7zCbwJM9ztnxwzof+97Be1KVqQpaXwTuPJC+559PwxVcDGybx+OXJM/L MF2vY6cG+M69ZjEdk22YllFQlR74CFzj2LrugTu99rmge/TxdlZ7gBO753ywMiaa DVmEOLuPzg8GIoYZcuccrYRobT4c+f1BFTfvu6fCXu8jQJjc9Ru6XA== =TLdf Subject: RE: Trouble with Berkeley DB version 4.4.20? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 13:27:55 -0000 Hello, I realize this is probably not the most flashy issue, but, if possible, I would really like an answer to this question. I compiled BerkeleyDB 4.4.20 with the following in config.in: INCLUDE = /usr/local/include/db44 LIB = /usr/local/lib # also tried /usr/local/lib/db44 directly DBNAME = -ldb-4.4 # end of file config.in I have done this upgrade path for BerkeleyDB and Perl several times; from 1.85 -> 4.1 -> 4.2, and now -> 4.4.20. It has always worked well. Even now it compiles just fine. It just isn't stable anymore. If someone out there has an idea, I'd really like to know. Thanks, - Mark > -----Original Message----- > From: Mark [mailto:admin@asarian-host.net] > Sent: vrijdag 29 september 2006 20:29 > To: 'FreeBSD-Questions Questions' > Subject: Trouble with Berkeley DB version 4.4.20? > > Hello, > > Am I the only person having trouble with Berkeley DB version 4.4.20? > I've been using 4.2 for quite a while. Then I upgraded, a few days back. > But a Perl process that actually uses it (BerkeleyDB-0.30) has become > unstable. I've been ktracing it, and setting log-points myself, but it > keeps core dumping at places where it accesses BerkeleyDB. Sporadically, > but often enough. > > Naturally I compiled BerkeleyDB-0.30 against the correct libraries (in > config.in). And it seems more or less ok, but not always. Finally, this > morning, I just did a full restore from an earlier date; db44 is not > working out for me, obviously. > > I'm not sure whether it's Berkeley DB version 4.4.20 or BerkeleyDB-0.30, > or a combination of the two; but I wonder if someone else has had trou- > ble with it, too? Sometimes I got a weird lock error notice; but other- > wise it remains a mystery. > > - Mark