From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs393992ebc; Mon, 18 Jan 2010 11:44:05 -0800 (PST) Received: by 10.224.23.145 with SMTP id r17mr1742800qab.119.1263843844567; Mon, 18 Jan 2010 11:44:04 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 8si3050730qwj.43.2010.01.18.11.44.04; Mon, 18 Jan 2010 11:44:04 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id F31FA3C804B; Mon, 18 Jan 2010 14:44:03 -0500 (EST) Received: from ns2.limegroup.com (ns2.limegroup.com [64.20.166.97]) by rubyforge.org (Postfix) with ESMTP id 24CD718582C2 for ; Mon, 18 Jan 2010 14:43:36 -0500 (EST) Received: from ns1.limegroup.com (ns1.limegroup.com [10.1.1.5]) by ns2.limegroup.com (8.13.1/8.13.1) with ESMTP id o0IJhamF016131 for ; Mon, 18 Jan 2010 14:43:36 -0500 Received: from lithium-a.limegroup.com (lithium-a.limegroup.com [10.1.1.12]) by ns1.limegroup.com (8.13.1/8.13.1) with ESMTP id o0IJhatd017804 for ; Mon, 18 Jan 2010 14:43:36 -0500 Received: from sgoldmanlinux.tower-research.com (sgoldmanlinux.tower-research.com [10.0.25.84]) by lithium-a.limegroup.com (8.13.1/8.13.1) with ESMTP id o0IJhad4023176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Jan 2010 14:43:36 -0500 Received: from sgoldmanlinux.tower-research.com (localhost.localdomain [127.0.0.1]) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3) with ESMTP id o0IJhaQT030493 for ; Mon, 18 Jan 2010 14:43:36 -0500 Received: (from sgoldman@localhost) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3/Submit) id o0IJhaLF030491; Mon, 18 Jan 2010 14:43:36 -0500 From: Steve Goldman To: sup-talk In-reply-to: <1263779746-sup-4232@zyrg.net> References: <1263757714-sup-394@sgoldmanlinux.tower-research.com> <1263760574-sup-1333@masanjin.net> <1263763237-sup-3701@sgoldmanlinux.tower-research.com> <1263764041-sup-9982@masanjin.net> <1263771478-sup-431@sgoldmanlinux.tower-research.com> <1263772988-sup-2344@masanjin.net> <1263774467-sup-9664@sgoldmanlinux.tower-research.com> <1263778916-sup-8839@sgoldmanlinux.tower-research.com> <1263779746-sup-4232@zyrg.net> Date: Mon, 18 Jan 2010 14:43:36 -0500 Message-Id: <1263843740-sup-4441@sgoldmanlinux.tower-research.com> User-Agent: Sup/git MIME-Version: 1.0 Content-Disposition: inline X-Scanned-By: MIMEDefang 2.67 on 10.1.1.6 X-Scanned-By: MIMEDefang 2.67 on 10.1.1.4 X-Scanned-By: MIMEDefang 2.67 on 10.1.1.10 Subject: Re: [sup-talk] Problems running sup-convert-ferret-index X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Rich Lane's message of Sun Jan 17 21:10:17 -0500 2010: > Excerpts from Steve Goldman's message of 2010-01-17 20:44:11 -0500: > > Excerpts from Steve Goldman's message of Sun Jan 17 19:28:12 -0500 2010: > > > Excerpts from William Morgan's message of Sun Jan 17 19:04:46 -0500 2010: > > > > Reformatted excerpts from Steve Goldman's message of 2010-01-17: > > > > > ... until it exited thirty minutes later with seg fault. > > > > > > > > > > Anyone else see this? Any way to debug it? > > > > > > > > Is it possible it's running out of memory? > > > > > > Possible. I have 4GB and about 60k messages in my index. So it's not > > > too likely. I'll run it again and watch the usage. > > > > I ran it in strace. It hung on a call to munmap, and then crashed > > with a lot of a bunch of system call timeout warnings. > > > > So it has something to do with memory. > > > > Would the ruby debugger help narrow it down? Does the ruby debugger > > exist? > > Try compiling Xapian from source with --enable-assertions. It would also > be useful to get a core dump (ulimit -c unlimited). This feels like a wild goose chase. Can I start a xapian index from scratch? Any downside to this besides the time sink? Thanks. -- Steve Goldman sgoldman@tower-research.com T: 212.219.6014 F: 212.219.6007 Tower Research Capital, LLC 377 Broadway, 11th Fl. New York, NY 10013 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk