Hi Andy,
You know, I really have become a big fan of CouchDB and PouchDB. I swear, it’s as if those
tools were made just for me and how I like to make stuff.
I’d love to do a blog post. I’ve subscribed to the marketing list and I’ll post there
soon.
Thank you!!
Kindest Regards,
Bill Stephenson
Tech Support
www.ezInvoice.com <http://www.ezinvoice.com/>
1-417-546-8390
> On Dec 9, 2016, at 3:45 AM, Andy Wenk <andywenk@apache.org> wrote:
>
> Hey Bill,
>
> thanks for reaching out to us and awesome to hear, that you are now a CouchDB and PouchDB
fanboy ;-).
>
> Would you be interested to share your experiences by writing a blog post for https://blog.couchdb.org/?
We would assist you with it as much as we can ;-) To organise or discuss this further, please
use the Marketing mailing-list marketing@couchdb.apache.org.
>
> Thank you and all the best
>
> Andy
>
> --
> Andy Wenk
> RockIt!
>
> Hamburg / Germany
>
> GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
>
>> On 9 Dec 2016, at 08:15, bill2@ezinvoice.com wrote:
>>
>> Hi Jenn, and all,
>>
>> I’ve been playing with CouchDB/PouchDB/JQuery/Bootstrap to make a sort of blog/sharing
site:
>>
>> http://ibloc.com <http://ibloc.com/>
>>
>> It’s kind of like https://medium.com <https://medium.com/> and "https://news.ycombinator.com
<https://news.ycombinator.com/>”, which are two of my favorite sites to take a break
from work with.
>>
>> The code is a mess because I’ve really just been hacking and playing, and I’ve
still got some things I’d like to add and tweak there, but I think it's a pretty fun app
and it only took a couple days to rough it out, which just amazes me. Those four tools work
so well together they should come in a boxed set. Sucks that I can’t think of a snazzy acronym
for them, but I’ve tried and still got nothing.
>>
>> Anyway, I’ll clean the code up soon but I wanted to share it here since we don’t
get to see enough stuff made just for fun and if anyone wants to post something there, well,
that would just make my day.
>>
>>
>> Kindest Regards,
>>
>> Bill Stephenson
>>
>>
>>> On Dec 8, 2016, at 10:40 AM, Jenn Turner <jenn@thehoodiefirm.com> wrote:
>>>
>>> Hello there!
>>>
>>> The CouchDB weekly news is now live at:
>>> https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/ <https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/>
>>>
>>> Highlights include new videos, new uses cases for PouchDb and CouchDB, plus burmese
pythons take over :/
>>>
>>> Thanks to Dave and Ronan for contributing content!
>>>
>>> You can help us spread the news by sharing on Twitter (https://twitter.com/CouchDB/status/806900432261918721
<https://twitter.com/CouchDB/status/806900432261918721>) and other social networks.
>>>
>>> Also, if you have news for next week, just REPLY to this thread.
>>>
>>> Cheers!
>>>
>>> Jenn Turner
>>> The Neighbourhoodie Software GmbH
>>> Adalbertstr. 7-8, 10999 Berlin
>>> neighbourhood.ie <http://neighbourhood.ie/>
>>>
>>> Handelsregister HRB 157851 B Amtsgericht Charlottenburg
>>> Geschäftsführung: Jan Lehnardt
>>
>

Hey Bill,
thanks for reaching out to us and awesome to hear, that you are now a CouchDB and PouchDB
fanboy ;-).
Would you be interested to share your experiences by writing a blog post for https://blog.couchdb.org/?
We would assist you with it as much as we can ;-) To organise or discuss this further, please
use the Marketing mailing-list marketing@couchdb.apache.org.
Thank you and all the best
Andy
--
Andy Wenk
RockIt!
Hamburg / Germany
GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
> On 9 Dec 2016, at 08:15, bill2@ezinvoice.com wrote:
>
> Hi Jenn, and all,
>
> I’ve been playing with CouchDB/PouchDB/JQuery/Bootstrap to make a sort of blog/sharing
site:
>
> http://ibloc.com <http://ibloc.com/>
>
> It’s kind of like https://medium.com <https://medium.com/> and "https://news.ycombinator.com
<https://news.ycombinator.com/>”, which are two of my favorite sites to take a break
from work with.
>
> The code is a mess because I’ve really just been hacking and playing, and I’ve still
got some things I’d like to add and tweak there, but I think it's a pretty fun app and it
only took a couple days to rough it out, which just amazes me. Those four tools work so well
together they should come in a boxed set. Sucks that I can’t think of a snazzy acronym for
them, but I’ve tried and still got nothing.
>
> Anyway, I’ll clean the code up soon but I wanted to share it here since we don’t
get to see enough stuff made just for fun and if anyone wants to post something there, well,
that would just make my day.
>
>
> Kindest Regards,
>
> Bill Stephenson
>
>
>> On Dec 8, 2016, at 10:40 AM, Jenn Turner <jenn@thehoodiefirm.com> wrote:
>>
>> Hello there!
>>
>> The CouchDB weekly news is now live at:
>> https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/ <https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/>
>>
>> Highlights include new videos, new uses cases for PouchDb and CouchDB, plus burmese
pythons take over :/
>>
>> Thanks to Dave and Ronan for contributing content!
>>
>> You can help us spread the news by sharing on Twitter (https://twitter.com/CouchDB/status/806900432261918721
<https://twitter.com/CouchDB/status/806900432261918721>) and other social networks.
>>
>> Also, if you have news for next week, just REPLY to this thread.
>>
>> Cheers!
>>
>> Jenn Turner
>> The Neighbourhoodie Software GmbH
>> Adalbertstr. 7-8, 10999 Berlin
>> neighbourhood.ie <http://neighbourhood.ie/>
>>
>> Handelsregister HRB 157851 B Amtsgericht Charlottenburg
>> Geschäftsführung: Jan Lehnardt
>

Re: [NEWS] The CouchDB weekly news for December 8 is out!"bill2@ezinvoice.com" <bill2@ezinvoice.com>urn:uuid:%3c82377791-18FC-42BF-8D24-80C01BB54EF3@ezinvoice-com%3e2016-12-09T07:15:03Z

Hi Jenn, and all,
I’ve been playing with CouchDB/PouchDB/JQuery/Bootstrap to make a sort of blog/sharing site:
http://ibloc.com <http://ibloc.com/>
It’s kind of like https://medium.com <https://medium.com/> and "https://news.ycombinator.com
<https://news.ycombinator.com/>”, which are two of my favorite sites to take a break
from work with.
The code is a mess because I’ve really just been hacking and playing, and I’ve still got
some things I’d like to add and tweak there, but I think it's a pretty fun app and it only
took a couple days to rough it out, which just amazes me. Those four tools work so well together
they should come in a boxed set. Sucks that I can’t think of a snazzy acronym for them,
but I’ve tried and still got nothing.
Anyway, I’ll clean the code up soon but I wanted to share it here since we don’t get
to see enough stuff made just for fun and if anyone wants to post something there, well, that
would just make my day.
Kindest Regards,
Bill Stephenson
> On Dec 8, 2016, at 10:40 AM, Jenn Turner <jenn@thehoodiefirm.com> wrote:
>
> Hello there!
>
> The CouchDB weekly news is now live at:
> https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/ <https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/>
>
> Highlights include new videos, new uses cases for PouchDb and CouchDB, plus burmese pythons
take over :/
>
> Thanks to Dave and Ronan for contributing content!
>
> You can help us spread the news by sharing on Twitter (https://twitter.com/CouchDB/status/806900432261918721
<https://twitter.com/CouchDB/status/806900432261918721>) and other social networks.
>
> Also, if you have news for next week, just REPLY to this thread.
>
> Cheers!
>
> Jenn Turner
> The Neighbourhoodie Software GmbH
> Adalbertstr. 7-8, 10999 Berlin
> neighbourhood.ie <http://neighbourhood.ie/>
>
> Handelsregister HRB 157851 B Amtsgericht Charlottenburg
> Geschäftsführung: Jan Lehnardt

OK, I should send a PUT instead of POST.
Daniel.
From: Daniel Suen <ttdsuen@yahoo.com.INVALID>
To: User <user@couchdb.apache.org>
Sent: Thursday, December 8, 2016 10:52 AM
Subject: update functions in design document - missing X-Couch-Id and X-Couch-Update-NewRev...
I am on CouchDB 2.0 on Linux.
I created a function inside the updates object of my design document. It basically looks similar
to the examples given in the API reference.
When I tried to invoke the function, it executes correctly (the target document gets updated),
and according the the API reference, I should be expecting "X-Couch-Id" and "X-Couch-Update-NewRev"
in the headers. However, I don't see them being returned. I saw "X-Couch-Request-ID" and "X-CouchDB-Body-Time",
but not the ones stated in the reference documentation.
Did anyone experience the same thing before?
What should I do to make them appear in the response headers?
The documtation is at 10.5.5. /db/_design/design-doc/_show/show-name — Apache CouchDB 2.0
Documentation.
|
| |
10.5.5. /db/_design/design-doc/_show/show-name — Apache CouchDB 2.0 Documentation
| |
|
Appreciate your help.
Daniel.

[NEWS] The CouchDB weekly news for December 8 is out!Jenn Turner <jenn@thehoodiefirm.com>urn:uuid:%3cE712335E-2BF9-4A69-923D-FFC42BBBCA85@thehoodiefirm-com%3e2016-12-08T16:40:48Z

Hello there!
The CouchDB weekly news is now live at:
https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/ <https://blog.couchdb.org/2016/12/08/couchdb-weekly-news-december-8-2016/>
Highlights include new videos, new uses cases for PouchDb and CouchDB, plus burmese pythons
take over :/
Thanks to Dave and Ronan for contributing content!
You can help us spread the news by sharing on Twitter (https://twitter.com/CouchDB/status/806900432261918721
<https://twitter.com/CouchDB/status/806900432261918721>) and other social networks.
Also, if you have news for next week, just REPLY to this thread.
Cheers!
Jenn Turner
The Neighbourhoodie Software GmbH
Adalbertstr. 7-8, 10999 Berlin
neighbourhood.ie <http://neighbourhood.ie/>
Handelsregister HRB 157851 B Amtsgericht Charlottenburg
Geschäftsführung: Jan Lehnardt

I am on CouchDB 2.0 on Linux.
I created a function inside the updates object of my design document. It basically looks similar
to the examples given in the API reference.
When I tried to invoke the function, it executes correctly (the target document gets updated),
and according the the API reference, I should be expecting "X-Couch-Id" and "X-Couch-Update-NewRev"
in the headers. However, I don't see them being returned. I saw "X-Couch-Request-ID" and "X-CouchDB-Body-Time",
but not the ones stated in the reference documentation.
Did anyone experience the same thing before?
What should I do to make them appear in the response headers?
The documtation is at 10.5.5. /db/_design/design-doc/_show/show-name — Apache CouchDB 2.0
Documentation.
|
| |
10.5.5. /db/_design/design-doc/_show/show-name — Apache CouchDB 2.0 Documentation
| |
|
Appreciate your help.
Daniel.

On Thu, Dec 8, 2016 at 12:19 PM, Jan Lehnardt <jan@apache.org> wrote:
>
> it definitely does: https://github.com/apache/couchdb-setup/blob/master/src/setup.erl#L172
;)
>
I agree that code is the ultimate documentation, but for those who
prefer reading in English over Erlang I made a little translation ;)
https://github.com/apache/couchdb-documentation/pull/94
>> On Thu, Dec 8, 2016 at 11:34 AM, Jan Lehnardt <jan@apache.org> wrote:
>>>
>>>> On 8 Dec 2016, at 11:30, Daniel Munch <dani.munch@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> another question regarding single-node-setup: Is it mandatory to run
>>>> the setup wizard? If yes, is there a way to run the single-node-setup
>>>> without the wizard, like there is for the cluster-setup?
>>>>
>>>> What I'm currently doing is to configure my admin user and password
>>>> beforehand in the config file and create those special databases
>>>> _users, _replicator and _global_changes manually like written in the
>>>> docs. CouchDB runs fine after this, however I'm always feeling guilty
>>>> since I'm not 100% sure if I missed something because I didn't run the
>>>> wizard.
>>>
>>> The wizard does precisely this: set an admin password and create the
>>> three system databases, so you’re good to go.
>>>
>>> Best
>>> Jan
>>> --
>>>
>>>
>>>
>>>>
>>>> Thanks!
>>>> Daniel
>>>>
>>>>
>>>> On Mon, Dec 5, 2016 at 7:29 PM, Joan Touzet <wohali@apache.org> wrote:
>>>>> You missed the setup step where you create the _users database:
>>>>>
>>>>> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>>>>>
>>>>> -Joan
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
>>>>>> To: user@couchdb.apache.org
>>>>>> Sent: Monday, December 5, 2016 10:42:00 AM
>>>>>> Subject: Creating users - getting back "Database does not exist."
>>>>>>
>>>>>> I’m working though the tutorial on CouchDB
>>>>>>
>>>>>> http://docs.couchdb.org/en/latest/intro/security.html
>>>>>>
>>>>>> I’m at the section “Creating a New User”, where is says:
>>>>>>
>>>>>> Creating a new user is a very trivial operation. You just need to
do
>>>>>> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>>>>>> request with the user’s data to CouchDB. Let’s create a user
with
>>>>>> login jan and password apple:
>>>>>>
>>>>>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>>>>>> -H "Accept: application/json" \
>>>>>> -H "Content-Type: application/json" \
>>>>>> -d '{"name": "jan", "password": "apple", "roles": [], "type":
>>>>>> "user"}'
>>>>>>
>>>>>> When I try this, I get
>>>>>>
>>>>>> {"error":"not_found","reason":"Database does not exist.”}
>>>>>>
>>>>>>
>>>>>>
>>>>>> I’m missing something here. Can anyone advise?
>>>>>>
>>>>>> Nick
>>>>>> ________________________________
>>>>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>>>>
>>>>>> This email and any files with it are confidential and intended solely
>>>>>> for the use of the recipient to whom it is addressed. If you are
not
>>>>>> the intended recipient then copying, distribution or other use of
>>>>>> the information contained is strictly prohibited and you should not
>>>>>> rely on it. If you have received this email in error please let the
>>>>>> sender know immediately and delete it from your system(s). Internet
>>>>>> emails are not necessarily secure. While we take every care,
>>>>>> Plymouth University accepts no responsibility for viruses and it
is
>>>>>> your responsibility to scan emails and their attachments. Plymouth
>>>>>> University does not accept responsibility for any changes made after
>>>>>> it was sent. Nothing in this email or its attachments constitutes
an
>>>>>> order for goods or services unless accompanied by an official order
>>>>>> form.
>>>>>>
>>>
>>> --
>>> Professional Support for Apache CouchDB:
>>> https://neighbourhood.ie/couchdb-support/
>>>
>
> --
> Professional Support for Apache CouchDB:
> https://neighbourhood.ie/couchdb-support/
>

> On 8 Dec 2016, at 11:58, Daniel Munch <dani.munch@gmail.com> wrote:
>
> Great, thanks!
>
> I think the question was asked before, but from the docs it doesn't
> seem obvious that the wizard creates the three system databases as
> well, it kind of reads as if you'd have to do this manually after it
> ran. So if that's the case I'd go and add those informations to the
> docs, guess this could be handy for others as well!
it definitely does: https://github.com/apache/couchdb-setup/blob/master/src/setup.erl#L172
;)
>
> Best,
> Daniel
>
> On Thu, Dec 8, 2016 at 11:34 AM, Jan Lehnardt <jan@apache.org> wrote:
>>
>>> On 8 Dec 2016, at 11:30, Daniel Munch <dani.munch@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> another question regarding single-node-setup: Is it mandatory to run
>>> the setup wizard? If yes, is there a way to run the single-node-setup
>>> without the wizard, like there is for the cluster-setup?
>>>
>>> What I'm currently doing is to configure my admin user and password
>>> beforehand in the config file and create those special databases
>>> _users, _replicator and _global_changes manually like written in the
>>> docs. CouchDB runs fine after this, however I'm always feeling guilty
>>> since I'm not 100% sure if I missed something because I didn't run the
>>> wizard.
>>
>> The wizard does precisely this: set an admin password and create the
>> three system databases, so you’re good to go.
>>
>> Best
>> Jan
>> --
>>
>>
>>
>>>
>>> Thanks!
>>> Daniel
>>>
>>>
>>> On Mon, Dec 5, 2016 at 7:29 PM, Joan Touzet <wohali@apache.org> wrote:
>>>> You missed the setup step where you create the _users database:
>>>>
>>>> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>>>>
>>>> -Joan
>>>>
>>>> ----- Original Message -----
>>>>> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
>>>>> To: user@couchdb.apache.org
>>>>> Sent: Monday, December 5, 2016 10:42:00 AM
>>>>> Subject: Creating users - getting back "Database does not exist."
>>>>>
>>>>> I’m working though the tutorial on CouchDB
>>>>>
>>>>> http://docs.couchdb.org/en/latest/intro/security.html
>>>>>
>>>>> I’m at the section “Creating a New User”, where is says:
>>>>>
>>>>> Creating a new user is a very trivial operation. You just need to do
>>>>> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>>>>> request with the user’s data to CouchDB. Let’s create a user with
>>>>> login jan and password apple:
>>>>>
>>>>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>>>>> -H "Accept: application/json" \
>>>>> -H "Content-Type: application/json" \
>>>>> -d '{"name": "jan", "password": "apple", "roles": [], "type":
>>>>> "user"}'
>>>>>
>>>>> When I try this, I get
>>>>>
>>>>> {"error":"not_found","reason":"Database does not exist.”}
>>>>>
>>>>>
>>>>>
>>>>> I’m missing something here. Can anyone advise?
>>>>>
>>>>> Nick
>>>>> ________________________________
>>>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>>>
>>>>> This email and any files with it are confidential and intended solely
>>>>> for the use of the recipient to whom it is addressed. If you are not
>>>>> the intended recipient then copying, distribution or other use of
>>>>> the information contained is strictly prohibited and you should not
>>>>> rely on it. If you have received this email in error please let the
>>>>> sender know immediately and delete it from your system(s). Internet
>>>>> emails are not necessarily secure. While we take every care,
>>>>> Plymouth University accepts no responsibility for viruses and it is
>>>>> your responsibility to scan emails and their attachments. Plymouth
>>>>> University does not accept responsibility for any changes made after
>>>>> it was sent. Nothing in this email or its attachments constitutes an
>>>>> order for goods or services unless accompanied by an official order
>>>>> form.
>>>>>
>>
>> --
>> Professional Support for Apache CouchDB:
>> https://neighbourhood.ie/couchdb-support/
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

Great, thanks!
I think the question was asked before, but from the docs it doesn't
seem obvious that the wizard creates the three system databases as
well, it kind of reads as if you'd have to do this manually after it
ran. So if that's the case I'd go and add those informations to the
docs, guess this could be handy for others as well!
Best,
Daniel
On Thu, Dec 8, 2016 at 11:34 AM, Jan Lehnardt <jan@apache.org> wrote:
>
>> On 8 Dec 2016, at 11:30, Daniel Munch <dani.munch@gmail.com> wrote:
>>
>> Hi,
>>
>> another question regarding single-node-setup: Is it mandatory to run
>> the setup wizard? If yes, is there a way to run the single-node-setup
>> without the wizard, like there is for the cluster-setup?
>>
>> What I'm currently doing is to configure my admin user and password
>> beforehand in the config file and create those special databases
>> _users, _replicator and _global_changes manually like written in the
>> docs. CouchDB runs fine after this, however I'm always feeling guilty
>> since I'm not 100% sure if I missed something because I didn't run the
>> wizard.
>
> The wizard does precisely this: set an admin password and create the
> three system databases, so you’re good to go.
>
> Best
> Jan
> --
>
>
>
>>
>> Thanks!
>> Daniel
>>
>>
>> On Mon, Dec 5, 2016 at 7:29 PM, Joan Touzet <wohali@apache.org> wrote:
>>> You missed the setup step where you create the _users database:
>>>
>>> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>>>
>>> -Joan
>>>
>>> ----- Original Message -----
>>>> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
>>>> To: user@couchdb.apache.org
>>>> Sent: Monday, December 5, 2016 10:42:00 AM
>>>> Subject: Creating users - getting back "Database does not exist."
>>>>
>>>> I’m working though the tutorial on CouchDB
>>>>
>>>> http://docs.couchdb.org/en/latest/intro/security.html
>>>>
>>>> I’m at the section “Creating a New User”, where is says:
>>>>
>>>> Creating a new user is a very trivial operation. You just need to do
>>>> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>>>> request with the user’s data to CouchDB. Let’s create a user with
>>>> login jan and password apple:
>>>>
>>>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>>>> -H "Accept: application/json" \
>>>> -H "Content-Type: application/json" \
>>>> -d '{"name": "jan", "password": "apple", "roles": [], "type":
>>>> "user"}'
>>>>
>>>> When I try this, I get
>>>>
>>>> {"error":"not_found","reason":"Database does not exist.”}
>>>>
>>>>
>>>>
>>>> I’m missing something here. Can anyone advise?
>>>>
>>>> Nick
>>>> ________________________________
>>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>>
>>>> This email and any files with it are confidential and intended solely
>>>> for the use of the recipient to whom it is addressed. If you are not
>>>> the intended recipient then copying, distribution or other use of
>>>> the information contained is strictly prohibited and you should not
>>>> rely on it. If you have received this email in error please let the
>>>> sender know immediately and delete it from your system(s). Internet
>>>> emails are not necessarily secure. While we take every care,
>>>> Plymouth University accepts no responsibility for viruses and it is
>>>> your responsibility to scan emails and their attachments. Plymouth
>>>> University does not accept responsibility for any changes made after
>>>> it was sent. Nothing in this email or its attachments constitutes an
>>>> order for goods or services unless accompanied by an official order
>>>> form.
>>>>
>
> --
> Professional Support for Apache CouchDB:
> https://neighbourhood.ie/couchdb-support/
>

Severity: High
Vendor:
The Apache Software Foundation
Versions Affected:
CouchDB 2.0.0 (Windows platform only)
Description:
The Windows installer that the Apache CouchDB team provides is vulnerable to local privilege
escalation. All files in the install inherit the file permissions of the parent directory
and therefore a non-privileged user can substitute any executable for the nssm.exe service
launcher, or CouchDB batch or binary files. A subsequent service or server restart will then
run that binary with administrator privilege.
We have replaced the 2.0.0 .msi file on our website with a fixed version and deleted the vulnerable
one.
The new installer can be downloaded at https://dl.bintray.com/apache/couchdb/win/2.0.0.1/apache-couchdb-2.0.0.1.msi
Mitigation:
The recommended remediation is to uninstall CouchDB 2.0.0 and install CouchDB 2.0.0.1. This
will set the permissions correctly on the target directory, preventing replacement of binaries
by unauthorized users.
If an upgrade cannot be performed, the following steps will secure an existing CouchDB 2.0.0
installation:
1. In Windows Explorer, navigate to the CouchDB installation folder. Right click on the folder
and select Properties.
2. In the Properties window, select the Security tab, and click on the Advanced button.
3. In the Advanced Security Settings window, click the Change Permissions... button.
4. Ensure only the following settings are listed, removing any other entries:
Allow - Users - Read & Execute
Allow - SYSTEM - Full control
Allow - Administrators - Full control
5. Check the "Replace all child object permissions with inheritable permissions from this
object."
6. Click OK three times to close all dialog boxes.
Credit:
This issue was reported by John Page aka hyp3rlinx.

> On 8 Dec 2016, at 11:30, Daniel Munch <dani.munch@gmail.com> wrote:
>
> Hi,
>
> another question regarding single-node-setup: Is it mandatory to run
> the setup wizard? If yes, is there a way to run the single-node-setup
> without the wizard, like there is for the cluster-setup?
>
> What I'm currently doing is to configure my admin user and password
> beforehand in the config file and create those special databases
> _users, _replicator and _global_changes manually like written in the
> docs. CouchDB runs fine after this, however I'm always feeling guilty
> since I'm not 100% sure if I missed something because I didn't run the
> wizard.
The wizard does precisely this: set an admin password and create the
three system databases, so you’re good to go.
Best
Jan
--
>
> Thanks!
> Daniel
>
>
> On Mon, Dec 5, 2016 at 7:29 PM, Joan Touzet <wohali@apache.org> wrote:
>> You missed the setup step where you create the _users database:
>>
>> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>>
>> -Joan
>>
>> ----- Original Message -----
>>> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
>>> To: user@couchdb.apache.org
>>> Sent: Monday, December 5, 2016 10:42:00 AM
>>> Subject: Creating users - getting back "Database does not exist."
>>>
>>> I’m working though the tutorial on CouchDB
>>>
>>> http://docs.couchdb.org/en/latest/intro/security.html
>>>
>>> I’m at the section “Creating a New User”, where is says:
>>>
>>> Creating a new user is a very trivial operation. You just need to do
>>> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>>> request with the user’s data to CouchDB. Let’s create a user with
>>> login jan and password apple:
>>>
>>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>>> -H "Accept: application/json" \
>>> -H "Content-Type: application/json" \
>>> -d '{"name": "jan", "password": "apple", "roles": [], "type":
>>> "user"}'
>>>
>>> When I try this, I get
>>>
>>> {"error":"not_found","reason":"Database does not exist.”}
>>>
>>>
>>>
>>> I’m missing something here. Can anyone advise?
>>>
>>> Nick
>>> ________________________________
>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>
>>> This email and any files with it are confidential and intended solely
>>> for the use of the recipient to whom it is addressed. If you are not
>>> the intended recipient then copying, distribution or other use of
>>> the information contained is strictly prohibited and you should not
>>> rely on it. If you have received this email in error please let the
>>> sender know immediately and delete it from your system(s). Internet
>>> emails are not necessarily secure. While we take every care,
>>> Plymouth University accepts no responsibility for viruses and it is
>>> your responsibility to scan emails and their attachments. Plymouth
>>> University does not accept responsibility for any changes made after
>>> it was sent. Nothing in this email or its attachments constitutes an
>>> order for goods or services unless accompanied by an official order
>>> form.
>>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

Hi,
another question regarding single-node-setup: Is it mandatory to run
the setup wizard? If yes, is there a way to run the single-node-setup
without the wizard, like there is for the cluster-setup?
What I'm currently doing is to configure my admin user and password
beforehand in the config file and create those special databases
_users, _replicator and _global_changes manually like written in the
docs. CouchDB runs fine after this, however I'm always feeling guilty
since I'm not 100% sure if I missed something because I didn't run the
wizard.
Thanks!
Daniel
On Mon, Dec 5, 2016 at 7:29 PM, Joan Touzet <wohali@apache.org> wrote:
> You missed the setup step where you create the _users database:
>
> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>
> -Joan
>
> ----- Original Message -----
>> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
>> To: user@couchdb.apache.org
>> Sent: Monday, December 5, 2016 10:42:00 AM
>> Subject: Creating users - getting back "Database does not exist."
>>
>> I’m working though the tutorial on CouchDB
>>
>> http://docs.couchdb.org/en/latest/intro/security.html
>>
>> I’m at the section “Creating a New User”, where is says:
>>
>> Creating a new user is a very trivial operation. You just need to do
>> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>> request with the user’s data to CouchDB. Let’s create a user with
>> login jan and password apple:
>>
>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>> -H "Accept: application/json" \
>> -H "Content-Type: application/json" \
>> -d '{"name": "jan", "password": "apple", "roles": [], "type":
>> "user"}'
>>
>> When I try this, I get
>>
>> {"error":"not_found","reason":"Database does not exist.”}
>>
>>
>>
>> I’m missing something here. Can anyone advise?
>>
>> Nick
>> ________________________________
>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>
>> This email and any files with it are confidential and intended solely
>> for the use of the recipient to whom it is addressed. If you are not
>> the intended recipient then copying, distribution or other use of
>> the information contained is strictly prohibited and you should not
>> rely on it. If you have received this email in error please let the
>> sender know immediately and delete it from your system(s). Internet
>> emails are not necessarily secure. While we take every care,
>> Plymouth University accepts no responsibility for viruses and it is
>> your responsibility to scan emails and their attachments. Plymouth
>> University does not accept responsibility for any changes made after
>> it was sent. Nothing in this email or its attachments constitutes an
>> order for goods or services unless accompanied by an official order
>> form.
>>

In addition, PRs against https://github.com/apache/couchdb-documentation would ideal for us,
and would guarantee the fastest turnaround time to publication ;)
Best
Jan
--
> On 7 Dec 2016, at 20:57, Joan Touzet <wohali@apache.org> wrote:
>
> If you can do the work to incorporate the information you've built up
> into our actual documentation repository, that's the best option. We
> want there to be a single place people go to learn how to install and
> setup CouchDB 2.0.
>
> If not, you can provide the HOWTO document to us, preferably with a
> JIRA ticket suggesting the info be incorporated into the installation
> documentation, and we'll make a best effort to get the info into the
> real docs.
>
> Thanks again for your help!
>
> Best,
> Joan
>
> ----- Original Message -----
>> From: "Karl Helmer" <helmer@nmr.mgh.harvard.edu>
>> To: "Joan Touzet" <wohali@apache.org>
>> Cc: user@couchdb.apache.org
>> Sent: Wednesday, December 7, 2016 10:45:02 AM
>> Subject: Re: Creating users - getting back "Database does not exist."
>>
>> Hi Joan,
>>
>> I've actually been working on a separate "how-to" doc for 2.0
>> installation on Ubuntu linux just for my own records. It has info on
>> a
>> few issues I've found as I go through the process. If you're
>> interested in it, I'd be happy to share (after I clean it up...). Or
>> I
>> can submit individual pull requests if that works better.
>>
>> regards,
>> Karl
>>
>>
>>> Hi Karl,
>>>
>>> Agreed. The docs were rushed for the v2.0.0 release and need work.
>>> Pull requests are welcome ;-)
>>>
>>> -Joan
>>>
>>> ----- Original Message -----
>>>> From: "Karl Helmer" <helmer@nmr.mgh.harvard.edu>
>>>> To: user@couchdb.apache.org
>>>> Cc: user@couchdb.apache.org, "Joan Touzet" <wohali@apache.org>
>>>> Sent: Tuesday, December 6, 2016 9:13:21 AM
>>>> Subject: Re: Creating users - getting back "Database does not
>>>> exist."
>>>>
>>>> Hi,
>>>>
>>>> I think one possible reason for why this question comes up
>>>> fairly
>>>> frequently is that if you follow the installation instructions
>>>> starting
>>>> at 2.1 and then keep hitting "next topic", section 2.6,
>>>> Single-node
>>>> Setup, is skipped - it goes from 2.5 -> 3.0.
>>>>
>>>> regards,
>>>> Karl
>>>>
>>>>
>>>>> Thank you Joan - indeed I was missing something!
>>>>>
>>>>> Much appreciated -
>>>>>
>>>>> Nick
>>>>>
>>>>> (email / Skype for Business):
>>>>> nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>
>>>>> (mobile / iMessage): +44 7540 695741<tel:+44%207540%20695741>
>>>>> (office): +44 1752 586257<tel:+44%201752%20586257>
>>>>> (twitter): noutram_at_uop
>>>>>
>>>>> iTunes U course: iOS Development in Swift:
>>>>> http://iTunes.com/plymouthswift<http://itunes.com/plymouthswift>
>>>>>
>>>>> On 5 Dec 2016, at 18:33, Joan Touzet
>>>>> <wohali@apache.org<mailto:wohali@apache.org>> wrote:
>>>>>
>>>>> You missed the setup step where you create the _users database:
>>>>>
>>>>> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>>>>>
>>>>> -Joan
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Nicholas Outram"
>>>>> <nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>>
>>>>> To: user@couchdb.apache.org<mailto:user@couchdb.apache.org>
>>>>> Sent: Monday, December 5, 2016 10:42:00 AM
>>>>> Subject: Creating users - getting back "Database does not
>>>>> exist."
>>>>>
>>>>> I'm working though the tutorial on CouchDB
>>>>>
>>>>> http://docs.couchdb.org/en/latest/intro/security.html
>>>>>
>>>>> I'm at the section "Creating a New User", where is says:
>>>>>
>>>>> Creating a new user is a very trivial operation. You just need
>>>>> to
>>>>> do
>>>>> a
>>>>> PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
>>>>> request with the user's data to CouchDB. Let's create a user
>>>>> with
>>>>> login jan and password apple:
>>>>>
>>>>> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
>>>>> -H "Accept: application/json" \
>>>>> -H "Content-Type: application/json" \
>>>>> -d '{"name": "jan", "password": "apple", "roles": [],
>>>>> "type":
>>>>> "user"}'
>>>>>
>>>>> When I try this, I get
>>>>>
>>>>> {"error":"not_found","reason":"Database does not exist."}
>>>>>
>>>>>
>>>>>
>>>>> I'm missing something here. Can anyone advise?
>>>>>
>>>>> Nick
>>>>> ________________________________
>>>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>>>
>>>>> This email and any files with it are confidential and intended
>>>>> solely
>>>>> for the use of the recipient to whom it is addressed. If you are
>>>>> not
>>>>> the intended recipient then copying, distribution or other use
>>>>> of
>>>>> the information contained is strictly prohibited and you should
>>>>> not
>>>>> rely on it. If you have received this email in error please let
>>>>> the
>>>>> sender know immediately and delete it from your system(s).
>>>>> Internet
>>>>> emails are not necessarily secure. While we take every care,
>>>>> Plymouth University accepts no responsibility for viruses and it
>>>>> is
>>>>> your responsibility to scan emails and their attachments.
>>>>> Plymouth
>>>>> University does not accept responsibility for any changes made
>>>>> after
>>>>> it was sent. Nothing in this email or its attachments
>>>>> constitutes
>>>>> an
>>>>> order for goods or services unless accompanied by an official
>>>>> order
>>>>> form.
>>>>>
>>>>> ________________________________
>>>>> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>>>>>
>>>>> This email and any files with it are confidential and intended
>>>>> solely for
>>>>> the use of the recipient to whom it is addressed. If you are not
>>>>> the
>>>>> intended recipient then copying, distribution or other use of
>>>>> the
>>>>> information contained is strictly prohibited and you should not
>>>>> rely on
>>>>> it. If you have received this email in error please let the
>>>>> sender
>>>>> know
>>>>> immediately and delete it from your system(s). Internet emails
>>>>> are
>>>>> not
>>>>> necessarily secure. While we take every care, Plymouth
>>>>> University
>>>>> accepts
>>>>> no responsibility for viruses and it is your responsibility to
>>>>> scan
>>>>> emails
>>>>> and their attachments. Plymouth University does not accept
>>>>> responsibility
>>>>> for any changes made after it was sent. Nothing in this email or
>>>>> its
>>>>> attachments constitutes an order for goods or services unless
>>>>> accompanied
>>>>> by an official order form.
>>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>> helmer@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.
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> 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
>> helmer@nmr.mgh.harvard.edu
>>
>>
>>
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

