Re: View returning errors

Hey Karl, I believe this is uncool and annoying. But you are writing, that you are using CouchDB 1.3, what is a very old version. I am not sure if anyone here can reproduce that error. So I know this will not solve your problem, but are you able to upgrade to a newer version? There is CouchDB

View returning errors

I'm running an instance of Couchdb 1.3 on a CentOS VM. All of the views I have written for a certain db are now returning an error, previously they were all working. All the views return a "noproc" error and there is a variety of gen_server, and get_state errors An example log report: [Wed, 12

Re: httpd vs chttpd, and 5984 vs 5986

Looks like you skipped over the "setup cluster" step from the installation notes on docs.couchdb.org. Even a single/node cluster-of-one needs this, as it creates the necessary system databases. At this point, best to ignore the 5986 port (unless for per-node maintenance). Cheers Jan -- > On

httpd vs chttpd, and 5984 vs 5986

I've installed CouchDB 2.0.0 from source using: ./configure make release sudo mv rel/couchdb /var/lib/couchdb sudo chown -R couchdb:couchdb /var/lib/couchdb sudo -u couchdb /var/lib/couchdb/bin/couchdb The problem I'm seeing is that, by default, [chttpd] is being assigned port 5984 (in the

Re: CouchDB 2.0.0 on Windows 10

Ah - that makes sense. I think the problems are all around the service installation. I've also been unable to properly remove my old 1.6 instance, so have to run 2.0 manually. But it is fine with a clean install, on a machine which has never had earlier versions. Nick > On 12 Oct 2016, at

Re: CouchDB 2.0.0 on Windows 10

Hi Nick. 2.0 is running as a service. I start 1.6 manually and it is not shown as a service. When started, DOS and Erlang windows open and when closed, 1.6 stops. On 12 October 2016 at 12:35, Nick North wrote: > Do you have both versions installed as services? I'd expect

Re: CouchDB 2.0.0 on Windows 10

Do you have both versions installed as services? I'd expect some clash if they are. Nick > On 12 Oct 2016, at 11:28, John Le Brasseur wrote: > > Hi. > I had this problem and reported it previously(CouchDB 2.0.0 on Windows 10). > I never solved it or found the cause

Re: CouchDB 2.0.0 on Windows 10

Hi. I had this problem and reported it previously(CouchDB 2.0.0 on Windows 10). I never solved it or found the cause or even saw a possible sign of the cause. As it happened, I was busy with connecting an SD card reader on my Windows machine and it seems the imported 3rd party drivers caused a

Re: CouchDB: 2.0 & 1.6.1 database compatibility

> On 12 Oct 2016, at 11:55, Bogdan Andu wrote: > > On Mon, Oct 10, 2016 at 4:36 PM, Jan Lehnardt wrote: > >> >>> On 10 Oct 2016, at 14:59, Bogdan Andu wrote: >>> >>> yes, I know , but couchdb storage engine cannot optimize >>> this

CouchDB 2.0 start/stop dilemma

Hi, I see Couch 2.0 comes with a free style start / stop mechanism and the user is encouraged to use runit or whatever mechanism he already has on his system. I do not want to use runit when I have modern systems like centos 7 or f edora 24 server editions that have systemd to start/stop couchdb

Re: CouchDB: 2.0 & 1.6.1 database compatibility

On Mon, Oct 10, 2016 at 4:36 PM, Jan Lehnardt wrote: > > > On 10 Oct 2016, at 14:59, Bogdan Andu wrote: > > > > yes, I know , but couchdb storage engine cannot optimize > > this while operating normaly. only after compaction is finished, the > > database > >