Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6270E200BA6 for ; Tue, 18 Oct 2016 18:49:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 60E22160AE5; Tue, 18 Oct 2016 16:49:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7FC29160ACE for ; Tue, 18 Oct 2016 18:49:37 +0200 (CEST) Received: (qmail 74156 invoked by uid 500); 18 Oct 2016 16:49:31 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 74143 invoked by uid 99); 18 Oct 2016 16:49:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2016 16:49:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F2DD0C0EBA for ; Tue, 18 Oct 2016 16:49:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.72 X-Spam-Level: X-Spam-Status: No, score=-0.72 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=messagingengine.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id m_FdLGuIOoia for ; Tue, 18 Oct 2016 16:49:27 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 95DCC5F257 for ; Tue, 18 Oct 2016 16:49:26 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E75C22067A for ; Tue, 18 Oct 2016 12:49:25 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 18 Oct 2016 12:49:25 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Z4K79LwMDXkov2a y4mj5t/XncJg=; b=PfuEbTYLWbXNWqRpFWMcCNufl4a8fAP/R2n47Hn/erM5IxG JOTHhNhuGmzLOjVLkdTZMtMTxFrXwUpo6gK2HA+0yyu1i5uq15JG1suW8ApmEcj+ V3hSglxBvFM3aRKGBlINjyDSVjn+NAMKjJ14Trr9gbTujxcnSl5TIRwX38Rs= X-Sasl-enc: 8fKtoO+vJDm5Rc0PrP2ne8CVdKJ4EptPP4aW7PaWzfBR 1476809365 Received: from kocolosk.cambridge.ibm.com (unknown [129.42.208.174]) by mail.messagingengine.com (Postfix) with ESMTPA id 9F972CC0B7 for ; Tue, 18 Oct 2016 12:49:25 -0400 (EDT) From: Adam Kocoloski Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\)) Subject: Re: CouchDB 2.0 Command Line Options Date: Tue, 18 Oct 2016 12:49:24 -0400 References: <5CD5BE3D2C4DF14B90B0B9727368F504DE9A9E@PRDCTWPEMLMB21.prod-am.ameritrade.com> <5CD5BE3D2C4DF14B90B0B9727368F504DEA979@PRDCTWPEMLMB21.prod-am.ameritrade.com> <6022D905-8B57-4360-8AEF-C0285A2186A1@apache.org> <5CD5BE3D2C4DF14B90B0B9727368F504DEAAEE@PRDCTWPEMLMB21.prod-am.ameritrade.com> <5CD5BE3D2C4DF14B90B0B9727368F504DED979@PRDCTWPEMLMB21.prod-am.ameritrade.com> <48ABBE93645D284FA23C3D57EC55225BA8CB1E@PRDCTWPEMLMB21.prod-am.ameritrade.com> To: user@couchdb.apache.org In-Reply-To: <48ABBE93645D284FA23C3D57EC55225BA8CB1E@PRDCTWPEMLMB21.prod-am.ameritrade.com> Message-Id: X-Mailer: Apple Mail (2.3226) archived-at: Tue, 18 Oct 2016 16:49:38 -0000 Hi Melvin, I have a theory here. Did the original $ROOTDIR/etc/vm.args = file still contain a =E2=80=9C-name=E2=80=9D directive? Multiple =E2=80=9C-args_file=E2=80=9D inclusions are OK, but when there = are conflicting =E2=80=9C-name=E2=80=9D settings the node will default = to nonode@nohost. When you specify both =E2=80=9C-name=E2=80=9D and = =E2=80=9C-sname=E2=80=9D the latter will take precedence. Try removing = the =E2=80=9C-name=E2=80=9D from $ROOTDIR/etc/vm.args and setting it = using either of your first two methods. Cheers, Adam > On Oct 18, 2016, at 11:33 AM, Melvin.Lew@tdameritrade.com wrote: >=20 > Hi, >=20 > 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: >=20 > export ERL_FLAGS=3D"-couch_ini /myinstance1/default.ini = /myinstance1/local.ini -args_file /myinstance1/vm.args" >=20 > However, the couchdb log shows the node identity as: nonode@nohost >=20 > Then I tried specifying -name in ERL_FLAGS: >=20 > export ERL_FLAGS=3D"-couch_ini /myinstance1/default.ini = /myinstance1/local.ini -name metc/yinstance1@hostname1.domain" >=20 > And I still get: nonode@nohost >=20 > Finally, I tried specifying -sname in ERL_FLAGS, and this seems to = work, but gives a shortname: >=20 > export ERL_FLAGS=3D"-couch_ini /myinstance1/default.ini = /myinstance1/local.ini -sname myinstance1" >=20 > 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? >=20 > Thanks for your help! >=20 > -----Original Message----- > From: Jiang, Maggie=20 > Sent: Thursday, October 06, 2016 5:27 PM > To: user@couchdb.apache.org > Subject: RE: CouchDB 2.0 Command Line Options >=20 > Thanks Adam and Jan. We were able to have a few instances running with = the workaround. >=20 > -----Original Message----- > From: Adam Kocoloski [mailto:kocolosk@apache.org]=20 > Sent: Thursday, October 06, 2016 12:47 PM > To: user@couchdb.apache.org > Subject: Re: CouchDB 2.0 Command Line Options >=20 > Thanks Jan, that was a bit cleaner than I realized. It=E2=80=99s a = decent workaround. Important to note that every file you want to be = consulted needs to be listed there =E2=80=94 the couch_ini flag will = override the default search space entirely. >=20 > Adam >=20 >> On Oct 6, 2016, at 11:48 AM, Jan Lehnardt wrote: >>=20 >> try >> export ERL_FLAGS=3D=E2=80=9C-couch_ini /path/to/default.ini = /path/to/local_one.ini=E2=80=9D >> ./bin/couchdb >>=20 >> Analogous with local_two.ini etc. >>=20 >> Best >> Jan >> -- >>=20 >>> On 06 Oct 2016, at 17:41, Maggie.Jiang@tdameritrade.com wrote: >>>=20 >>> Hi Adam, >>>=20 >>> 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. >>>=20 >>> Maggie >>>=20 >>> -----Original Message----- >>> From: Adam Kocoloski [mailto:kocolosk@apache.org]=20 >>> Sent: Thursday, October 06, 2016 11:10 AM >>> To: user@couchdb.apache.org >>> Subject: Re: CouchDB 2.0 Command Line Options >>>=20 >>> Hi Maggie, >>>=20 >>> You=E2=80=99re right, the =E2=80=9C-a=E2=80=9D switch is ignored in = 2.0. That=E2=80=99s a miss on our part. I filed = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__issues.apache.org_j= ira_browse_COUCHDB-2D3183&d=3DDQIFaQ&c=3DnulvIAQnC0yOOjC0e0NVa8TOcyq9jNhjZ= 156R-JJU10&r=3DNRwPGDrZo7L6ztGDn5UDKmqnTC5BQkZuuScVw4Hm9u4&m=3DCvGFCOSao1p= TuD2kwqk7Wzhvz_0qdcdqfL_QjL_7E3o&s=3DLfHg4gH3qRk1Ve2f26b8_Pnj3TqhGxUo0O_du= EaLikg&e=3D . 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. >>>=20 >>> 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=E2=80=99t really recommend going there. Does the local.d option = work for you or do you need to point to another location? >>>=20 >>> Adam >>>=20 >>>> On Oct 5, 2016, at 10:20 AM, Maggie.Jiang@tdameritrade.com wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> 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. >>>>=20 >>>> Thanks, >>>>=20 >>>> Maggie >>>=20 >>=20 >> --=20 >> Professional Support for Apache CouchDB: >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__neighbourhood.ie_co= uchdb-2Dsupport_&d=3DDQIFaQ&c=3DnulvIAQnC0yOOjC0e0NVa8TOcyq9jNhjZ156R-JJU1= 0&r=3DNRwPGDrZo7L6ztGDn5UDKmqnTC5BQkZuuScVw4Hm9u4&m=3DUrPI_7HMw1047UYbHeTM= FRtpuzryeI9yzBKSv0ieS8E&s=3D6d4Kf2O6B8PgNTTpkGIW73WmB8P-S3Ysw6TbUfVuhZg&e=3D= =20 >>=20 >=20