Re: [DISCUSS] Improved CouchDB logo

Dear All! I just want to say that I really like everything about CouchDB, the database, the documentation and the logo. Best, Sinan On 28 October 2014 17:38, Maria wrote: > On Tue, 28 Oct 2014 08:33:13 -0500 > Bryan Green wrote: > > > I noticed you too seem to assume it is a man on the couch?

Re: CouchDB SSL Problems

Hi! A non-answer: For me it works on Ubuntu 13.04 (towards all main browsers) as described in: http://docs.couchdb.org/en/latest/config/http.html#secure-socket-level-options However when I switch to Ubuntu 14.04 I can't get it to work, so on Ubuntu 14.04 I have actually set up an nginx load bal

Re: map function with a helper function

Hi! You may want to take a look at the basics here: http://docs.couchdb.org/en/latest/couchapp/views/index.html and Cloudant has some interactive samples at: https://cloudant.com/for-developers/all_docs/ *Using map*: You may want to emit the letters and use keys to find the docs. *Not using map*

Re: Continous Replications Stopping Unexpectedly

Hi! You may want to take a look at e.g. "Resource Limits" at http://wiki.apache.org/couchdb/Performance . Also the previous discussion thread "Tweaking CouchDB For DB-Per-User" is about the same. Best, Sinan On 9 February 2015 at 16:51, Bill Foshay wrote: > Hi, > > We're experiencing issues

Re: Continous Replications Stopping Unexpectedly

Hi, Another thing you may want to check is that you have enough disk space for compaction. As I recall it needs at least 2x the size of the compacted db size. On 9 Feb 2015 19:59, "Bill Foshay" wrote: > > You may want to take a look at e.g. "Resource Limits" at > > http://wiki.apache.org/couchdb

Re: Continous Replications Stopping Unexpectedly

I have not tried it but I understand that coucdb will crash somehow if there is not enough disk space during compaction. But perhaps you should present some more facts about your installation and environment and some of the gurus can help :) On Monday, February 9, 2015, Bill Foshay wrote: > > A

CouchDB configuration: the {couch_httpd_auth: timeout} parameter & pouchdb-authentication

Hi, Is there a recommended setting of the CouchDB configuration: {couch_httpd_auth: timeout} parameter value when using CouchDB user authentication (login) via the pouchdb-authentication .js library. PROBLEM: The default cookie refresh time is 10 minutes with pouchdb-authentication, and I loose t

Re: problems with replication

Hi! I would try a couple things: (1) Increase connection_timeout to e.g. 18 (3 minutes) (2) Do not use filtered replication on the server sending the data, just make a full replication, and if needed filter the data on the receiving side with a script. Br, Sinan On 6 October 2015 at 13:18,

Re: problems with replication

PS (3) If documents are small I would also set worker_batch_size = 5000 or 1 either in configuration or better just with the individual replication call On 6 October 2015 at 14:37, Sinan Gabel wrote: > Hi! > > I would try a couple things: > > (1) Increase connection_timeout

Re: Got Apache CouchDB?

Hi Robert, Thank you very much for your email. Innova Financial Solutions ApS, Copenhagen, Denmark (ifs.dk) RiskButler.com - Visually oriented financial risk management software service (SaaS) Beta version is being opened up later this week which includes a free user version for private investors

Re: CouchDB crashing with SSL

Sounds good, else place e.g. Nginx with SSL in front of CouchDB. Best, Sinan On 28 April 2016 at 15:05, Raja wrote: > Upgrading to Erlang 18 solved this issue. I can successfully connect from > my browsers as well as Couchbase Lite. > > On Wed, Apr 27, 2016 at 11:28 PM, Raja wrote: > > > Hi >

Re: The state of filtered replication

Hi Stefan, I recognise your description and problem: I also gave up on the server-side performance. With 1.6.1 version of CouchDB I only saw two immediate options: (1) More databases on the server-side to reduce the number of docs per database (2) Simply do the filtering on the client-side in Pou

Re: CouchDB 1.6.1 on Debian 8