Oh, I wasn't implying you were, was just explaining/apologising. Happy to hear your experience
of 2.0 is otherwise good.
B.
> On 7 Dec 2016, at 20:26, Brian Lanier <brianl@amco.me> wrote:
>
> Sorry, I didn't mean to infer I was unhappy with anything. On the contrary, considering
the amount of work that was done, I'm extremely impressed so far. I sort of expected more
trouble setting up the cluster the first time as I went straight for binding the IP's of the
services, firewalling the ports, requiring users, etc. Once I understood a few things and
fixed the connections/config, it just worked!
>
> Thanks again for the quick fix.
>
> Brian
>
> On 12/7/16 11:53 AM, Robert Samuel Newson wrote:
>> The road to 2.0 was long and unfortunately a number of things slipped us by. I think
you're the first to try coffeescript on 2.0, that's all. We know coffeescript _works_ because
we have tests for it, and those tests can find main-coffee.js in the source tree. The slip
was failing to copy it into the 'make release' output only.
>>
>> B.
>>
>>> On 7 Dec 2016, at 19:34, Brian Lanier <brianl@amco.me> wrote:
>>>
>>> Hi,
>>> I saw your fix and it worked for me. I was kind of hoping for some sort of bug
as I had run out of ideas to try and places to look. For now, its an easy manual fix for my
test cluster. I was able to fully replicate my previous db from 1.6.1 into 2.0.0 and can continue
testing/learning.
>>>
>>> Other than this, its been pretty good minus a few issues with documentation on
setup that have either been addressed or already have an issue open. Mainly the not well documented
way to require users for chtppd and wanting to lock down ports and access better via the bind
address. I see there are changes coming along those lines anyway. As 2.0 matures, I hope to
see some of the config I need migrated from direct erlang config via environment or via the
vm.args file and into couchdb config directly.
>>>
>>> Thanks for the quick fix and response on this. Was starting to wonder if couchdb
2.0 was not ready for our needs or if we were doing something extremely weird with coffeescript.
>>>
>>> Brian
>>>
>>> On 12/7/16 11:22 AM, Robert Samuel Newson wrote:
>>>> Hi Brian,
>>>>
>>>> I got there first. Fix is applied to master and will be in the next release.
It's as you say, it's the other .js file that's needed.
>>>>
>>>> B.
>>>>
>>>>> On 7 Dec 2016, at 18:45, Brian Lanier <brianl@amco.me> wrote:
>>>>>
>>>>> Hi Jan,
>>>>> I went to open an issue and found one already created. Don't know if
it was because of this email or total coincidence. I made the change manually and copied the
main-coffee.js from the source directory to my release directory and it looks like it resolved
my issues.
>>>>>
>>>>> So looks like this will resolve my issue. Should I add a comment to the
issue or is that not necessary?
>>>>>
>>>>> https://issues.apache.org/jira/browse/COUCHDB-3252
>>>>>
>>>>> Thanks
>>>>> Brian
>>>>>
>>>>> On 12/7/16 1:26 AM, Jan Lehnardt wrote:
>>>>>> Heya Brian,
>>>>>>
>>>>>> this looks serious,
>>>>>>
>>>>>> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB
so we can track this?
>>>>>>
>>>>>> Thank you!
>>>>>> Best
>>>>>> Jan
>>>>>> --
>>>>>>
>>>>>>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me>
wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>> I have a 2 node couchdb 2.0 cluster setup to start testing things.
It has been running great until I went to replicate a current db into the cluster from 1.6.1.
The replication locks up and fails and both nodes start spitting out a bunch of repeating
log lines indicating something is crashing. After further inspection, it seems the problem
occurs when the replication hits the _design docs, all of which are written in coffeescript.
>>>>>>>
>>>>>>> I switched to just trying to create a simple coffeescript design
doc via fauxton and via curl and I get the same process crashing errors. I have tried taking
a javascript design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>>>>>>
>>>>>>> This is all after changing the query server definition for coffeescript
to point to the file included. By default, the config points to ./share/server/main-coffee.js
which is not included in the release. I have changed it to ./share/server/coffee-script.js
which is included. Not sure if that was correct or not, but seemed to match what was done
in previous releases and I couldn't find much info in searches relating to coffeescript specific
config.
>>>>>>>
>>>>>>> Config on both nodes is the same.
>>>>>>>
>>>>>>> For testing purposes, here is the design doc I am testing with
and the command used to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>>>>>>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>>>>>>> {"error":"unknown_error","reason":"undefined"}
>>>>>>> root@stage.cdb-n1:~ #
>>>>>>>
>>>>>>> simple_test.json:
>>>>>>> root@stage.cdb-n1:~ # cat /simple_test.json
>>>>>>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n
emit doc._conflicts, null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>>>>>>
>>>>>>> The errors I see in the logs on both servers as soon as I try
to save the design doc with a coffeescript view:
>>>>>>>
>>>>>>> Node 1
>>>>>>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 cache miss for admin
>>>>>>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 no record of user admin
>>>>>>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process Start :: #Port<0.12902>
>>>>>>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17799.31> died normal
>>>>>>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>>>>>>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process Start :: #Port<0.12903>
>>>>>>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17809.31> died normal
>>>>>>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>>>>>>
>>>>>>> Node 2
>>>>>>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process Start :: #Port<0.7040>
>>>>>>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3683.1> died normal
>>>>>>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>>>>>>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process Start :: #Port<0.7082>
>>>>>>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3687.1> died normal
>>>>>>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>>>>>>
>>>>>>> couchdb is started via systemd and I am not seeing anything in
the log from standard out/error when this happens. As you can see I turned up the logging
to debug and just not getting any good info. Run out of ideas to try to get more info or resolve
this.
>>>>>>>
>>>>>>> I'm not sure if I am running into a configuration error, setup
error, install error or a bug. Any help on this would be appreciated. I can supply any additional
info as needed as this is a testing cluster and not in production yet.
>>>>>>>
>>>>>>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe:
Installed: 1:19.1-1)
>>>>>>>
>>>>>>> Thanks
>>>>>>> Brian
>

