incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: problem with replication through proxy
Date Wed, 08 Jun 2011 20:46:50 GMT
The replicator is looking for a checkpoint. It's perfectly ok if it
doesn't find one, though.

I suspect Apache is returning its own 404 message (and response body)
instead of the one that couchdb sends, and that the replicator is
expecting. Disable the error page handling and have another try.


On 8 June 2011 21:42, Kevin R. Coombes <> wrote:
> Hi,
> We have a setup with CouchDB running behind an Apache proxy, and are having
> trouble replicating from the proxy to an outside server.  Basically, you can
> imagine the following setup:
> Proxy Server:
>    which forwards GET requests (but not PUT, POST, or DELETE) to
> CouchDB server:
>    and we want to replicate this database to
> New CouchDB Server:
> We started by creating a new empty database ('newdb') on the new server; it
> contains absolutely no documents.  We then POST a replicaton request to the
> new server in the form
> curl -X POST -d
> '{"source":"",
> "target":""}'
> The error message we get has the form
>    The requested URL
>        /ourdb/_local/8262b7d6670639f25400d5940bbe4094
>    was not found on this server.
> We cannot figure out what it is looking for (since it does not exist on the
> server...)  And so we cannot tell if this is a problem with the
> configuration of the proxy server or if it is something about our particular
> database.  As far as we can tell, none of the documents in the original
> couch database has an _id that looks anything like this.  (We assigned all
> of the _id's manually, since there is a good semantic reason to assign
> meaningful unique _id's in our application.)
> Can anyone point us in the right direction to resolve this problem?
> Thanks,
>    Kevin

View raw message