Hi! I tried to install 1.x.x on Ubuntu 16.04 Desktop and it failed with roughly the same info as given above. Br, Sinan On 3 June 2016 at 05:32, Frédéric Audon wrote: > > > On 1 Jun 2016, at 7:43, Jan Lehnardt wrote: > > On 01 Jun 2016, at 00:09, Frédéric Audon wrote: >>> >>> >>> Le 31 mai 20

Re: CouchDB 1.6.1 on Debian 8

|d...@couchdb.apache.org|g" \ -e "s|%package_author_name%|The Apache Software Foundation|g" \ -e "s|%package_name%|Apache CouchDB|g" \ -e "s|%version%|1.7.0|g" \ -e "s|%couchdb_command_name%|`echo couchdb | sed 's,x,x,'`|g" > \ ru

Re: CouchDB 1.6.1 on Debian 8

Good, that did it i.e.: touch THANKS CouchDB 1.x.x now works also on Ubuntu 16.04 Desktop. On 3 June 2016 at 16:27, Sinan Gabel wrote: > ... > make[3]: Leaving directory '/usr/local/src/couchdb-1.x.x/src/snappy' > Making all in couchjs-node > make[3]: Entering dir

Re: CouchDB 1.6.1 on Debian 8

Hi! For CouchDB 1.x.x or kind of "1.7.0" on Ubuntu 16.04, I placed an installation script and example configuration file here: https://gist.github.com/SinanGabel/eac83a2f9d0ac64e2c9d4bd936be9313 Br, Sinan On 3 June 2016 at 16:37, Sinan Gabel wrote: > Good, that did it i.

Re: CouchDB 1.6.1 on Debian 8

-recommended texlive-latex-extra texlive-fonts-recommended > texinfo gnupg > > > mkdir -p /usr/local/{lib,etc}/couchdb /usr/local/var/{lib,log,run}/couchdb > /var/lib/couchdb > > > > On 3 Jun 2016, at 18:27, Sinan Gabel wrote: > > Hi! >> >> For Couch

Re: Using couches

Hi Etay, You probably want to look at: https://cloudant.com/ Also possibly want to follow the blog on activitities: https://blog.couchdb.org/ At the "Issue tracker" you can see that there is quite some activity: https://issues.apache.org/jira/browse/CouchDB/?selectedTab=com.atlassian.jira.jira-p

Re: CouchDB 1.6.1 on Debian 8

/local/{lib,etc}/couchdb > > > > > > On 4 Jun 2016, at 12:33, Sinan Gabel wrote: > > > > > Thanks Frédéric, I updated the script with your changes. > > > > > > On 3 June 2016 at 19:23, Frédéric Audon wrote: > > > > > >> ap

Re: Install CouchDB 1.6.5 with Erlang/OTP 19.0

Hi! You may want to try with this version of CouchDB instead: https://github.com/apache/couchdb/archive/1.x.x.zip This version works with e.g. Ubuntu 16.04 and the corresponding default Erlang version for Ubuntu 16.04. Here are the installation details (use couchdb_1.7.0_install.sh

Replication breaks to target on localhost single-node 2.0 install

Hi! I am testing couchdb 2.x (version commit 20 Dec. 2016), and have made a single node install on Ubuntu Desktop 16.04. I also have a 1.x.x (later than 1.6.1 but not the big couchdb version) cloud-based pair of couchdb's with nginx ssl load balancer in front of the two cloud-based couchdb's. The

Re: What does " = " mean under [admins] ?

Hi! ; You can add more admin accounts with more 'username = password' lines. Don't forget to restart CouchDB after changing this. [admins] your_admin_username = your_admin_password for example jasmine = 1234 For explanation see: https://github.com/nolanlawson/pouchdb-authentication#first-step-d

[couch_peruser] not working on single-node

Hi! Tried* [couch_peruser] *configuration setup on couchdb 2.x (latest version) on Ubuntu 16.04 Desktop, and it does not work. Perhaps it is working with the cluster config.? Br, Sinan

Re: [couch_peruser] not working on single-node

nal Message ----- > > From: "Sinan Gabel" > > To: user@couchdb.apache.org > > Sent: Friday, December 23, 2016 5:31:26 AM > > Subject: [couch_peruser] not working on single-node > > > > Hi! > > > > Tried* [couch_peruser] *configuration setup o