Sorry, I didn't mean to infer I was unhappy with anything. On the
contrary, considering the amount of work that was done, I'm extremely
impressed so far. I sort of expected more trouble setting up the cluster
the first time as I went straight for binding the IP's of the services,
firewalling the ports, requiring users, etc. Once I understood a few
things and fixed the connections/config, it just worked!
Thanks again for the quick fix.
Brian
On 12/7/16 11:53 AM, Robert Samuel Newson wrote:
> The road to 2.0 was long and unfortunately a number of things slipped us by. I think
you're the first to try coffeescript on 2.0, that's all. We know coffeescript _works_ because
we have tests for it, and those tests can find main-coffee.js in the source tree. The slip
was failing to copy it into the 'make release' output only.
>
> B.
>
>> On 7 Dec 2016, at 19:34, Brian Lanier <brianl@amco.me> wrote:
>>
>> Hi,
>> I saw your fix and it worked for me. I was kind of hoping for some sort of bug as
I had run out of ideas to try and places to look. For now, its an easy manual fix for my test
cluster. I was able to fully replicate my previous db from 1.6.1 into 2.0.0 and can continue
testing/learning.
>>
>> Other than this, its been pretty good minus a few issues with documentation on setup
that have either been addressed or already have an issue open. Mainly the not well documented
way to require users for chtppd and wanting to lock down ports and access better via the bind
address. I see there are changes coming along those lines anyway. As 2.0 matures, I hope to
see some of the config I need migrated from direct erlang config via environment or via the
vm.args file and into couchdb config directly.
>>
>> Thanks for the quick fix and response on this. Was starting to wonder if couchdb
2.0 was not ready for our needs or if we were doing something extremely weird with coffeescript.
>>
>> Brian
>>
>> On 12/7/16 11:22 AM, Robert Samuel Newson wrote:
>>> Hi Brian,
>>>
>>> I got there first. Fix is applied to master and will be in the next release.
It's as you say, it's the other .js file that's needed.
>>>
>>> B.
>>>
>>>> On 7 Dec 2016, at 18:45, Brian Lanier <brianl@amco.me> wrote:
>>>>
>>>> Hi Jan,
>>>> I went to open an issue and found one already created. Don't know if it was
because of this email or total coincidence. I made the change manually and copied the main-coffee.js
from the source directory to my release directory and it looks like it resolved my issues.
>>>>
>>>> So looks like this will resolve my issue. Should I add a comment to the issue
or is that not necessary?
>>>>
>>>> https://issues.apache.org/jira/browse/COUCHDB-3252
>>>>
>>>> Thanks
>>>> Brian
>>>>
>>>> On 12/7/16 1:26 AM, Jan Lehnardt wrote:
>>>>> Heya Brian,
>>>>>
>>>>> this looks serious,
>>>>>
>>>>> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB
so we can track this?
>>>>>
>>>>> Thank you!
>>>>> Best
>>>>> Jan
>>>>> --
>>>>>
>>>>>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>>>>>>
>>>>>> Hello,
>>>>>> I have a 2 node couchdb 2.0 cluster setup to start testing things.
It has been running great until I went to replicate a current db into the cluster from 1.6.1.
The replication locks up and fails and both nodes start spitting out a bunch of repeating
log lines indicating something is crashing. After further inspection, it seems the problem
occurs when the replication hits the _design docs, all of which are written in coffeescript.
>>>>>>
>>>>>> I switched to just trying to create a simple coffeescript design
doc via fauxton and via curl and I get the same process crashing errors. I have tried taking
a javascript design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>>>>>
>>>>>> This is all after changing the query server definition for coffeescript
to point to the file included. By default, the config points to ./share/server/main-coffee.js
which is not included in the release. I have changed it to ./share/server/coffee-script.js
which is included. Not sure if that was correct or not, but seemed to match what was done
in previous releases and I couldn't find much info in searches relating to coffeescript specific
config.
>>>>>>
>>>>>> Config on both nodes is the same.
>>>>>>
>>>>>> For testing purposes, here is the design doc I am testing with and
the command used to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>>>>>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>>>>>> {"error":"unknown_error","reason":"undefined"}
>>>>>> root@stage.cdb-n1:~ #
>>>>>>
>>>>>> simple_test.json:
>>>>>> root@stage.cdb-n1:~ # cat /simple_test.json
>>>>>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n
emit doc._conflicts, null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>>>>>
>>>>>> The errors I see in the logs on both servers as soon as I try to
save the design doc with a coffeescript view:
>>>>>>
>>>>>> Node 1
>>>>>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 cache miss for admin
>>>>>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 no record of user admin
>>>>>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process Start :: #Port<0.12902>
>>>>>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17799.31> died normal
>>>>>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>>>>>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process Start :: #Port<0.12903>
>>>>>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17809.31> died normal
>>>>>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>>>>>
>>>>>> Node 2
>>>>>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process Start :: #Port<0.7040>
>>>>>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3683.1> died normal
>>>>>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>>>>>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process Start :: #Port<0.7082>
>>>>>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3687.1> died normal
>>>>>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>>>>>
>>>>>> couchdb is started via systemd and I am not seeing anything in the
log from standard out/error when this happens. As you can see I turned up the logging to debug
and just not getting any good info. Run out of ideas to try to get more info or resolve this.
>>>>>>
>>>>>> I'm not sure if I am running into a configuration error, setup error,
install error or a bug. Any help on this would be appreciated. I can supply any additional
info as needed as this is a testing cluster and not in production yet.
>>>>>>
>>>>>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed:
1:19.1-1)
>>>>>>
>>>>>> Thanks
>>>>>> Brian

