Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 15226 invoked from network); 2 Jan 2009 21:36:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jan 2009 21:36:15 -0000 Received: (qmail 99495 invoked by uid 500); 2 Jan 2009 21:36:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 99450 invoked by uid 500); 2 Jan 2009 21:36:15 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 99439 invoked by uid 99); 2 Jan 2009 21:36:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jan 2009 13:36:15 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com designates 74.125.92.27 as permitted sender) Received: from [74.125.92.27] (HELO qw-out-2122.google.com) (74.125.92.27) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jan 2009 21:36:05 +0000 Received: by qw-out-2122.google.com with SMTP id 5so21347285qwi.29 for ; Fri, 02 Jan 2009 13:35:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tg52XxX8toj4gs1MeuJGhP4GL7D7VFiSdNpG3LMg1SQ=; b=jHtrgz5jEcRmsYVt0tc82J96Vqs8BH//gj5EPeK+jUZcwvS8LFhuv+TE6UWUHzV0GI 501N7GF12xmUOoxU/1WuFnVIoiyMMfsSq0J8KT45Qo2A8ekyh/K3Aj03tzjfr1PgjgEq C0A48nZZgd5eZ2XsY7gCvm0vB+58TR6jCa5AI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=w4B/0SYGOxmvpcC4jv18RkW0Z3BnoZl+zXiLxC9UC9Xt/wB79/SO5/J+J+Kn5TjE0M FH+E3DIy6cBK0xB7EtgKR68cp+KnMmsLRPVSdkQ5q1CHHIpqNFgRcxIETUNfFnzU7hUX +aWrc4ruIr1dwgKVhh0xaaB1EFW1wTziEa9yE= Received: by 10.214.59.16 with SMTP id h16mr15415777qaa.300.1230932144079; Fri, 02 Jan 2009 13:35:44 -0800 (PST) Received: by 10.214.243.21 with HTTP; Fri, 2 Jan 2009 13:35:44 -0800 (PST) Message-ID: Date: Fri, 2 Jan 2009 16:35:44 -0500 From: "Paul Davis" To: dev@couchdb.apache.org Subject: Re: problem with update notification In-Reply-To: <495E6F24.80708@straptank.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <495E6F24.80708@straptank.com> X-Virus-Checked: Checked by ClamAV on apache.org My bad. This was an error in the os_process patch. Trivial patch: Index: src/couchdb/couch_db_update_notifier.erl =================================================================== --- src/couchdb/couch_db_update_notifier.erl (revision 730307) +++ src/couchdb/couch_db_update_notifier.erl (working copy) @@ -37,7 +37,7 @@ couch_event_sup:stop(Pid). init(Exec) when is_list(Exec) -> % an exe - {ok, couch_os_process:start_link(Exec, [], [stream, exit_status, hide])}; + couch_os_process:start_link(Exec, [], [stream, exit_status, hide]); init(Else) -> {ok, Else}. On Fri, Jan 2, 2009 at 2:46 PM, James Arthur wrote: > Hi, > > I'm getting the same issue as this post: > http://n2.nabble.com/Problem-with-update-notification-td1961907.html > > It seems that the move from:: > > DbUpdateNotificationProcess=/my/path/bin/xapian-index > > to:: > > [update_notification] > xapian=/my/path/bin/xapian-index > > Has borked the notifications. I had a working xapian full text indexer, ala > http://couchprojects.googlecode.com/svn/trunk/query_servers/xapian/couchdb-xapian-index > which now throws the error listed on the first link above. I get the same > errors from a simple notification script like > http://dev.timparkin.co.uk/2008/12/couchdb-notification-in-python.html > > Any pointers to get things back up and running would be much appreciated. > > Thanks, > > James. >