incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Iñigo Sola Núñez <inigo.s...@gmail.com>
Subject Re: CouchDB view does not finish
Date Wed, 30 Nov 2011 11:03:27 GMT
I fix it installing couchdb again using the following script:

https://raw.github.com/gist/1171217/605dee397799da48ed1c5f13878afceedfa6738e/couchdb-ec2-install.sh

Thanks

2011/11/29 Iñigo Sola Núñez <inigo.sola@gmail.com>

> I tried in other computer and works. But in the server is not work. So, It
> is not a sintax error.
>
>
> 2011/11/29 James Marca <jmarca@translab.its.uci.edu>
>
>> On Tue, Nov 29, 2011 at 10:53:37AM +0000, Iñigo Sola Núñez wrote:
>> > 2011/11/29 Nils Breunese <N.Breunese@vpro.nl>
>> >
>> > > Iñigo Sola Núñez wrote:
>> > >
>> > > > My documents are smalls (just 6 string fields or something like
>> that,
>> > > and I
>> > > > have 130 documents in database).
>> > > > I don't know how I can see/_utils/status.html because I don't use
>> Futon,
>> > > I
>> > > > just use REST to manage my database.
>> > >
>> > > The status page just queries /_active_tasks, so you can also do that
>> > > directly yourself: http://wiki.apache.org/couchdb/HttpGetActiveTasks
>> > >
>> > > > I am using in Amazon EC2. And I don't know where are the logs
>> files. I'm
>> > > so sorry.
>> > >
>> > > You should also be able to access the log at /_log:
>> > > http://wiki.apache.org/couchdb/HttpGetLog
>> > >
>> > >
>> > Active task:
>> >
>> [{"pid":"<0.8222.1>","changes_done":0,"database":"mydatabase","design_document":"_design/myview","progress":0,"started_on":1322561328,"total_changes":116,"type":"indexer","updated_on":1322561328}]
>> >
>> > My log:
>> >
>> > [Tue, 29 Nov 2011 10:48:25 GMT] [error] [<0.8222.1>] OS Process Error
>> > <0.13654.2> :: {os_process_error,
>> >                                                       {exit_status,127}}
>>
>> When I see this sort of behavior, it usually means my javascript has a
>> syntax error
>> or a bug somewhere.
>>
>> Sometimes it helps to try running the view on a known bit of data, say
>> using node on your desktop.  Or if the error is really basic, I find
>> running   "node myview.js" will catch those.
>>
>> regards,
>> James
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message