The road to 2.0 was long and unfortunately a number of things slipped us by. I think you're
the first to try coffeescript on 2.0, that's all. We know coffeescript _works_ because we
have tests for it, and those tests can find main-coffee.js in the source tree. The slip was
failing to copy it into the 'make release' output only.
B.
> On 7 Dec 2016, at 19:34, Brian Lanier <brianl@amco.me> wrote:
>
> Hi,
> I saw your fix and it worked for me. I was kind of hoping for some sort of bug as I had
run out of ideas to try and places to look. For now, its an easy manual fix for my test cluster.
I was able to fully replicate my previous db from 1.6.1 into 2.0.0 and can continue testing/learning.
>
> Other than this, its been pretty good minus a few issues with documentation on setup
that have either been addressed or already have an issue open. Mainly the not well documented
way to require users for chtppd and wanting to lock down ports and access better via the bind
address. I see there are changes coming along those lines anyway. As 2.0 matures, I hope to
see some of the config I need migrated from direct erlang config via environment or via the
vm.args file and into couchdb config directly.
>
> Thanks for the quick fix and response on this. Was starting to wonder if couchdb 2.0
was not ready for our needs or if we were doing something extremely weird with coffeescript.
>
> Brian
>
> On 12/7/16 11:22 AM, Robert Samuel Newson wrote:
>> Hi Brian,
>>
>> I got there first. Fix is applied to master and will be in the next release. It's
as you say, it's the other .js file that's needed.
>>
>> B.
>>
>>> On 7 Dec 2016, at 18:45, Brian Lanier <brianl@amco.me> wrote:
>>>
>>> Hi Jan,
>>> I went to open an issue and found one already created. Don't know if it was because
of this email or total coincidence. I made the change manually and copied the main-coffee.js
from the source directory to my release directory and it looks like it resolved my issues.
>>>
>>> So looks like this will resolve my issue. Should I add a comment to the issue
or is that not necessary?
>>>
>>> https://issues.apache.org/jira/browse/COUCHDB-3252
>>>
>>> Thanks
>>> Brian
>>>
>>> On 12/7/16 1:26 AM, Jan Lehnardt wrote:
>>>> Heya Brian,
>>>>
>>>> this looks serious,
>>>>
>>>> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB so
we can track this?
>>>>
>>>> Thank you!
>>>> Best
>>>> Jan
>>>> --
>>>>
>>>>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>>>>>
>>>>> Hello,
>>>>> I have a 2 node couchdb 2.0 cluster setup to start testing things. It
has been running great until I went to replicate a current db into the cluster from 1.6.1.
The replication locks up and fails and both nodes start spitting out a bunch of repeating
log lines indicating something is crashing. After further inspection, it seems the problem
occurs when the replication hits the _design docs, all of which are written in coffeescript.
>>>>>
>>>>> I switched to just trying to create a simple coffeescript design doc
via fauxton and via curl and I get the same process crashing errors. I have tried taking a
javascript design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>>>>
>>>>> This is all after changing the query server definition for coffeescript
to point to the file included. By default, the config points to ./share/server/main-coffee.js
which is not included in the release. I have changed it to ./share/server/coffee-script.js
which is included. Not sure if that was correct or not, but seemed to match what was done
in previous releases and I couldn't find much info in searches relating to coffeescript specific
config.
>>>>>
>>>>> Config on both nodes is the same.
>>>>>
>>>>> For testing purposes, here is the design doc I am testing with and the
command used to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>>>>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>>>>> {"error":"unknown_error","reason":"undefined"}
>>>>> root@stage.cdb-n1:~ #
>>>>>
>>>>> simple_test.json:
>>>>> root@stage.cdb-n1:~ # cat /simple_test.json
>>>>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n
emit doc._conflicts, null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>>>>
>>>>> The errors I see in the logs on both servers as soon as I try to save
the design doc with a coffeescript view:
>>>>>
>>>>> Node 1
>>>>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 cache miss for admin
>>>>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 no record of user admin
>>>>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process Start :: #Port<0.12902>
>>>>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17799.31> died normal
>>>>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>>>>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process Start :: #Port<0.12903>
>>>>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17809.31> died normal
>>>>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>>>>
>>>>> Node 2
>>>>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process Start :: #Port<0.7040>
>>>>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3683.1> died normal
>>>>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>>>>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process Start :: #Port<0.7082>
>>>>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3687.1> died normal
>>>>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>>>>
>>>>> couchdb is started via systemd and I am not seeing anything in the log
from standard out/error when this happens. As you can see I turned up the logging to debug
and just not getting any good info. Run out of ideas to try to get more info or resolve this.
>>>>>
>>>>> I'm not sure if I am running into a configuration error, setup error,
install error or a bug. Any help on this would be appreciated. I can supply any additional
info as needed as this is a testing cluster and not in production yet.
>>>>>
>>>>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed:
1:19.1-1)
>>>>>
>>>>> Thanks
>>>>> Brian
>