Re: Replication breaks to target on localhost single-node 2.0 install

cause and resolve. Anyway, case closed! Thanks! PS I have made a full description of the CouchDB 2.0 Cluster setup I am using on Ubuntu 16.04 servers: https://gist.github.com/SinanGabel/eac83a2f9d0ac64e2c9d4bd936be9313 On 22 December 2016 at 12:50, Sinan Gabel wrote: > Hi! > > I a

Re: Replication breaks to target on localhost single-node 2.0 install

Jan 5, 2017, at 9:29 AM, Sinan Gabel wrote: > > > > Hi! > > > > The problem I experienced with replication break, using CouchDB 2.0 > > single-node on Desktop against CouchDB 1.x.x. through nginx on cloud, is > > solved when upgrading to CouchDB 2.0 cluster through

Re: Problems with continuous replication while using NginX as an SSL proxy for a subdirectory

Hi, Looks fine except there is a missing: proxy_set_header X-Forwarded-Ssl on; in the _changes part. I would start by removing the rewrite and the SSL and test, then add the SSL and test, and finally add the rewrite and test. Best regards, On 12 January 2017 at 00:07, Doug Snyder wrote: > I

Re: CouchDB 2.0 and centos 6.8 and rebar error

Hi Brian, I cannot say if the following will solve your problem but I also had some problems at the "make" step with Ubuntu 16.04, and this was solved by doing the following prior to doing the "make release". touch THANKS touch /usr/lib/erlang/man/man1/x86_64-linux-gnu-gcov-tool.1.gz touch /usr/l

Re: Looking for public-data CouchDB DBs

Hi, how many docs would you like in the db, and should it be a db that is static i.e. not updated or a db that is updated periodically? Br, Sinan On 19 April 2017 at 05:20, Joan Touzet wrote: > Hi there everyone, > > I'm testing a new CouchDB 1.x -> 2.x upgrade tool (to be included in > the Cou

Re: 100% CPU on only a single node because of couchjs processes

Hi, I am also experiencing 100% CPU usage, not sure why, it happens suddenly and continues until couchdb is restarted. CouchDB version being used is also single-node (n:3, q:8) and v. 2.1.0-6c4def6 on Ubuntu 16.04 2 vCPU's and 4.5 GB memory. On 4 December 2017 at 19:46, Geoffrey Cox wrote: > Hi

Re: 100% CPU on only a single node because of couchjs processes

Hi, I do not have a solution but also experiencing the 100% CPU usage. Here's a .png screen shot of the processes running (my case): On 10 December 2017 at 02:00, Geoffrey Cox wrote: > Well, I'm back at this and here is the latest info and I think it may be > related to writes and the _global_

Re: 100% CPU on only a single node because of couchjs processes

PS I have just now upgraded to latest couchdb clustered version, I will see if that solves the 100% CPU usage problem. On 10 December 2017 at 15:28, Sinan Gabel wrote: > Hi, > > I do not have a solution but also experiencing the 100% CPU usage. Here's > a .png screen shot

Re: 100% CPU on only a single node because of couchjs processes

10 December 2017 at 16:50, Sinan Gabel wrote: > PS I have just now upgraded to latest couchdb clustered version, I will > see if that solves the 100% CPU usage problem. > > On 10 December 2017 at 15:28, Sinan Gabel wrote: > >> Hi, >> >> I do not have a solution

Re: 100% CPU on only a single node because of couchjs processes

.cz/security/2017/11/14/couchdb-rce-npm.html>. > > I've seen another case where a user's couchdb installation was compromised > and a bitcoin mining tool installed. This would (obviously) use all your > cpu, and I think fs-manager was part of that. > > B. &g

Re: 100% CPU on only a single node because of couchjs processes

of the nodes. > > Perhaps in your situation you just need to add some more CPU or memory > capacity? > On Sun, Dec 10, 2017 at 9:07 AM Sinan Gabel wrote: > > > Same problem with latest couchdb clustered version. What is the process " > > */.fs-manager*" doing? >

Re: 100% CPU on only a single node because of couchjs processes

icehash": false } ]} On 10 December 2017 at 18:11, Robert Samuel Newson wrote: > fs-manager is not part of couchdb. You should check that you've not been > hacked. See https://justi.cz/security/2017/11/14/couchdb-rce-npm.html < > https://justi.cz/security/2017/11/14/couchdb-rc

