replication sometimes fails
@drebs posted a log in #8706 (closed) about a failed replication rake task.
Since the task resulted in a couchdb 500 i created https://github.com/apache/couchdb/issues/912 .
CouchDB devs were very responsive saying that the error points at a missing target. So i investigated the replication definition:
{
"source":"tokens_582",
"filter":"rotation_filter/not_expired",
"target":"http://admin:...@localhost:4000/tokens_583",
"continuous":true
}
What is interesting is the port number. We have an stunnel from the couchdb client to the server that uses this port. However it looks to me like the port is not available on the couch node itself though:
root@aardwolf:~# curl localhost:5984
{"couchdb":"Welcome","uuid":"bf8a3ad0d04f254ffbd571b710aa6eb6","version":"1.6.0","vendor":{"name":"The Apache Software Foundation","version":"1.6.0"}}
root@aardwolf:~# curl localhost:4000
curl: (7) Failed to connect to localhost port 4000: Verbindungsaufbau abgelehnt
Which leaves me wondering how replication could ever work on the environments that have separate couch and webapp nodes.