Hi,
I saw your fix and it worked for me. I was kind of hoping for some sort
of bug as I had run out of ideas to try and places to look. For now, its
an easy manual fix for my test cluster. I was able to fully replicate my
previous db from 1.6.1 into 2.0.0 and can continue testing/learning.
Other than this, its been pretty good minus a few issues with
documentation on setup that have either been addressed or already have
an issue open. Mainly the not well documented way to require users for
chtppd and wanting to lock down ports and access better via the bind
address. I see there are changes coming along those lines anyway. As 2.0
matures, I hope to see some of the config I need migrated from direct
erlang config via environment or via the vm.args file and into couchdb
config directly.
Thanks for the quick fix and response on this. Was starting to wonder if
couchdb 2.0 was not ready for our needs or if we were doing something
extremely weird with coffeescript.
Brian
On 12/7/16 11:22 AM, Robert Samuel Newson wrote:
> Hi Brian,
>
> I got there first. Fix is applied to master and will be in the next release. It's as
you say, it's the other .js file that's needed.
>
> B.
>
>> On 7 Dec 2016, at 18:45, Brian Lanier <brianl@amco.me> wrote:
>>
>> Hi Jan,
>> I went to open an issue and found one already created. Don't know if it was because
of this email or total coincidence. I made the change manually and copied the main-coffee.js
from the source directory to my release directory and it looks like it resolved my issues.
>>
>> So looks like this will resolve my issue. Should I add a comment to the issue or
is that not necessary?
>>
>> https://issues.apache.org/jira/browse/COUCHDB-3252
>>
>> Thanks
>> Brian
>>
>> On 12/7/16 1:26 AM, Jan Lehnardt wrote:
>>> Heya Brian,
>>>
>>> this looks serious,
>>>
>>> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB so we
can track this?
>>>
>>> Thank you!
>>> Best
>>> Jan
>>> --
>>>
>>>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>>>>
>>>> Hello,
>>>> I have a 2 node couchdb 2.0 cluster setup to start testing things. It has
been running great until I went to replicate a current db into the cluster from 1.6.1. The
replication locks up and fails and both nodes start spitting out a bunch of repeating log
lines indicating something is crashing. After further inspection, it seems the problem occurs
when the replication hits the _design docs, all of which are written in coffeescript.
>>>>
>>>> I switched to just trying to create a simple coffeescript design doc via
fauxton and via curl and I get the same process crashing errors. I have tried taking a javascript
design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>>>
>>>> This is all after changing the query server definition for coffeescript to
point to the file included. By default, the config points to ./share/server/main-coffee.js
which is not included in the release. I have changed it to ./share/server/coffee-script.js
which is included. Not sure if that was correct or not, but seemed to match what was done
in previous releases and I couldn't find much info in searches relating to coffeescript specific
config.
>>>>
>>>> Config on both nodes is the same.
>>>>
>>>> For testing purposes, here is the design doc I am testing with and the command
used to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>>>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>>>> {"error":"unknown_error","reason":"undefined"}
>>>> root@stage.cdb-n1:~ #
>>>>
>>>> simple_test.json:
>>>> root@stage.cdb-n1:~ # cat /simple_test.json
>>>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n emit
doc._conflicts, null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>>>
>>>> The errors I see in the logs on both servers as soon as I try to save the
design doc with a coffeescript view:
>>>>
>>>> Node 1
>>>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 cache miss for admin
>>>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 no record of user admin
>>>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process Start :: #Port<0.12902>
>>>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0> --------
couch_proc_manager <0.17799.31> died normal
>>>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>>>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process Start :: #Port<0.12903>
>>>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0> --------
couch_proc_manager <0.17809.31> died normal
>>>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>>>
>>>> Node 2
>>>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process Start :: #Port<0.7040>
>>>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0> --------
couch_proc_manager <0.3683.1> died normal
>>>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>>>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process Start :: #Port<0.7082>
>>>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0> --------
couch_proc_manager <0.3687.1> died normal
>>>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>>>
>>>> couchdb is started via systemd and I am not seeing anything in the log from
standard out/error when this happens. As you can see I turned up the logging to debug and
just not getting any good info. Run out of ideas to try to get more info or resolve this.
>>>>
>>>> I'm not sure if I am running into a configuration error, setup error, install
error or a bug. Any help on this would be appreciated. I can supply any additional info as
needed as this is a testing cluster and not in production yet.
>>>>
>>>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed:
1:19.1-1)
>>>>
>>>> Thanks
>>>> Brian

Hi Brian,
I got there first. Fix is applied to master and will be in the next release. It's as you say,
it's the other .js file that's needed.
B.
> On 7 Dec 2016, at 18:45, Brian Lanier <brianl@amco.me> wrote:
>
> Hi Jan,
> I went to open an issue and found one already created. Don't know if it was because of
this email or total coincidence. I made the change manually and copied the main-coffee.js
from the source directory to my release directory and it looks like it resolved my issues.
>
> So looks like this will resolve my issue. Should I add a comment to the issue or is that
not necessary?
>
> https://issues.apache.org/jira/browse/COUCHDB-3252
>
> Thanks
> Brian
>
> On 12/7/16 1:26 AM, Jan Lehnardt wrote:
>> Heya Brian,
>>
>> this looks serious,
>>
>> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB so we can
track this?
>>
>> Thank you!
>> Best
>> Jan
>> --
>>
>>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>>>
>>> Hello,
>>> I have a 2 node couchdb 2.0 cluster setup to start testing things. It has been
running great until I went to replicate a current db into the cluster from 1.6.1. The replication
locks up and fails and both nodes start spitting out a bunch of repeating log lines indicating
something is crashing. After further inspection, it seems the problem occurs when the replication
hits the _design docs, all of which are written in coffeescript.
>>>
>>> I switched to just trying to create a simple coffeescript design doc via fauxton
and via curl and I get the same process crashing errors. I have tried taking a javascript
design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>>
>>> This is all after changing the query server definition for coffeescript to point
to the file included. By default, the config points to ./share/server/main-coffee.js which
is not included in the release. I have changed it to ./share/server/coffee-script.js which
is included. Not sure if that was correct or not, but seemed to match what was done in previous
releases and I couldn't find much info in searches relating to coffeescript specific config.
>>>
>>> Config on both nodes is the same.
>>>
>>> For testing purposes, here is the design doc I am testing with and the command
used to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>>> {"error":"unknown_error","reason":"undefined"}
>>> root@stage.cdb-n1:~ #
>>>
>>> simple_test.json:
>>> root@stage.cdb-n1:~ # cat /simple_test.json
>>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n emit doc._conflicts,
null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>>
>>> The errors I see in the logs on both servers as soon as I try to save the design
doc with a coffeescript view:
>>>
>>> Node 1
>>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
cache miss for admin
>>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
no record of user admin
>>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31> --------
OS Process Start :: #Port<0.12902>
>>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31> --------
OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0> --------
couch_proc_manager <0.17799.31> died normal
>>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31> --------
OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31> --------
OS Process Start :: #Port<0.12903>
>>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31> --------
OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0> --------
couch_proc_manager <0.17809.31> died normal
>>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31> --------
OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>>
>>> Node 2
>>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1> --------
OS Process Start :: #Port<0.7040>
>>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1> --------
OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0> --------
couch_proc_manager <0.3683.1> died normal
>>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1> --------
OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1> --------
OS Process Start :: #Port<0.7082>
>>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1> --------
OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0> --------
couch_proc_manager <0.3687.1> died normal
>>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1> --------
OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>>
>>> couchdb is started via systemd and I am not seeing anything in the log from standard
out/error when this happens. As you can see I turned up the logging to debug and just not
getting any good info. Run out of ideas to try to get more info or resolve this.
>>>
>>> I'm not sure if I am running into a configuration error, setup error, install
error or a bug. Any help on this would be appreciated. I can supply any additional info as
needed as this is a testing cluster and not in production yet.
>>>
>>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed: 1:19.1-1)
>>>
>>> Thanks
>>> Brian
>

Hi Jan,
I went to open an issue and found one already created. Don't know if it
was because of this email or total coincidence. I made the change
manually and copied the main-coffee.js from the source directory to my
release directory and it looks like it resolved my issues.
So looks like this will resolve my issue. Should I add a comment to the
issue or is that not necessary?
https://issues.apache.org/jira/browse/COUCHDB-3252
Thanks
Brian
On 12/7/16 1:26 AM, Jan Lehnardt wrote:
> Heya Brian,
>
> this looks serious,
>
> could you open an issue on http://issues.apache.org/jira/browse/COUCHDB so we can track
this?
>
> Thank you!
> Best
> Jan
> --
>
>> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>>
>> Hello,
>> I have a 2 node couchdb 2.0 cluster setup to start testing things. It has been running
great until I went to replicate a current db into the cluster from 1.6.1. The replication
locks up and fails and both nodes start spitting out a bunch of repeating log lines indicating
something is crashing. After further inspection, it seems the problem occurs when the replication
hits the _design docs, all of which are written in coffeescript.
>>
>> I switched to just trying to create a simple coffeescript design doc via fauxton
and via curl and I get the same process crashing errors. I have tried taking a javascript
design doc that is entered into a test db and just changing the language to coffeescript.
This causes the error when I would expect either validation errors or for the design doc to
crash when trying to use it. I can create an empty design doc with the language set to coffeescript
and this will save, but it has no views or anything else.
>>
>> This is all after changing the query server definition for coffeescript to point
to the file included. By default, the config points to ./share/server/main-coffee.js which
is not included in the release. I have changed it to ./share/server/coffee-script.js which
is included. Not sure if that was correct or not, but seemed to match what was done in previous
releases and I couldn't find much info in searches relating to coffeescript specific config.
>>
>> Config on both nodes is the same.
>>
>> For testing purposes, here is the design doc I am testing with and the command used
to insert the doc: (Same file and command worked on couchdb 1.6.1 server)
>> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test
-d @/simple_test.json
>> {"error":"unknown_error","reason":"undefined"}
>> root@stage.cdb-n1:~ #
>>
>> simple_test.json:
>> root@stage.cdb-n1:~ # cat /simple_test.json
>> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n emit doc._conflicts,
null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>>
>> The errors I see in the logs on both servers as soon as I try to save the design
doc with a coffeescript view:
>>
>> Node 1
>> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
cache miss for admin
>> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
no record of user admin
>> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31> --------
OS Process Start :: #Port<0.12902>
>> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31> --------
OS Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0> -------- couch_proc_manager
<0.17799.31> died normal
>> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31> --------
OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
>> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31> --------
OS Process Start :: #Port<0.12903>
>> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31> --------
OS Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0> -------- couch_proc_manager
<0.17809.31> died normal
>> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31> --------
OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>>
>> Node 2
>> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1> --------
OS Process Start :: #Port<0.7040>
>> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1> --------
OS Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0> -------- couch_proc_manager
<0.3683.1> died normal
>> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1> --------
OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
>> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1> --------
OS Process Start :: #Port<0.7082>
>> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1> --------
OS Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
>> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0> -------- couch_proc_manager
<0.3687.1> died normal
>> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1> --------
OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>>
>> couchdb is started via systemd and I am not seeing anything in the log from standard
out/error when this happens. As you can see I turned up the logging to debug and just not
getting any good info. Run out of ideas to try to get more info or resolve this.
>>
>> I'm not sure if I am running into a configuration error, setup error, install error
or a bug. Any help on this would be appreciated. I can supply any additional info as needed
as this is a testing cluster and not in production yet.
>>
>> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed: 1:19.1-1)
>>
>> Thanks
>> Brian

