Looks like you skipped over the "setup cluster" step from the installation
notes on docs.couchdb.org. Even a single/node cluster-of-one needs this, as it
creates the necessary system databases.
At this point, best to ignore the 5986 port (unless for per-node maintenance).
> On 12 Oct 2016, at 20:44, Timothy McKernan <timbitsandby...@gmail.com> wrote:
> I've installed CouchDB 2.0.0 from source using:
> make release
> sudo mv rel/couchdb /var/lib/couchdb
> sudo chown -R couchdb:couchdb /var/lib/couchdb
> sudo -u couchdb /var/lib/couchdb/bin/couchdb
> The problem I'm seeing is that, by default, [chttpd] is being assigned port
> 5984 (in the default.ini) and [httpd] is assigned 5986.
> Throughout the online docs port 5984 is referenced for the majority of
> endpoints, such as fauxton.
> Used for pretty much everything, such as couchapps (fauxton is the new
> futon) and db access.
> And port 5986 is the "back-door" port.
> So we end up with the following behavior:
> md-007:~ $ curl -k -X GET http://127.0.0.1:5984/_all_dbs
> md-007:~ $ curl -k -X GET http://127.0.0.1:5986/_all_dbs
> md-007:~ $ curl -k -X GET https://127.0.0.1:6984/_all_dbs
> It seems that chttpd doesn't have the usual default access to everything
> that it used to in couchdb 1.6. Indeed, if you use fauxton over port 5984
> as the docs say to, it _doesn't_ show you any db's, because it clearly
> (from the above curl examples) can't see any. And the emulator complains
> because it's using 5984 to try and find _users.
> [error] 2016-10-12T18:42:53.106630Z couchdb@localhost emulator --------
> Error in process <0.4185.0> on node couchdb@localhost with exit value:
> What's the correct configuration here? What ports should chttpd and httpd
> be set to so that the emulator process isn't erroring?