Re: 100% CPU on only a single node because of couchjs processes

I just found this, it may solve the problem by removing it. It is a script that starts the crypto mining program as user couchdb. [image: Inline images 1] On 11 December 2017 at 15:04, Sinan Gabel wrote: > > > I have now checked it, and it is as you @Robert perceived, a crypto mining

Re: 100% CPU on only a single node because of couchjs processes

the nano editor the command are "ctrl-k" to remove lines, and "ctrl-o" to write the file, and "ctrl-x" to exit the crontab editing. And thus the problem should be resolved. Else just write to me. On 11 December 2017 at 17:49, Sinan Gabel wrote: > I just found

Re: 100% CPU on only a single node because of couchjs processes

us code > as well (rootkit, etc) > > Definetly, If you detect a database node compromised you must destroy it > and load a backup. > > > > > > > > On Thu, Dec 21, 2017 at 6:27 PM, Sinan Gabel > wrote: > > > PS Just want to say that by removing the cron

Re: Reverse proxy for a sub directory

Hi Max, Sorry for not being able to answer your actual question, I still want to draw your attention to the need for further nginx location needs (i.e. _changes): Here's an example of a working configuration when listening at the root / and using ssl. location ~ ^/(.*)/_changes { prox

Re: efficiency of storing large HTML documents in couchdb?

Hi, Here is an introduction. http://docs.couchdb.org/en/stable/intro/why.html You can easily store .html documents in couchdb and it is very suited for that, and you can scale to clusters of clusters of couchdb nodes. And here's something about replication: http://docs.couchdb.org/en/stable/re

Re: Nginx as reverse proxy (111: Connection refused)

There should normally be a .conf file at: /etc/nginx/nginx.conf , it has http {...} and more parameters set: In that file ensure that the user set, also has access to the file with the couchdb location parameters. On Mon, 29 Oct 2018 at 11:44, max wrote: > Hi, > > I noticed strange error in

Re: Nginx as reverse proxy (111: Connection refused)

t 10:11 PM, max wrote: > > > In my nginx.conf (enclosed in my previous mail) there is "user > www-data;". > > Do you mean this user is supposed to get read access to all my CouchDB > > database files? > > > > Le lun. 29 oct. 2018 à 16:57, Sinan Gabel a

Re: automated replication of all databases on a couchdb server?

You should use the _replicator database (and not one-off replications, even if continuous), these also restart after reboot. As far as I know - someone else can correct me if I am wrong - the _replicator database speaks through Erlang port, perhaps port 4369. Thus you should check if the servers

Re: Controlling per-user access to data

Also see: https://github.com/pouchdb-community/pouchdb-authentication/blob/master/docs/recipes.md On Sun, 9 Feb 2020 at 11:26, Marcus wrote: > One database per user would not actually offer the access control > granularity required for sharing read-access to individual documents. I > originally

Re: Maximum number of databases?

You should probably make a test that fits your perceived number of databases but otherwise I would not speculate too much about what the maximum is (I do not believe there is any built-in maximum number of databases), if it works you're done. A configuration you may want to experiment with is the

Re: Per subdomain DBs with Node

Here's some further info: https://github.com/apache/couchdb-nano#pool-size-and-open-sockets https://nodejs.org/api/http.html#http_new_agent_options However, I would not worry too much about the number of sockets at first. Better to make some performance* tests that fits your use case: if the tes

Re: Fauxton and reverse proxies

Hi! Here's a link: https://docs.couchdb.org/en/stable/best-practices/reverse-proxies.html#reverse-proxying-with-nginx If this does not work, you may have to provide more information about your setup to receive proper help. Best regards, Sinan On Thu, 8 Jun 2023 at 16:36, Paul Milner wrote:

Re: http/2 with CouchDB

Hi, You can optionally put couchdb behind a proxy web server that uses http/2 between the browser and the proxy web server, and then there will only be the http(2) issue between the proxy web server and couchdb in the backend. On Wed, 21 Aug 2024 at 14:02, Andrew Ellerton wrote: > Hi all, > > As