couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: CouchDB 2.0 Command Line Options
Date Tue, 18 Oct 2016 15:33:31 GMT

I work with Maggie, and had a follow up question about running multiple instances of couchdb
using one binaries directory.  When setting up a cluster, I understand I need to set the identity
of each node in vm.args.  I tried the following to have couchdb look in a different location
for the vm.args file:

	export ERL_FLAGS="-couch_ini /myinstance1/default.ini /myinstance1/local.ini -args_file /myinstance1/vm.args"

However, the couchdb log shows the node identity as: nonode@nohost

Then I tried specifying -name in ERL_FLAGS:

	export ERL_FLAGS="-couch_ini /myinstance1/default.ini /myinstance1/local.ini -name myinstance1@hostname1.domain"

And I still get: nonode@nohost

Finally, I tried specifying -sname in ERL_FLAGS, and this seems to work, but gives a shortname:

	export ERL_FLAGS="-couch_ini /myinstance1/default.ini /myinstance1/local.ini -sname myinstance1"

And now I get: myinstance1@hostname1.  Is there any way I can either point couchdb at my instance's
vm.args file, or I can specify the fully qualified -name option correctly?

Thanks for your help!

-----Original Message-----
From: Jiang, Maggie 
Sent: Thursday, October 06, 2016 5:27 PM
Subject: RE: CouchDB 2.0 Command Line Options

Thanks Adam and Jan. We were able to have a few instances running with the workaround.

-----Original Message-----
From: Adam Kocoloski [] 
Sent: Thursday, October 06, 2016 12:47 PM
Subject: Re: CouchDB 2.0 Command Line Options

Thanks Jan, that was a bit cleaner than I realized. It’s a decent workaround. Important
to note that every file you want to be consulted needs to be listed there — the couch_ini
flag will override the default search space entirely.


> On Oct 6, 2016, at 11:48 AM, Jan Lehnardt <> wrote:
> try
> export ERL_FLAGS=“-couch_ini /path/to/default.ini /path/to/local_one.ini”
> ./bin/couchdb
> Analogous with local_two.ini etc.
> Best
> Jan
> --
>> On 06 Oct 2016, at 17:41, wrote:
>> Hi Adam,
>> Thanks for replying! I need to point it to another location. We plan to have a few
instances of CouchDB for different purposes on our dev servers and would like to use the same
binaries to start it up (but pointing to different local.ini files on start up). Without the
-a option, I'd have to build CouchDB 2.0 3 times (for example) in order to be able to start
up 3 instances of it on a dev server.
>> Maggie
>> -----Original Message-----
>> From: Adam Kocoloski [] 
>> Sent: Thursday, October 06, 2016 11:10 AM
>> To:
>> Subject: Re: CouchDB 2.0 Command Line Options
>> Hi Maggie,
>> You’re right, the “-a” switch is ignored in 2.0. That’s a miss on our part.
I filed
. You can still drop files in the local.d directory and they should take precedence over any
files in default.* as well as local.ini.
>> There are other undocumented ways to customize the list of configuration files that
are consulted using flags in the vm.args file (and probably using some environment variables
as well),, but I wouldn’t really recommend going there. Does the local.d option work for
you or do you need to point to another location?
>> Adam
>>> On Oct 5, 2016, at 10:20 AM, wrote:
>>> Hi,
>>> I'm looking to point to a different local.ini than the one located in the CouchDB
2.0 etc folder. Is there a way to specify this when starting up CouchDB or is there another
way?  Looking at the docs, it seems like we should still be using the "-a" option but after
looking at the startup scripts in the bin folder there is no code there to accept the "-a"
switch anymore.
>>> Thanks,
>>> Maggie
> -- 
> Professional Support for Apache CouchDB:


View raw message