You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by James Arthur <th...@straptank.com> on 2009/01/02 20:46:44 UTC

Re: problem with update notification

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.

Re: problem with update notification

Posted by Chris Anderson <jc...@gmail.com>.
committed in r730846, thanks Paul!

On Fri, Jan 2, 2009 at 1:35 PM, Paul Davis <pa...@gmail.com> wrote:
> 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 <th...@straptank.com> 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.
>>
>



-- 
Chris Anderson
http://jchris.mfdz.com

Re: problem with update notification

Posted by Paul Davis <pa...@gmail.com>.
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 <th...@straptank.com> 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.
>