couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: Status of 1.2.1 and 1.2.0
Date Tue, 12 Mar 2013 14:04:59 GMT
Thanks Lucas!

I am hoping someone else can step in here to talk you through the problems
you're experiencing.


On 12 March 2013 11:22, Lucas <lucas@cozycloud.cc> wrote:

> Yes, Noah I still have problems. I pause them for few days, but still have
> them.
> We've update to 1.2.1
>
> Thank's to answer.
>
>
> 1-> We see more couchdb instance bloked in their replication. More over
> Couchdb crash sometimes and need a manual restart.
>  In fact we link that to install of one our application.
>  We try to copy a mail box. (So large web box).
>  We open an issue for that :
> https://issues.apache.org/jira/browse/COUCHDB-1672
>     I could tell your more info about that if you want.
>
>
>
> 2-> Replication trough https
> Update to 1.2.1 change nothing.
> We have a signed certificate. We try with it and with selfsigned (and
> desactivate checking in couch)
>
> We replicate from the couchA to couchB.
> CouchA is in a OpenVZ container and listen only localhost. Could access to
> the Internet.
> CouchB is in a openVZ container , on a other server, it listen the internet
>
> we try
> --> to route a port from host to CouchB directly. and do SSL with Couchdb.
> --> to route connection on 443/80 with a reverse proxy Nginx to CouchB
> where SSL/TLS is done by Nginx.
> --> to route connection for 443 to 443 on the container but not do SSL on
> nginx but with CouchSSL config.
>
> In this three way to listen the internet from CouchB
> We CAN'T do the replication from A.
> But trough Curl or any Browser operations with Futon, it works.
>
>
> Thank to your consideration
>
> Lucas
>
>
> 2013/3/10 Noah Slater <nslater@apache.org>
>
> > Are you still having problems Lusas?
> >
> >
> > On 11 January 2013 10:40, Lucas Toulouse <lucas.toulouse@cozycloud.cc
> > >wrote:
> >
> > > Hello.
> > >
> > > I prepare a mail yesterday. And after seeing mails of mailing list this
> > > morning, I modify my point of view.
> > >
> > >
> > > I use (try) to deploy couchdb in our production server. I today in
> > version
> > > 1.2.0. and have some troubles with replication
> > >
> > > -> Is the 1.2.1 officially release this night, i'm right?
> > >
> > > I'm oppose with 2 'bugs' or wrong conf, in my usage of couchdb.
> > >
> > > First, I use one instance of couchdb in localhost as DB. And each
> night,
> > i
> > > would replicate changes to another instance of couch (in an other
> > > server)(who listen from the internet).
> > > I use _replicator (not continuous) to launch my replication.
> > > Sometimes it work's, sometimes it's not. An error of timed out where
> > > 'new_edit=false' return 201 and the worker died.
> > > It's looks like https://issues.apache.org/jira/browse/COUCHDB-1510.
> > >
> > >
> > > My second problem is more networking.
> > > The couch local listen local host, and the remote, the port 80/443
> where
> > > nginx negociate ssl(if 443) and redirect to the remote couch on port
> 5984
> > > (server locally).
> > >
> > > I launch the replication from the first couch in local with homemade
> > script
> > > using requests module of python (like curl so).
> > > I success to create user, db,... trough https(443) and http(80).
> > > But the replication working ONLY with http.
> > > -> Is it look like to
> https://issues.apache.org/jira/browse/COUCHDB-1377 ?
> > >
> > >
> > > So It's seems enhance in 1.2.1 according to JIRA. (and mails)
> > >
> > > -> Is the update to 1.2.1 could fix this two issues ?
> > > -> How to do that properly? (For uninstalling 1.2.0)
> > >
> > > If anyone has an advice, i take it with humility.
> > >
> > > Thank's.
> > >
> > >
> > > Lucas
> > >
> >
> >
> >
> > --
> > NS
> >
>



-- 
NS

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message