Couchdb 2.0 installation issue - missing _users

[Karl Helmer]

Hi,

I'm installing CouchDB 2.0 on a Lubuntu 14.04 machine. When I start up
CouchDB using:

>sudo -i -u couchdb couchdb/bin/couchdb
as in the installation wiki I get the following error:

[info] 2016-10-06T19:23:53.759016Z couchdb@localhost <0.7.0> --------
Application couch_log started on node couchdb@localhost
[info] 2016-10-06T19:23:53.831092Z couchdb@localhost <0.7.0> --------
Application folsom started on node couchdb@localhost
[info] 2016-10-06T19:23:54.229325Z couchdb@localhost <0.7.0> --------
Application couch_stats started on node couchdb@localhost
[info] 2016-10-06T19:23:54.230105Z couchdb@localhost <0.7.0> --------
Application khash started on node couchdb@localhost
[info] 2016-10-06T19:23:54.344321Z couchdb@localhost <0.7.0> --------
Application couch_event started on node couchdb@localhost
[info] 2016-10-06T19:23:54.418931Z couchdb@localhost <0.7.0> --------
Application ibrowse started on node couchdb@localhost
[info] 2016-10-06T19:23:54.498700Z couchdb@localhost <0.7.0> --------
Application ioq started on node couchdb@localhost
[info] 2016-10-06T19:23:54.499451Z couchdb@localhost <0.7.0> --------
Application mochiweb started on node couchdb@localhost
[info] 2016-10-06T19:23:54.500156Z couchdb@localhost <0.7.0> --------
Application oauth started on node couchdb@localhost
[info] 2016-10-06T19:23:54.594987Z couchdb@localhost <0.207.0> --------
Apache CouchDB 2.0.0 is starting.

[info] 2016-10-06T19:23:54.595671Z couchdb@localhost <0.208.0> --------
Starting couch_sup
[notice] 2016-10-06T19:23:54.955006Z couchdb@localhost <0.92.0> --------
config: [couchdb] uuid set to <blah> for reason nil
[info] 2016-10-06T19:23:55.409606Z couchdb@localhost <0.213.0> --------
open_result error {not_found,no_db_file} for _users
[info] 2016-10-06T19:23:56.187778Z couchdb@localhost <0.207.0> --------
Apache CouchDB has started. Time to relax.


which looks good except for the "not_found" error for _users. Then things
continue and end with continual bouncing back and forth between a notice
and an error (see at the very bottom).


