Hi,

Thank you for your prompt reply !

>That may not be ok, but cannot say for sure as Verify Install page was
>recently seriously improved.

How can I obtain the latest version ?

I have build couchdb-2.0 from the latest code of the developer-preview-2.0,
however
improvements would not be found.

Cheers,
Makoto


2015-05-15 7:53 GMT+09:00 Alexander Shorin <[email protected]>:

> Hi,
>
> Thanks for testing! Replied inline.
>
> On Fri, May 15, 2015 at 12:55 AM, Makoto Hashimoto
> <[email protected]> wrote:
> > I am testing couchdb 2.0. However I encountered some errors.
> >
> > 1. When I started couchdb using 'dev/run', there is an error message like
> > this.
> >
> > $ dev/run
> > [ * ] Setup environment ... ok
> > [ * ] Ensure CouchDB is built ... ok
> > [ * ] Prepare configuration files ... ok
> > [ * ] Start node node1 ... ok
> > [ * ] Start node node2 ... ok
> > [ * ] Start node node3 ... ok
> > [ * ] Check node at http://127.0.0.1:15984/ ... failed: [Errno socket
> > error] [Errno 111] Connection refused
> > [ * ] Check node at http://127.0.0.1:25984/ ... ok
> > [ * ] Check node at http://127.0.0.1:35984/ ... ok
> > [ * ] Check node at http://127.0.0.1:15984/ ... ok
> > [ * ] Running cluster setup ... ok
> > [ * ] Developers cluster is set up at http://127.0.0.1:15984.
> >
> > My environment is correct ?
>
> Yes. Those error is ok as you may see finally node check had passed.
>
> > I found some errors in the log/crash.log there are message.
> >
> > 2015-05-15 06:05:47 =SUPERVISOR REPORT====
> >      Supervisor: {local,couch_secondary_services}
> >      Context:    child_terminated
> >      Reason:     normal
> >      Offender:
> >
> [{pid,<0.231.0>},{name,httpd},{mfargs,{couch_httpd,start_link,[]}},{restart_type,permanent},{shutdown,brutal_kill},{child_type,worker}]
> >
> > 2015-05-15 06:05:47 =SUPERVISOR REPORT====
> >      Supervisor: {local,couch_secondary_services}
> >      Context:    child_terminated
> >      Reason:     normal
> >      Offender:
> >
> [{pid,<0.239.0>},{name,httpd},{mfargs,{couch_httpd,start_link,[]}},{restart_type,permanent},{shutdown,brutal_kill},{child_type,worker}]
> >
> > 2015-05-15 06:05:47 =SUPERVISOR REPORT====
> >      Supervisor: {local,couch_secondary_services}
> >      Context:    child_terminated
> >      Reason:     normal
> >      Offender:
> >
> [{pid,<0.232.0>},{name,httpd},{mfargs,{couch_httpd,start_link,[]}},{restart_type,permanent},{shutdown,brutal_kill},{child_type,worker}]
> >
>
> These are regular supervisor reports. It's ok while everything keeps
> working.
>
> > 2. 'Database does not exist' error.
> >
> > After starting couchdb, I encountered a 'Database does not exist' error
> > when I clicked "Config" menu and
> > "Change Password" menu.
> >
> > There was a 404 error in the dev/logs/node01.log.
> >
> > 2015-05-15 06:51:27.300 [debug] [email protected] <0.2854.0> cache hit for
> > root
> > 2015-05-15 06:51:27.300 [debug] [email protected] <0.2854.0> timeout 600
> > 2015-05-15 06:51:27.300 [debug] [email protected] <0.2854.0> Successful
> > cookie auth as: "root"
> > 2015-05-15 06:51:27.300 [debug] [email protected] <0.2854.0> httpd 404
> error
> > response:
> >  {"error":"not_found","reason":"Database does not exist."}
> >
> > 2015-05-15 06:51:27.300 [notice] [email protected] <0.2854.0> dbd78145
> > 127.0.0.1 127.0.0.1:15984 GET /_config 404 ok 1
>
> /_config endpoint is not available on Cluster interface. AFAIK, in
> recent Fauxton commits Config menu item was removed as well to not
> cause a confusion. So that's ok.
>
> > 3. Verify CouchDB Installation failed
> >
> > I tested the "Verify CouchDB", but it failed at Create View as follows:
> >
> > The request could not be processed in a reasonable amount time.
> >
> >
> > I hope someone would find solutions.
>
> That may not be ok, but cannot say for sure as Verify Install page was
> recently seriously improved.
>
> --
> ,,,^..^,,,
>

Reply via email to