Heya Brian,
this looks serious,
could you open an issue on http://issues.apache.org/jira/browse/COUCHDB so we can track this?
Thank you!
Best
Jan
--
> On 6 Dec 2016, at 20:45, Brian Lanier <brianl@amco.me> wrote:
>
> Hello,
> I have a 2 node couchdb 2.0 cluster setup to start testing things. It has been running
great until I went to replicate a current db into the cluster from 1.6.1. The replication
locks up and fails and both nodes start spitting out a bunch of repeating log lines indicating
something is crashing. After further inspection, it seems the problem occurs when the replication
hits the _design docs, all of which are written in coffeescript.
>
> I switched to just trying to create a simple coffeescript design doc via fauxton and
via curl and I get the same process crashing errors. I have tried taking a javascript design
doc that is entered into a test db and just changing the language to coffeescript. This causes
the error when I would expect either validation errors or for the design doc to crash when
trying to use it. I can create an empty design doc with the language set to coffeescript and
this will save, but it has no views or anything else.
>
> This is all after changing the query server definition for coffeescript to point to the
file included. By default, the config points to ./share/server/main-coffee.js which is not
included in the release. I have changed it to ./share/server/coffee-script.js which is included.
Not sure if that was correct or not, but seemed to match what was done in previous releases
and I couldn't find much info in searches relating to coffeescript specific config.
>
> Config on both nodes is the same.
>
> For testing purposes, here is the design doc I am testing with and the command used to
insert the doc: (Same file and command worked on couchdb 1.6.1 server)
> curl -X PUT http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test -d @/simple_test.json
> {"error":"unknown_error","reason":"undefined"}
> root@stage.cdb-n1:~ #
>
> simple_test.json:
> root@stage.cdb-n1:~ # cat /simple_test.json
> {"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n emit doc._conflicts,
null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
>
> The errors I see in the logs on both servers as soon as I try to save the design doc
with a coffeescript view:
>
> Node 1
> debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
cache miss for admin
> [debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31> 79e07a0d50
no record of user admin
> [debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31> -------- OS
Process Start :: #Port<0.12902>
> [debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31> -------- OS
Process #Port<0.12902> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
> [info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0> -------- couch_proc_manager
<0.17799.31> died normal
> [error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31> -------- OS
Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
> [debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31> -------- OS
Process Start :: #Port<0.12903>
> [debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31> -------- OS
Process #Port<0.12903> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
> [info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0> -------- couch_proc_manager
<0.17809.31> died normal
> [error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31> -------- OS
Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
>
> Node 2
> [debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1> -------- OS
Process Start :: #Port<0.7040>
> [debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1> -------- OS
Process #Port<0.7040> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
> [info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0> -------- couch_proc_manager
<0.3683.1> died normal
> [error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1> -------- OS
Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
> [debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1> -------- OS
Process Start :: #Port<0.7082>
> [debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1> -------- OS
Process #Port<0.7082> Input :: ["reset",{"reduce_limit":true,"timeout":5000}]
> [info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0> -------- couch_proc_manager
<0.3687.1> died normal
> [error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1> -------- OS
Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
>
> couchdb is started via systemd and I am not seeing anything in the log from standard
out/error when this happens. As you can see I turned up the logging to debug and just not
getting any good info. Run out of ideas to try to get more info or resolve this.
>
> I'm not sure if I am running into a configuration error, setup error, install error or
a bug. Any help on this would be appreciated. I can supply any additional info as needed as
this is a testing cluster and not in production yet.
>
> Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe: Installed: 1:19.1-1)
>
> Thanks
> Brian
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

Hi Nicholas,
You've run into a documentation bug on CouchDB 2.0. Sorry about that.
First off, you don't want to be using _config on port 5986. The 5986
endpoint is in the process of being deprecated...and in my opinion
should never be bound to any interface other than loopback (127.0.0.1).
Instead, you want to use the /_node/<nodename>/_config endpoint
on the main 5984 port. The nodename is what you set the node's name to
at install time. If you're not sure what the node name might be, check
the /_membership interface (on port 5984) for a list of nodes that
particular node is aware of.
The reason this API was changed is because in a cluster configuration,
especially one where you have a load balancer in front of the CouchDB
cluster, you have no knowledge of which node you're speaking with when
you hit /_config. Further, CouchDB has no mechanism to ensure consistency
across all nodes when a change is made - remember, we are an AP not a CP
datastore - meaning that a "global" /_config endpoint can't guarantee
that all nodes will make the exact same /_config change consistently
upon a single request. So, we have a global (5984) endpoint that provides
a node-local API.
Hope this helps,
Joan
----- Original Message -----
> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
> To: user@couchdb.apache.org
> Sent: Tuesday, December 6, 2016 5:54:17 AM
> Subject: The _config endpoint
>
> Hello
>
> Something odd has happened with my CouchDB server (or more like, I’ve
> done something which had an unexpected side effect)
>
> I’ve been working through the documentation. At first, I was able to
> add an admin user using the _config endpoint on port 5984 (as per
> the tutorial).
>
> I’ve done something since and now it requires me to use port 5986.
> Not knowing what has caused this change makes me uneasy.
>
> Can anyone throw some light on this?
>
> Many thanks in advance,
>
> Nick
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely
> for the use of the recipient to whom it is addressed. If you are not
> the intended recipient then copying, distribution or other use of
> the information contained is strictly prohibited and you should not
> rely on it. If you have received this email in error please let the
> sender know immediately and delete it from your system(s). Internet
> emails are not necessarily secure. While we take every care,
> Plymouth University accepts no responsibility for viruses and it is
> your responsibility to scan emails and their attachments. Plymouth
> University does not accept responsibility for any changes made after
> it was sent. Nothing in this email or its attachments constitutes an
> order for goods or services unless accompanied by an official order
> form.
>

Hello,
I have a 2 node couchdb 2.0 cluster setup to start testing things. It
has been running great until I went to replicate a current db into the
cluster from 1.6.1. The replication locks up and fails and both nodes
start spitting out a bunch of repeating log lines indicating something
is crashing. After further inspection, it seems the problem occurs when
the replication hits the _design docs, all of which are written in
coffeescript.
I switched to just trying to create a simple coffeescript design doc via
fauxton and via curl and I get the same process crashing errors. I have
tried taking a javascript design doc that is entered into a test db and
just changing the language to coffeescript. This causes the error when I
would expect either validation errors or for the design doc to crash
when trying to use it. I can create an empty design doc with the
language set to coffeescript and this will save, but it has no views or
anything else.
This is all after changing the query server definition for coffeescript
to point to the file included. By default, the config points to
./share/server/main-coffee.js which is not included in the release. I
have changed it to ./share/server/coffee-script.js which is included.
Not sure if that was correct or not, but seemed to match what was done
in previous releases and I couldn't find much info in searches relating
to coffeescript specific config.
Config on both nodes is the same.
For testing purposes, here is the design doc I am testing with and the
command used to insert the doc: (Same file and command worked on couchdb
1.6.1 server)
curl -X PUT
http://admin:hiddenpassword@stage.cdb-n1:5984/bs/_design/simple_test -d
@/simple_test.json
{"error":"unknown_error","reason":"undefined"}
root@stage.cdb-n1:~ #
simple_test.json:
root@stage.cdb-n1:~ # cat /simple_test.json
{"views":{"by_conflicts":{"map":"(doc)->\n if doc._conflicts\n emit
doc._conflicts, null\n"}},"filters":{},"lists":{},"language":"coffeescript"}
The errors I see in the logs on both servers as soon as I try to save
the design doc with a coffeescript view:
Node 1
debug] 2016-12-06T19:27:22.961461Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 cache miss for admin
[debug] 2016-12-06T19:27:22.963456Z cdb-n1@stage.cdb-n1 <0.17765.31>
79e07a0d50 no record of user admin
[debug] 2016-12-06T19:27:22.969784Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process Start :: #Port<0.12902>
[debug] 2016-12-06T19:27:22.970009Z cdb-n1@stage.cdb-n1 <0.17799.31>
-------- OS Process #Port<0.12902> Input ::
["reset",{"reduce_limit":true,"timeout":5000}]
[info] 2016-12-06T19:27:23.014571Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17799.31> died normal
[error] 2016-12-06T19:27:23.014599Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17799.31> :: {os_process_error,{exit_status,0}}
[debug] 2016-12-06T19:27:23.016954Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process Start :: #Port<0.12903>
[debug] 2016-12-06T19:27:23.017185Z cdb-n1@stage.cdb-n1 <0.17809.31>
-------- OS Process #Port<0.12903> Input ::
["reset",{"reduce_limit":true,"timeout":5000}]
[info] 2016-12-06T19:27:23.054046Z cdb-n1@stage.cdb-n1 <0.216.0>
-------- couch_proc_manager <0.17809.31> died normal
[error] 2016-12-06T19:27:23.054136Z cdb-n1@stage.cdb-n1 <0.17789.31>
-------- OS Process Error <0.17809.31> :: {os_process_error,{exit_status,0}}
Node 2
[debug] 2016-12-06T19:27:22.978069Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process Start :: #Port<0.7040>
[debug] 2016-12-06T19:27:22.986184Z cdb-n2@stage.cdb-n2 <0.3683.1>
-------- OS Process #Port<0.7040> Input ::
["reset",{"reduce_limit":true,"timeout":5000}]
[info] 2016-12-06T19:27:23.051441Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3683.1> died normal
[error] 2016-12-06T19:27:23.051560Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3683.1> :: {os_process_error,{exit_status,0}}
[debug] 2016-12-06T19:27:23.054276Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process Start :: #Port<0.7082>
[debug] 2016-12-06T19:27:23.054564Z cdb-n2@stage.cdb-n2 <0.3687.1>
-------- OS Process #Port<0.7082> Input ::
["reset",{"reduce_limit":true,"timeout":5000}]
[info] 2016-12-06T19:27:23.095047Z cdb-n2@stage.cdb-n2 <0.216.0>
-------- couch_proc_manager <0.3687.1> died normal
[error] 2016-12-06T19:27:23.095175Z cdb-n2@stage.cdb-n2 <0.3681.1>
-------- OS Process Error <0.3687.1> :: {os_process_error,{exit_status,0}}
couchdb is started via systemd and I am not seeing anything in the log
from standard out/error when this happens. As you can see I turned up
the logging to debug and just not getting any good info. Run out of
ideas to try to get more info or resolve this.
I'm not sure if I am running into a configuration error, setup error,
install error or a bug. Any help on this would be appreciated. I can
supply any additional info as needed as this is a testing cluster and
not in production yet.
Running on Ubuntu 16.04 using Erlang/OTP 19 (erlang-base-hipe:
Installed: 1:19.1-1)
Thanks
Brian

Re: Best practise for authentication of users"bill2@ezinvoice.com" <bill2@ezinvoice.com>urn:uuid:%3c746A1029-D14B-4B58-A9BC-3652C3B3B5F3@ezinvoice-com%3e2016-12-06T18:17:57Z

You might want to look into using PouchDB with the User authentication plugin for PouchDB and
CouchDB. That’s really a pretty great option and offers a lot more that can make your development
easier.
https://pouchdb.com
https://github.com/nolanlawson/pouchdb-authentication
Kindest Regards,
Bill Stephenson
Tech Support
www.ezInvoice.com <http://www.ezinvoice.com/>
1-417-546-8390
> On Dec 5, 2016, at 5:30 AM, Nicholas Outram <nicholas.outram@plymouth.ac.uk> wrote:
>
> Hi
>
> Thanks Martin. I’ll take a look at those links.
>
> I’ve since understood that the CouchDB users are to authenticate at database level,
and not document (which is fine, as long as I know). Right now the option I’m considering
is to use Kituta and create a middleware layer to abstract away the creation of users and
authentication, plus perform the hashing of passwords etc.. Not sure where this leaves me
with "Offline First”.
>
> Nick
>
>
>
>
> On 5 Dec 2016, at 09:49, Martin Broerse <martin.broerse@gmail.com<mailto:martin.broerse@gmail.com>>
wrote:
>
> Hi Nick,
>
> You can use https://github.com/gr2m/couchdb-user-management-app to create
> users. We use https://github.com/martinic/ember-simple-auth-pouch to auth
> users without middleware. Example: https://bloggr.exmer.com/ (
> https://github.com/broerse/ember-cli-blog )
> We still need something for password reset but are trying to solve this
> last part with OpenWhisk.
>
> - Martin
>
>
> On Mon, Dec 5, 2016 at 10:05 AM, Nicholas Outram <
> nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>> wrote:
>
> I’m new to CouchDB, and much more accustomed to relational databases, so
> please excuse any naivety in this question.
>
> I’m going to dive right in a build an iOS app using CouchDB instead of
> iCloud, but before I do so, I’d just like to clarify a few fundamentals if
> I may:
>
> The app is a simple idea, designed to help management of large classes in
> University:
>
> A tutor creates a classroom session with a unique session id; students
> sign in and join the session using the session id; when students have a
> question, they tap a button (join the queue) - the teacher(s) can then help
> students in order (so it’s fair etc..).
>
> 1. I'm assuming the client app will connect directly to CouchDB, as there
> is little motivation to write any middleware - unless I’m missing something
> here?
>
> 2. What is the best practise for managing users and sign-in? There is the
> notion of ‘users’ in couch, but I’m unclear where they fit into the greater
> scheme of things. For a traditional middleware + SQL server, there would
> typically be one database user with imposed limited privileges (for
> security, no drop table etc..), and end-user credentials would be hashed
> and stored in tables by the middleware. Is the model similar in CouchDB, or
> more fluid? I could also use client side encryption and store student
> credentials in a single document (as described in the Wiki).
>
> May thanks in advance,
>
>
> Nick
>
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http:
> //www.plymouth.ac.uk/worldclass<http://www.plymouth.ac.uk/worldclass>>
>
> This email and any files with it are confidential and intended solely for
> the use of the recipient to whom it is addressed. If you are not the
> intended recipient then copying, distribution or other use of the
> information contained is strictly prohibited and you should not rely on it.
> If you have received this email in error please let the sender know
> immediately and delete it from your system(s). Internet emails are not
> necessarily secure. While we take every care, Plymouth University accepts
> no responsibility for viruses and it is your responsibility to scan emails
> and their attachments. Plymouth University does not accept responsibility
> for any changes made after it was sent. Nothing in this email or its
> attachments constitutes an order for goods or services unless accompanied
> by an official order form.
>
>
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely for the use of
the recipient to whom it is addressed. If you are not the intended recipient then copying,
distribution or other use of the information contained is strictly prohibited and you should
not rely on it. If you have received this email in error please let the sender know immediately
and delete it from your system(s). Internet emails are not necessarily secure. While we take
every care, Plymouth University accepts no responsibility for viruses and it is your responsibility
to scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Agreed - that would explain a lot.
Having the wrong port for _config also gave me quite a lot of trouble.
Getting there now :)
On 6 Dec 2016, at 14:13, Karl Helmer <helmer@nmr.mgh.harvard.edu<mailto:helmer@nmr.mgh.harvard.edu>>
wrote:
Hi,
I think one possible reason for why this question comes up fairly
frequently is that if you follow the installation instructions starting
at 2.1 and then keep hitting "next topic", section 2.6, Single-node
Setup, is skipped - it goes from 2.5 -> 3.0.
regards,
Karl
Thank you Joan - indeed I was missing something!
Much appreciated -
Nick
(email / Skype for Business):
nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk><mailto:nicholas.outram@plymouth.ac.uk>
(mobile / iMessage): +44 7540 695741<tel:+44%207540%20695741>
(office): +44 1752 586257<tel:+44%201752%20586257>
(twitter): noutram_at_uop
iTunes U course: iOS Development in Swift:
http://iTunes.com/plymouthswift<http://itunes.com/plymouthswift>
On 5 Dec 2016, at 18:33, Joan Touzet
<wohali@apache.org<mailto:wohali@apache.org>> wrote:
You missed the setup step where you create the _users database:
http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
-Joan
----- Original Message -----
From: "Nicholas Outram"
<nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>>
To: user@couchdb.apache.org<mailto:user@couchdb.apache.org>
Sent: Monday, December 5, 2016 10:42:00 AM
Subject: Creating users - getting back "Database does not exist."
I'm working though the tutorial on CouchDB
http://docs.couchdb.org/en/latest/intro/security.html
I'm at the section "Creating a New User", where is says:
Creating a new user is a very trivial operation. You just need to do
a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
request with the user's data to CouchDB. Let's create a user with
login jan and password apple:
curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"name": "jan", "password": "apple", "roles": [], "type":
"user"}'
When I try this, I get
{"error":"not_found","reason":"Database does not exist."}
I'm missing something here. Can anyone advise?
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely
for the use of the recipient to whom it is addressed. If you are not
the intended recipient then copying, distribution or other use of
the information contained is strictly prohibited and you should not
rely on it. If you have received this email in error please let the
sender know immediately and delete it from your system(s). Internet
emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is
your responsibility to scan emails and their attachments. Plymouth
University does not accept responsibility for any changes made after
it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order
form.
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for
the use of the recipient to whom it is addressed. If you are not the
intended recipient then copying, distribution or other use of the
information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know
immediately and delete it from your system(s). Internet emails are not
necessarily secure. While we take every care, Plymouth University accepts
no responsibility for viruses and it is your responsibility to scan emails
and their attachments. Plymouth University does not accept responsibility
for any changes made after it was sent. Nothing in this email or its
attachments constitutes an order for goods or services unless accompanied
by an official order form.
--
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
helmer@nmr.mgh.harvard.edu<mailto:helmer@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.
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Hi,
I think one possible reason for why this question comes up fairly
frequently is that if you follow the installation instructions starting
at 2.1 and then keep hitting "next topic", section 2.6, Single-node
Setup, is skipped - it goes from 2.5 -> 3.0.
regards,
Karl
> Thank you Joan - indeed I was missing something!
>
> Much appreciated -
>
> Nick
>
> (email / Skype for Business):
> nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>
> (mobile / iMessage): +44 7540 695741<tel:+44%207540%20695741>
> (office): +44 1752 586257<tel:+44%201752%20586257>
> (twitter): noutram_at_uop
>
> iTunes U course: iOS Development in Swift:
> http://iTunes.com/plymouthswift<http://itunes.com/plymouthswift>
>
> On 5 Dec 2016, at 18:33, Joan Touzet
> <wohali@apache.org<mailto:wohali@apache.org>> wrote:
>
> You missed the setup step where you create the _users database:
>
> http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
>
> -Joan
>
> ----- Original Message -----
> From: "Nicholas Outram"
> <nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>>
> To: user@couchdb.apache.org<mailto:user@couchdb.apache.org>
> Sent: Monday, December 5, 2016 10:42:00 AM
> Subject: Creating users - getting back "Database does not exist."
>
> I'm working though the tutorial on CouchDB
>
> http://docs.couchdb.org/en/latest/intro/security.html
>
> I'm at the section "Creating a New User", where is says:
>
> Creating a new user is a very trivial operation. You just need to do
> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
> request with the user's data to CouchDB. Let's create a user with
> login jan and password apple:
>
> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
> -H "Accept: application/json" \
> -H "Content-Type: application/json" \
> -d '{"name": "jan", "password": "apple", "roles": [], "type":
> "user"}'
>
> When I try this, I get
>
> {"error":"not_found","reason":"Database does not exist."}
>
>
>
> I'm missing something here. Can anyone advise?
>
> Nick
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely
> for the use of the recipient to whom it is addressed. If you are not
> the intended recipient then copying, distribution or other use of
> the information contained is strictly prohibited and you should not
> rely on it. If you have received this email in error please let the
> sender know immediately and delete it from your system(s). Internet
> emails are not necessarily secure. While we take every care,
> Plymouth University accepts no responsibility for viruses and it is
> your responsibility to scan emails and their attachments. Plymouth
> University does not accept responsibility for any changes made after
> it was sent. Nothing in this email or its attachments constitutes an
> order for goods or services unless accompanied by an official order
> form.
>
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely for
> the use of the recipient to whom it is addressed. If you are not the
> intended recipient then copying, distribution or other use of the
> information contained is strictly prohibited and you should not rely on
> it. If you have received this email in error please let the sender know
> immediately and delete it from your system(s). Internet emails are not
> necessarily secure. While we take every care, Plymouth University accepts
> no responsibility for viruses and it is your responsibility to scan emails
> and their attachments. Plymouth University does not accept responsibility
> for any changes made after it was sent. Nothing in this email or its
> attachments constitutes an order for goods or services unless accompanied
> by an official order form.
>
--
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
helmer@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.

Hello
Something odd has happened with my CouchDB server (or more like, I’ve done something which
had an unexpected side effect)
I’ve been working through the documentation. At first, I was able to add an admin user using
the _config endpoint on port 5984 (as per the tutorial).
I’ve done something since and now it requires me to use port 5986. Not knowing what has
caused this change makes me uneasy.
Can anyone throw some light on this?
Many thanks in advance,
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Thank you Joan - indeed I was missing something!
Much appreciated -
Nick
(email / Skype for Business): nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>
(mobile / iMessage): +44 7540 695741<tel:+44%207540%20695741>
(office): +44 1752 586257<tel:+44%201752%20586257>
(twitter): noutram_at_uop
iTunes U course: iOS Development in Swift: http://iTunes.com/plymouthswift<http://itunes.com/plymouthswift>
On 5 Dec 2016, at 18:33, Joan Touzet <wohali@apache.org<mailto:wohali@apache.org>>
wrote:
You missed the setup step where you create the _users database:
http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
-Joan
----- Original Message -----
From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>>
To: user@couchdb.apache.org<mailto:user@couchdb.apache.org>
Sent: Monday, December 5, 2016 10:42:00 AM
Subject: Creating users - getting back "Database does not exist."
I'm working though the tutorial on CouchDB
http://docs.couchdb.org/en/latest/intro/security.html
I'm at the section "Creating a New User", where is says:
Creating a new user is a very trivial operation. You just need to do
a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
request with the user's data to CouchDB. Let's create a user with
login jan and password apple:
curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"name": "jan", "password": "apple", "roles": [], "type":
"user"}'
When I try this, I get
{"error":"not_found","reason":"Database does not exist."}
I'm missing something here. Can anyone advise?
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely
for the use of the recipient to whom it is addressed. If you are not
the intended recipient then copying, distribution or other use of
the information contained is strictly prohibited and you should not
rely on it. If you have received this email in error please let the
sender know immediately and delete it from your system(s). Internet
emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is
your responsibility to scan emails and their attachments. Plymouth
University does not accept responsibility for any changes made after
it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order
form.
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

You missed the setup step where you create the _users database:
http://docs.couchdb.org/en/2.0.0/install/index.html#single-node-setup
-Joan
----- Original Message -----
> From: "Nicholas Outram" <nicholas.outram@plymouth.ac.uk>
> To: user@couchdb.apache.org
> Sent: Monday, December 5, 2016 10:42:00 AM
> Subject: Creating users - getting back "Database does not exist."
>
> I’m working though the tutorial on CouchDB
>
> http://docs.couchdb.org/en/latest/intro/security.html
>
> I’m at the section “Creating a New User”, where is says:
>
> Creating a new user is a very trivial operation. You just need to do
> a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
> request with the user’s data to CouchDB. Let’s create a user with
> login jan and password apple:
>
> curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
> -H "Accept: application/json" \
> -H "Content-Type: application/json" \
> -d '{"name": "jan", "password": "apple", "roles": [], "type":
> "user"}'
>
> When I try this, I get
>
> {"error":"not_found","reason":"Database does not exist.”}
>
>
>
> I’m missing something here. Can anyone advise?
>
> Nick
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely
> for the use of the recipient to whom it is addressed. If you are not
> the intended recipient then copying, distribution or other use of
> the information contained is strictly prohibited and you should not
> rely on it. If you have received this email in error please let the
> sender know immediately and delete it from your system(s). Internet
> emails are not necessarily secure. While we take every care,
> Plymouth University accepts no responsibility for viruses and it is
> your responsibility to scan emails and their attachments. Plymouth
> University does not accept responsibility for any changes made after
> it was sent. Nothing in this email or its attachments constitutes an
> order for goods or services unless accompanied by an official order
> form.
>

I’m working though the tutorial on CouchDB
http://docs.couchdb.org/en/latest/intro/security.html
I’m at the section “Creating a New User”, where is says:
Creating a new user is a very trivial operation. You just need to do a PUT<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6>
request with the user’s data to CouchDB. Let’s create a user with login jan and password
apple:
curl -X PUT http://localhost:5984/_users/org.couchdb.user:jan \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"name": "jan", "password": "apple", "roles": [], "type": "user"}'
When I try this, I get
{"error":"not_found","reason":"Database does not exist.”}
I’m missing something here. Can anyone advise?
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Hey there,
it’s great to see people wanting to take initiative for
humanitarian projects. It shows that we are doing things
for the right reasons <3
FWIW, there are a few organisations of the “hack for good”-type.
Any particular names elude me, but this exists ;)
As for the Ebola project in particular, I was part of that and
we wouldn’t have been able to work with outside volunteers. The
pressures in this project were so high, that it required a
dedicated and in-one-office team to make it work at all.
This is just as a perspective, that some of these things can’t
be done in the more traditional open source way, even though
many good open source projects came out of it.
For example:
- https://github.com/eHealthAfrica/couchdb-bootstrap
- http://ehealthafrica.github.io/couchdb-best-practices/
Best
Jan
--
> On 2 Dec 2016, at 18:00, Mr. T <mandinkamohawk@gmail.com> wrote:
>
> Hello,
>
> New here with a dated comment...
>
> IDEA: It would be nice if there was a place online where developers
> could donate time to working on these sorts of projects. I'm thinking
> somewhere where the project dev head could publish a task list, and
> developers who have signed up to be volunteers could commit code.
>
> I personally would love to lend my meager coding skills to a project
> that actually matters (I spend my days writing enterprise stuff so
> that our customers can make more money! It pays the bills but surely
> there's more to life).
>
> Mr. T.
>
>> I’m sure you all get tired of hearing about this, but I don’t! :)
>>
>> Here’s another write-up about how CouchDB played a role in helping with one of
>> the largest humanitarian crises this century: https://medium.com/net-magazine
>> /fighting-ebola-with-javascript-26b48da8f84a
>>
>> This is why I love what we do <3
>>
>> Best
>> Jan
>> --
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/

Re: Best practise for authentication of usersNicholas Outram <nicholas.outram@plymouth.ac.uk>urn:uuid:%3c8D673DED-32A1-418F-9005-A7E8160DA1C8@plymouth-ac-uk%3e2016-12-05T11:30:45Z

Hi
Thanks Martin. I’ll take a look at those links.
I’ve since understood that the CouchDB users are to authenticate at database level, and
not document (which is fine, as long as I know). Right now the option I’m considering is
to use Kituta and create a middleware layer to abstract away the creation of users and authentication,
plus perform the hashing of passwords etc.. Not sure where this leaves me with "Offline First”.
Nick
On 5 Dec 2016, at 09:49, Martin Broerse <martin.broerse@gmail.com<mailto:martin.broerse@gmail.com>>
wrote:
Hi Nick,
You can use https://github.com/gr2m/couchdb-user-management-app to create
users. We use https://github.com/martinic/ember-simple-auth-pouch to auth
users without middleware. Example: https://bloggr.exmer.com/ (
https://github.com/broerse/ember-cli-blog )
We still need something for password reset but are trying to solve this
last part with OpenWhisk.
- Martin
On Mon, Dec 5, 2016 at 10:05 AM, Nicholas Outram <
nicholas.outram@plymouth.ac.uk<mailto:nicholas.outram@plymouth.ac.uk>> wrote:
I’m new to CouchDB, and much more accustomed to relational databases, so
please excuse any naivety in this question.
I’m going to dive right in a build an iOS app using CouchDB instead of
iCloud, but before I do so, I’d just like to clarify a few fundamentals if
I may:
The app is a simple idea, designed to help management of large classes in
University:
A tutor creates a classroom session with a unique session id; students
sign in and join the session using the session id; when students have a
question, they tap a button (join the queue) - the teacher(s) can then help
students in order (so it’s fair etc..).
1. I'm assuming the client app will connect directly to CouchDB, as there
is little motivation to write any middleware - unless I’m missing something
here?
2. What is the best practise for managing users and sign-in? There is the
notion of ‘users’ in couch, but I’m unclear where they fit into the greater
scheme of things. For a traditional middleware + SQL server, there would
typically be one database user with imposed limited privileges (for
security, no drop table etc..), and end-user credentials would be hashed
and stored in tables by the middleware. Is the model similar in CouchDB, or
more fluid? I could also use client side encryption and store student
credentials in a single document (as described in the Wiki).
May thanks in advance,
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http:
//www.plymouth.ac.uk/worldclass<http://www.plymouth.ac.uk/worldclass>>
This email and any files with it are confidential and intended solely for
the use of the recipient to whom it is addressed. If you are not the
intended recipient then copying, distribution or other use of the
information contained is strictly prohibited and you should not rely on it.
If you have received this email in error please let the sender know
immediately and delete it from your system(s). Internet emails are not
necessarily secure. While we take every care, Plymouth University accepts
no responsibility for viruses and it is your responsibility to scan emails
and their attachments. Plymouth University does not accept responsibility
for any changes made after it was sent. Nothing in this email or its
attachments constitutes an order for goods or services unless accompanied
by an official order form.
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Re: Best practise for authentication of usersMartin Broerse <martin.broerse@gmail.com>urn:uuid:%3cCAPimKeMMUEzxm6C8Ae3zoxBz4dq+vh6ABvWxi_zJ21TovXTKew@mail-gmail-com%3e2016-12-05T09:49:15Z

Hi Nick,
You can use https://github.com/gr2m/couchdb-user-management-app to create
users. We use https://github.com/martinic/ember-simple-auth-pouch to auth
users without middleware. Example: https://bloggr.exmer.com/ (
https://github.com/broerse/ember-cli-blog )
We still need something for password reset but are trying to solve this
last part with OpenWhisk.
- Martin
On Mon, Dec 5, 2016 at 10:05 AM, Nicholas Outram <
nicholas.outram@plymouth.ac.uk> wrote:
> I’m new to CouchDB, and much more accustomed to relational databases, so
> please excuse any naivety in this question.
>
> I’m going to dive right in a build an iOS app using CouchDB instead of
> iCloud, but before I do so, I’d just like to clarify a few fundamentals if
> I may:
>
> The app is a simple idea, designed to help management of large classes in
> University:
>
> A tutor creates a classroom session with a unique session id; students
> sign in and join the session using the session id; when students have a
> question, they tap a button (join the queue) - the teacher(s) can then help
> students in order (so it’s fair etc..).
>
> 1. I'm assuming the client app will connect directly to CouchDB, as there
> is little motivation to write any middleware - unless I’m missing something
> here?
>
> 2. What is the best practise for managing users and sign-in? There is the
> notion of ‘users’ in couch, but I’m unclear where they fit into the greater
> scheme of things. For a traditional middleware + SQL server, there would
> typically be one database user with imposed limited privileges (for
> security, no drop table etc..), and end-user credentials would be hashed
> and stored in tables by the middleware. Is the model similar in CouchDB, or
> more fluid? I could also use client side encryption and store student
> credentials in a single document (as described in the Wiki).
>
> May thanks in advance,
>
>
> Nick
>
> ________________________________
> [http://www.plymouth.ac.uk/images/email_footer.gif]<http:
> //www.plymouth.ac.uk/worldclass>
>
> This email and any files with it are confidential and intended solely for
> the use of the recipient to whom it is addressed. If you are not the
> intended recipient then copying, distribution or other use of the
> information contained is strictly prohibited and you should not rely on it.
> If you have received this email in error please let the sender know
> immediately and delete it from your system(s). Internet emails are not
> necessarily secure. While we take every care, Plymouth University accepts
> no responsibility for viruses and it is your responsibility to scan emails
> and their attachments. Plymouth University does not accept responsibility
> for any changes made after it was sent. Nothing in this email or its
> attachments constitutes an order for goods or services unless accompanied
> by an official order form.
>

Re: Best practise for authentication of usersMatthew Buckett <matthew.buckett@it.ox.ac.uk>urn:uuid:%3cCANpZKy4zOS-vPoLN=xBFx7Ak7py1axjz72YwirWeOLtq9ScxSA@mail-gmail-com%3e2016-12-05T09:15:06Z

On 5 December 2016 at 09:05, Nicholas Outram
<nicholas.outram@plymouth.ac.uk> wrote:
>
> 2. What is the best practise for managing users and sign-in? There is the notion of ‘users’
in couch, but I’m unclear where they fit into the greater scheme of things. For a traditional
middleware + SQL server, there would typically be one database user with imposed limited privileges
(for security, no drop table etc..), and end-user credentials would be hashed and stored in
tables by the middleware. Is the model similar in CouchDB, or more fluid? I could also use
client side encryption and store student credentials in a single document (as described in
the Wiki).
Locally we had a working pilot of CouchDB 1.6.1 setup with the
couch_jwt_auth plugin, create_user_db plugin
(https://github.com/buckett/create-user-db). We used https://auth0.com
to create the JWT tokens and integrated that with our local single
sign on solution using OAuth 2. As you suggest this allowed us to not
have anything serverside apart from CouchDB.
If you're storing credentials directly in CouchDB then there's
https://github.com/etrepum/couchperuser which creates the DB when a
new user is created.
--
Matthew Buckett
VLE Developer
WebLearn, Academic IT
IT Services, University of Oxford
13 Banbury Road, OX2 6NN
Tel: 01865 283349

Best practise for authentication of usersNicholas Outram <nicholas.outram@plymouth.ac.uk>urn:uuid:%3c81751730-6DD4-448F-A418-1BEBF059F308@plymouth-ac-uk%3e2016-12-05T09:05:05Z

I’m new to CouchDB, and much more accustomed to relational databases, so please excuse any
naivety in this question.
I’m going to dive right in a build an iOS app using CouchDB instead of iCloud, but before
I do so, I’d just like to clarify a few fundamentals if I may:
The app is a simple idea, designed to help management of large classes in University:
A tutor creates a classroom session with a unique session id; students sign in and join the
session using the session id; when students have a question, they tap a button (join the queue)
- the teacher(s) can then help students in order (so it’s fair etc..).
1. I'm assuming the client app will connect directly to CouchDB, as there is little motivation
to write any middleware - unless I’m missing something here?
2. What is the best practise for managing users and sign-in? There is the notion of ‘users’
in couch, but I’m unclear where they fit into the greater scheme of things. For a traditional
middleware + SQL server, there would typically be one database user with imposed limited privileges
(for security, no drop table etc..), and end-user credentials would be hashed and stored in
tables by the middleware. Is the model similar in CouchDB, or more fluid? I could also use
client side encryption and store student credentials in a single document (as described in
the Wiki).
May thanks in advance,
Nick
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient
to whom it is addressed. If you are not the intended recipient then copying, distribution
or other use of the information contained is strictly prohibited and you should not rely on
it. If you have received this email in error please let the sender know immediately and delete
it from your system(s). Internet emails are not necessarily secure. While we take every care,
Plymouth University accepts no responsibility for viruses and it is your responsibility to
scan emails and their attachments. Plymouth University does not accept responsibility for
any changes made after it was sent. Nothing in this email or its attachments constitutes an
order for goods or services unless accompanied by an official order form.

Thanks Martin, I'll check out that repo and see where I can help
El sáb., 3 de dic. de 2016 a la(s) 08:39, Martin Broerse <
martin.broerse@gmail.com> escribió:
> Mr. T,
>
> You can help with https://github.com/HospitalRun/hospitalrun-frontend to
> get offline first hospital software to the developing world.
>
> - Martin
>
> On Fri, Dec 2, 2016 at 6:00 PM, Mr. T <mandinkamohawk@gmail.com> wrote:
>
> > Hello,
> >
> > New here with a dated comment...
> >
> > IDEA: It would be nice if there was a place online where developers
> > could donate time to working on these sorts of projects. I'm thinking
> > somewhere where the project dev head could publish a task list, and
> > developers who have signed up to be volunteers could commit code.
> >
> > I personally would love to lend my meager coding skills to a project
> > that actually matters (I spend my days writing enterprise stuff so
> > that our customers can make more money! It pays the bills but surely
> > there's more to life).
> >
> > Mr. T.
> >
> > > I’m sure you all get tired of hearing about this, but I don’t! :)
> > >
> > > Here’s another write-up about how CouchDB played a role in helping with
> > one of
> > > the largest humanitarian crises this century: https://medium.com/net-
> > magazine
> > > /fighting-ebola-with-javascript-26b48da8f84a
> > >
> > > This is why I love what we do <3
> > >
> > > Best
> > > Jan
> > > --
> >
>

Hi,
does anybody know this book:
https://www.amazon.de/CouchDB-2-0-Reference-Manual-Team/dp/9888381652
It seems to be just a copy of the online manual at http://docs.couchdb.org
Any recommendations for recent books (including the replication and
mango query features)?
Regards,
Max

Mr. T,
You can help with https://github.com/HospitalRun/hospitalrun-frontend to
get offline first hospital software to the developing world.
- Martin
On Fri, Dec 2, 2016 at 6:00 PM, Mr. T <mandinkamohawk@gmail.com> wrote:
> Hello,
>
> New here with a dated comment...
>
> IDEA: It would be nice if there was a place online where developers
> could donate time to working on these sorts of projects. I'm thinking
> somewhere where the project dev head could publish a task list, and
> developers who have signed up to be volunteers could commit code.
>
> I personally would love to lend my meager coding skills to a project
> that actually matters (I spend my days writing enterprise stuff so
> that our customers can make more money! It pays the bills but surely
> there's more to life).
>
> Mr. T.
>
> > I’m sure you all get tired of hearing about this, but I don’t! :)
> >
> > Here’s another write-up about how CouchDB played a role in helping with
> one of
> > the largest humanitarian crises this century: https://medium.com/net-
> magazine
> > /fighting-ebola-with-javascript-26b48da8f84a
> >
> > This is why I love what we do <3
> >
> > Best
> > Jan
> > --
>