[info] 2016-10-06T19:23:56.188416Z couchdb@localhost <0.207.0> --------
Apache CouchDB has started on http://127.0.0.1:5986/
[info] 2016-10-06T19:23:56.189180Z couchdb@localhost <0.7.0> --------
Application couch started on node couchdb@localhost
[info] 2016-10-06T19:23:56.189864Z couchdb@localhost <0.7.0> --------
Application ets_lru started on node couchdb@localhost
[info] 2016-10-06T19:23:56.305984Z couchdb@localhost <0.7.0> --------
Application rexi started on node couchdb@localhost
[info] 2016-10-06T19:23:56.385948Z couchdb@localhost <0.213.0> --------
open_result error {not_found,no_db_file} for _nodes
[info] 2016-10-06T19:23:56.717963Z couchdb@localhost <0.213.0> --------
open_result error {not_found,no_db_file} for _dbs
[error] 2016-10-06T19:23:56.719286Z couchdb@localhost emulator --------
Error in process <0.295.0> on node 'couchdb@localhost' with exit value:
{{badmatch,file_exists},[{mem3_shards,fold,2,[{file,"src/mem3_shards.erl"},{line,156}]},{mem3_sync,initial_sync,1,[{file,"src/mem3_sync.erl"},{line,241}]}]}
[info] 2016-10-06T19:23:56.794057Z couchdb@localhost <0.7.0> --------
Application mem3 started on node couchdb@localhost
[info] 2016-10-06T19:23:56.794324Z couchdb@localhost <0.7.0> --------
Application fabric started on node couchdb@localhost
[info] 2016-10-06T19:23:56.973065Z couchdb@localhost <0.7.0> --------
Application chttpd started on node couchdb@localhost
[error] 2016-10-06T19:23:57.039445Z couchdb@localhost emulator --------
Error in process <0.334.0> on node 'couchdb@localhost' with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
[notice] 2016-10-06T19:23:57.040488Z couchdb@localhost <0.333.0> --------
chttpd_auth_cache changes listener died database_does_not_exist at
mem3_shards:load_shards_from_db/6(line:327) <=
mem3_shards:load_shards_from_disk/1(line:315) <=
mem3_shards:load_shards_from_disk/2(line:331) <=
mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
chttpd_auth_cache:listen_for_changes/1(line:134)
[info] 2016-10-06T19:23:57.079393Z couchdb@localhost <0.7.0> --------
Application couch_index started on node couchdb@localhost
[info] 2016-10-06T19:23:57.079773Z couchdb@localhost <0.7.0> --------
Application couch_mrview started on node couchdb@localhost
[info] 2016-10-06T19:23:57.079930Z couchdb@localhost <0.7.0> --------
Application couch_plugins started on node couchdb@localhost
[info] 2016-10-06T19:23:57.156246Z couchdb@localhost <0.213.0> --------
open_result error {not_found,no_db_file} for _replicator
[notice] 2016-10-06T19:23:57.270166Z couchdb@localhost <0.368.0> --------
creating replicator ddoc
[info] 2016-10-06T19:23:57.410734Z couchdb@localhost <0.7.0> --------
Application couch_replicator started on node couchdb@localhost
[info] 2016-10-06T19:23:57.410932Z couchdb@localhost <0.7.0> --------
Application couch_peruser started on node couchdb@localhost
[info] 2016-10-06T19:23:57.460988Z couchdb@localhost <0.7.0> --------
Application ddoc_cache started on node couchdb@localhost
[info] 2016-10-06T19:23:57.611355Z couchdb@localhost <0.7.0> --------
Application global_changes started on node couchdb@localhost
[info] 2016-10-06T19:23:57.611607Z couchdb@localhost <0.7.0> --------
Application jiffy started on node couchdb@localhost
[info] 2016-10-06T19:23:57.657742Z couchdb@localhost <0.7.0> --------
Application mango started on node couchdb@localhost
[info] 2016-10-06T19:23:57.730338Z couchdb@localhost <0.7.0> --------
Application setup started on node couchdb@localhost
[info] 2016-10-06T19:23:57.730781Z couchdb@localhost <0.7.0> --------
Application snappy started on node couchdb@localhost
[error] 2016-10-06T19:24:02.041860Z couchdb@localhost emulator --------
Error in process <0.476.0> on node 'couchdb@localhost' with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
[notice] 2016-10-06T19:24:02.041947Z couchdb@localhost <0.333.0> --------
chttpd_auth_cache changes listener died database_does_not_exist at
mem3_shards:load_shards_from_db/6(line:327) <=
mem3_shards:load_shards_from_disk/1(line:315) <=
mem3_shards:load_shards_from_disk/2(line:331) <=
mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
chttpd_auth_cache:listen_for_changes/1(line:134)
[error] 2016-10-06T19:24:07.044149Z couchdb@localhost emulator --------
Error in process <0.557.0> on node 'couchdb@localhost' with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
[notice] 2016-10-06T19:24:07.044249Z couchdb@localhost <0.333.0> --------
chttpd_auth_cache changes listener died database_does_not_exist at
mem3_shards:load_shards_from_db/6(line:327) <=
mem3_shards:load_shards_from_disk/1(line:315) <=
mem3_shards:load_shards_from_disk/2(line:331) <=
mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
chttpd_auth_cache:listen_for_changes/1(line:134)
[error] 2016-10-06T19:24:12.046115Z couchdb@localhost emulator --------
Error in process <0.638.0> on node 'couchdb@localhost' with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
[notice] 2016-10-06T19:24:12.046250Z couchdb@localhost <0.333.0> --------
chttpd_auth_cache changes listener died database_does_not_exist at
mem3_shards:load_shards_from_db/6(line:327) <=
mem3_shards:load_shards_from_disk/1(line:315) <=
mem3_shards:load_shards_from_disk/2(line:331) <=
mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
chttpd_auth_cache:listen_for_changes/1(line:134)
[error] 2016-10-06T19:24:17.048005Z couchdb@localhost emulator --------
Error in process <0.719.0> on node 'couchdb@localhost' with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...


