It does seem alarming but it isn't. What's happening is an internal process is 
looking for the _users database, and you haven't created it yet. the 2.0 setup 
UI (and the /_setup endpoint) creates this database for you after your cluster 
is connected but you can do it yourself with "curl -X PUT 
localhost:5984/_users'.

B.


> On 16 Oct 2016, at 17:25, John Le Brasseur <johnlebrass...@gmail.com> wrote:
> 
> I am sure this has been covered, but does this make sense to anyone:
> 
> [info] 2016-10-16T16:00:56.272067Z couchdb@localhost <0.7.0> --------
> Application couch_log started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.277619Z couchdb@localhost <0.7.0> --------
> Application folsom started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.340155Z couchdb@localhost <0.7.0> --------
> Application couch_stats started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.340440Z couchdb@localhost <0.7.0> --------
> Application khash started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.350362Z couchdb@localhost <0.7.0> --------
> Application couch_event started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.372625Z couchdb@localhost <0.7.0> --------
> Application ibrowse started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.380792Z couchdb@localhost <0.7.0> --------
> Application ioq started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.381011Z couchdb@localhost <0.7.0> --------
> Application mochiweb started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.381201Z couchdb@localhost <0.7.0> --------
> Application oauth started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.391670Z couchdb@localhost <0.204.0> --------
> Apache CouchDB 2.0.0 is starting.
> 
> [info] 2016-10-16T16:00:56.391918Z couchdb@localhost <0.205.0> --------
> Starting couch_sup
> [info] 2016-10-16T16:00:56.623998Z couchdb@localhost <0.204.0> --------
> Apache CouchDB has started. Time to relax.
> 
> [info] 2016-10-16T16:00:56.624254Z couchdb@localhost <0.204.0> --------
> Apache CouchDB has started on http://127.0.0.1:5986/
> [info] 2016-10-16T16:00:56.624447Z couchdb@localhost <0.7.0> --------
> Application couch started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.624652Z couchdb@localhost <0.7.0> --------
> Application ets_lru started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.633401Z couchdb@localhost <0.7.0> --------
> Application rexi started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.672782Z couchdb@localhost <0.7.0> --------
> Application mem3 started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.673030Z couchdb@localhost <0.7.0> --------
> Application fabric started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.698930Z couchdb@localhost <0.7.0> --------
> Application chttpd started on node couchdb@localhost
> [error] 2016-10-16T16:00:56.721472Z couchdb@localhost emulator --------
> Error in process <0.320.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-16T16:00:56.721693Z couchdb@localhost <0.319.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-16T16:00:56.724709Z couchdb@localhost <0.7.0> --------
> Application couch_index started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.724943Z couchdb@localhost <0.7.0> --------
> Application couch_mrview started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.725147Z couchdb@localhost <0.7.0> --------
> Application couch_plugins started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.762984Z couchdb@localhost <0.7.0> --------
> Application couch_replicator started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.763216Z couchdb@localhost <0.7.0> --------
> Application couch_peruser started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.780470Z couchdb@localhost <0.7.0> --------
> Application ddoc_cache started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.795482Z couchdb@localhost <0.7.0> --------
> Application global_changes started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.796385Z couchdb@localhost <0.7.0> --------
> Application jiffy started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.801313Z couchdb@localhost <0.7.0> --------
> Application mango started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.812070Z couchdb@localhost <0.7.0> --------
> Application setup started on node couchdb@localhost
> [info] 2016-10-16T16:00:56.813400Z couchdb@localhost <0.7.0> --------
> Application snappy started on node couchdb@localhost
> [error] 2016-10-16T16:01:01.722265Z couchdb@localhost emulator --------
> Error in process <0.446.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-16T16:01:01.722526Z couchdb@localhost <0.319.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)
> 
> Couchdb does start and gets to a point and something goes wrong.
> 
> I'm so uneducated as far as Linux/Unix is concerned so it's going to be an
> obvious error.
> 
> Many thanks.
> 
> John Le Brasseur

Reply via email to