From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs343469ebc; Sun, 17 Jan 2010 15:38:53 -0800 (PST) Received: by 10.224.35.33 with SMTP id n33mr988809qad.259.1263771532381; Sun, 17 Jan 2010 15:38:52 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 5si4739324qwg.18.2010.01.17.15.38.52; Sun, 17 Jan 2010 15:38:52 -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 DF16E15B8033; Sun, 17 Jan 2010 18:38:51 -0500 (EST) Received: from ns2.limegroup.com (ns2.limegroup.com [64.20.166.97]) by rubyforge.org (Postfix) with ESMTP id 8571618582E3 for ; Sun, 17 Jan 2010 18:38:46 -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 o0HNckDS005165 for ; Sun, 17 Jan 2010 18:38:46 -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 o0HNcj0D026769 for ; Sun, 17 Jan 2010 18:38:46 -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 o0HNcj8n012205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Jan 2010 18:38:45 -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 o0HNcj8n008022 for ; Sun, 17 Jan 2010 18:38:45 -0500 Received: (from sgoldman@localhost) by sgoldmanlinux.tower-research.com (8.14.3/8.14.3/Submit) id o0HNcji9008020; Sun, 17 Jan 2010 18:38:45 -0500 From: Steve Goldman To: sup-talk In-reply-to: <1263764041-sup-9982@masanjin.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> Date: Sun, 17 Jan 2010 18:38:45 -0500 Message-Id: <1263771478-sup-431@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 William Morgan's message of Sun Jan 17 16:34:49 -0500 2010: > Reformatted excerpts from Steve Goldman's message of 2010-01-17: > > It went for about ten minutes and appeared to finish with success. > > But something isn't right. When I started sup the index was empty, > > and my xapian directory looks like this: > > Hm, that sure looks empty. Did the sup-sync look like it was working? > If you run the command manually, does that have the same effect? > Is this with git master or next? Ah, yes. sup-sync exited with error. I corrected an incorrect password in my sources.yaml and then it ran... ... until it exited thirty minutes later with seg fault. Anyone else see this? Any way to debug it? 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