Clearly the lack of _users is causing problems, but any ideas as to what
would cause _users not to be there? Is this an issue with the couchdb
user?

thanks,
Karl




--
Karl Helmer, PhD
Athinoula A Martinos Center
for Biomedical Imaging Massachusetts General Hospital
149 - 13th St Room 2301
Charlestown, MA 02129
(p) 617.726.8636
(f) 617.726.7422
hel...@nmr.mgh.harvard.edu





The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Garren Smith]

Hi Karl,

You need to setup the cluster it will then create the required databases
for you.

On Thursday, 06 October 2016, Karl Helmer <hel...@nmr.mgh.harvard.edu>
wrote:

> shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
> [notice] 2016-10-06T19:24:02.041947Z couchdb@localhost <0.333.0> --------
> chttpd_auth_cache changes listener died database_does_not_exist at
> mem3_shards:load_shards_from_db/6(line:327) <=
> mem3_shards:load_shards_from_disk/1(line:315) <=
> mem3_shards:load_shards_from_disk/2(line:331) <=
> mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
> chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
> chttpd_auth_cache:listen_for_changes/1(line:134)
> [error] 2016-10-06T19:24:07.044149Z couchdb@localhost emulator --------
> Error in process <0.557.0> on node 'couchdb@localhost' with exit value:
> {database_does_not_exist,[{mem3_shards,load_shards_from_

> db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{
> mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_

> shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
> [notice] 2016-10-06T19:24:07.044249Z couchdb@localhost <0.333.0> --------
> chttpd_auth_cache changes listener died database_does_not_exist at
> mem3_shards:load_shards_from_db/6(line:327) <=
> mem3_shards:load_shards_from_disk/1(line:315) <=
> mem3_shards:load_shards_from_disk/2(line:331) <=
> mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
> chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
> chttpd_auth_cache:listen_for_changes/1(line:134)
> [error] 2016-10-06T19:24:12.046115Z couchdb@localhost emulator --------
> Error in process <0.638.0> on node 'couchdb@localhost' with exit value:
> {database_does_not_exist,[{mem3_shards,load_shards_from_

> db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{
> mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_

> shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
> [notice] 2016-10-06T19:24:12.046250Z couchdb@localhost <0.333.0> --------
> chttpd_auth_cache changes listener died database_does_not_exist at
> mem3_shards:load_shards_from_db/6(line:327) <=
> mem3_shards:load_shards_from_disk/1(line:315) <=
> mem3_shards:load_shards_from_disk/2(line:331) <=
> mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <=
> chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <=
> chttpd_auth_cache:listen_for_changes/1(line:134)
> [error] 2016-10-06T19:24:17.048005Z couchdb@localhost emulator --------
> Error in process <0.719.0> on node 'couchdb@localhost' with exit value:
> {database_does_not_exist,[{mem3_shards,load_shards_from_

> db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{
> mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_

> shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
>
>
> Clearly the lack of _users is causing problems, but any ideas as to what
> would cause _users not to be there? Is this an issue with the couchdb
> user?
>
> thanks,
> Karl
>
>
>
>
> --
> Karl Helmer, PhD
> Athinoula A Martinos Center
> for Biomedical Imaging Massachusetts General Hospital
> 149 - 13th St Room 2301
> Charlestown, MA 02129
> (p) 617.726.8636
> (f) 617.726.7422

> hel...@nmr.mgh.harvard.edu <javascript:;>

[Bogdan Andu]

u need to do these:

curl -X PUT http://10.10.13.104:5984/_users

curl -X PUT http://10.10.13.104:5984/_replicator

curl -X PUT http://10.10.13.104:5984/_global_changes

/Bogdan

[Karl Helmer]

Thanks. I found the wiki 2.6 page with the instructions for the
single-node setup.

One thing I don't get is that the installation instructions say "After
installation and initial startup, visit Fauxton at
http://127.0.0.01:5984/_utils#setup. You will be asked to set up CouchDB
as a single-node instance or set up a cluster."
and then
"When you run 2.0 as a single node, it doesn’t create system databases on
startup. You have to do this manually
curl -X PUT http://127.0.0.1:5984/_users
curl -X PUT http://127.0.0.1:5984/_replicator
curl -X PUT http://127.0.0.1:5984/_global_changes:
"

Does the setup create those databases or do I have to do it by hand? I
can't seem to do it by hand without doing the setup, because I get a
{
"error":"method_not_allowed",
"reason":"Only GET,HEAD allowed"
}
error that is mentioned here:
http://couchdb-13.readthedocs.io/en/latest/api-basics/
if I try.

But I also can't navigate to http://127.0.0.01:5984/_utils#setup
successfully. I have stopped my 1.6.1 instance, but not uninstalled it. If
I navigate to http://127.0.0.01:5984/_utils#setup , I get my old futon
dashboard. I was hoping to be able to keep the old and new versions on
the same computer for testing. Is this not possible/advisable? Is there
a way to get the above IP address to point to Fauxton and do the node
setup?

thanks,
Karl


Karl

[Jan Lehnardt]

Best to give the old version a new port, like 15984, then start both and
proceed with http://127.0.0.01:5984/_utils#setup to setup the cluster.

Best
Jan
--

--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

[Karl Helmer]

Thanks, Jan.

To make sure I'm doing this right:
1) shut down couchdb 1.6.1:
>sudo couchdb -d
2) go to /etc/couchdb and change the port to 15984
3) restart 1.6.1
>sudo couchdb -b
4) open up a web browser and navigate to 127.0.0.1:15984/_utils

This works and I see my existing db's and see "Futon on Apache CouchDB
1.6.1" at the bottom RHS.


5) Start up 2.0

>sudo -i -u couchdb couchdb/bin/couchdb

The output is below, but there are two things - first is that the port
that it starts CouchDB on is 5986. If I try to use
127.0.0.1:5986/_utils#setup I get an "unable to connect" error.
2nd thing is of course the eaddrinuse at gen_server error. Any idea what
that address is?

thanks,
Karl


[info] 2016-10-07T19:12:53.299321Z couchdb@localhost <0.7.0> --------

Application couch_log started on node couchdb@localhost

[info] 2016-10-07T19:12:53.346217Z couchdb@localhost <0.7.0> --------

Application folsom started on node couchdb@localhost

[info] 2016-10-07T19:12:53.733463Z couchdb@localhost <0.7.0> --------

Application couch_stats started on node couchdb@localhost

[info] 2016-10-07T19:12:53.734501Z couchdb@localhost <0.7.0> --------

Application khash started on node couchdb@localhost

[info] 2016-10-07T19:12:53.826730Z couchdb@localhost <0.7.0> --------

Application couch_event started on node couchdb@localhost

[info] 2016-10-07T19:12:53.883363Z couchdb@localhost <0.7.0> --------

Application ibrowse started on node couchdb@localhost

[info] 2016-10-07T19:12:53.943737Z couchdb@localhost <0.7.0> --------

Application ioq started on node couchdb@localhost

[info] 2016-10-07T19:12:53.944473Z couchdb@localhost <0.7.0> --------

Application mochiweb started on node couchdb@localhost

[info] 2016-10-07T19:12:53.945170Z couchdb@localhost <0.7.0> --------

Application oauth started on node couchdb@localhost

[info] 2016-10-07T19:12:54.032220Z couchdb@localhost <0.207.0> --------

Apache CouchDB 2.0.0 is starting.

[info] 2016-10-07T19:12:54.032898Z couchdb@localhost <0.208.0> --------
Starting couch_sup
[info] 2016-10-07T19:12:54.861568Z couchdb@localhost <0.207.0> --------

Apache CouchDB has started. Time to relax.

[info] 2016-10-07T19:12:54.862168Z couchdb@localhost <0.207.0> --------

Apache CouchDB has started on http://127.0.0.1:5986/

[info] 2016-10-07T19:12:54.862811Z couchdb@localhost <0.7.0> --------

Application couch started on node couchdb@localhost

[info] 2016-10-07T19:12:54.863485Z couchdb@localhost <0.7.0> --------

Application ets_lru started on node couchdb@localhost

[info] 2016-10-07T19:12:54.931349Z couchdb@localhost <0.7.0> --------

Application rexi started on node couchdb@localhost

[info] 2016-10-07T19:12:55.117916Z couchdb@localhost <0.7.0> --------

Application mem3 started on node couchdb@localhost

[info] 2016-10-07T19:12:55.118646Z couchdb@localhost <0.7.0> --------

Application fabric started on node couchdb@localhost

Failure to start Mochiweb: eaddrinuse
[error] 2016-10-07T19:12:55.194840Z couchdb@localhost <0.305.0> --------
CRASH REPORT Process (<0.305.0>) with 0 neighbors exited with reason:
eaddrinuse at gen_server:init_it/6(line:320) <=
proc_lib:init_p_do_apply/3(line:239); initial_call:
{mochiweb_socket_server,init,['Argument__1']}, ancestors:
[chttpd_sup,<0.302.0>], messages: [], links: [<0.303.0>], dictionary: [],
trap_exit: true, status: running, heap_size: 376, stack_size: 27,
reductions: 548
[error] 2016-10-07T19:12:55.195189Z couchdb@localhost <0.303.0> --------
Supervisor chttpd_sup had child chttpd started with chttpd:start_link() at
undefined exit with reason eaddrinuse in context start_error
[error] 2016-10-07T19:12:55.195862Z couchdb@localhost <0.301.0> --------
CRASH REPORT Process (<0.301.0>) with 0 neighbors exited with reason:
{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
at application_master:init/4(line:133) <=
proc_lib:init_p_do_apply/3(line:239); initial_call:
{application_master,init,['Argument__1','Argument__2',...]}, ancestors:
[<0.300.0>], messages: [{'EXIT',<0.302.0>,normal}], links:
[<0.300.0>,<0.7.0>], dictionary: [], trap_exit: true, status: running,
heap_size: 376, stack_size: 27, reductions: 109
[info] 2016-10-07T19:12:55.196426Z couchdb@localhost <0.7.0> --------
Application chttpd exited with reason:
{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
{"Kernel pid
terminated",application_controller,"{application_start_failure,chttpd,{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}}"}

Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller)
({application_start_failure,chttpd,{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}})

[Jan Lehnardt]

The url is http://127.0.0.1:5984/_utils#setup not 5986

Cheers
Jan
--

[Karl Helmer]

Yes, but in the error report that I pasted below the message said that it
was starting up CouchDB on 5986. I see why in the init files though. I'm
able to change the port as you suggested and 1.6.1 connects to futon on
that new port, but it continues to start 1.6.1 on port 5984 as well. I
think my only choice here is to delete both, install 2.0 using port 5984
and then install 1.6.1 back using another port. I'm not sure what else to
do unless there is somewhere else that is pointing 1.6.1 to 5984 that I
don't know about.

thanks,
Karl

[Joan Touzet]

Use the default ports CouchDB 2.0 comes with. It will start services on
both port 5984 and 5986. You don't want to change either if you can avoid
it. Agree that starting 1.6.1 on a different port makes the most sense.

-Joan

> >>>> "When you run 2.0 as a single node, it doesn’t create system

[Jan Lehnardt]

> On 11 Oct 2016, at 03:56, Karl Helmer <hel...@nmr.mgh.harvard.edu> wrote:
>
> Yes, but in the error report that I pasted below the message said that it
> was starting up CouchDB on 5986. I see why in the init files though. I'm
> able to change the port as you suggested and 1.6.1 connects to futon on
> that new port, but it continues to start 1.6.1 on port 5984 as well. I
> think my only choice here is to delete both, install 2.0 using port 5984
> and then install 1.6.1 back using another port. I'm not sure what else to
> do unless there is somewhere else that is pointing 1.6.1 to 5984 that I
> don't know about.

CouchDB 1.6.1 can be rebound to a new port at runtime, there is no need
to reinstall anything. If you change the port in Futon, everything is instant.
If you change it in the 1.6.1 ini file, you need to restart CouchDB.

2.0 should behave the same. On top, 2.0 starts on ports 5984 and 5986, and
it only reports 5986 in the logs, and that’s confusing, but ignore this
for the moment.

Best
Jan
--


>
> thanks,
> Karl
>
>

>>>>> "When you run 2.0 as a single node, it doesn’t create system