Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
1.1
-
None
-
Ubuntu 10.04 64bit, CouchDB 1.1.0, Erlang 1:13.b.3-dfsg-2ubuntu2.1, Spidermonkey 3.5.15
-
Committers Level (Medium to Hard)
Description
I just tried out native SSL in CouchDB 1.1. SSL pull replication works fine for very small databases. Though for long running older databases it never works. So this means having CouchDB 1.1.0 running on Port 5984 non SSL and on 6984 SSL replication works for the first but not for the second URL (same source database, same local target).
This is the output for the non SSL replication:
{"session_id":"8703d846d4a90184b5cdc4358ebbdec4","start_time":"Tue, 28 Jun 2011 14:57:15 GMT","end_time":"Tue, 28 Jun 2011 14:57:40 GMT","start_last_seq":0,"end_last_seq":1303811,"recorded_seq":1303811,"missing_checked":0,"missing_found":14965,"docs_read":14984,"docs_written":14984,"doc_write_failures":0}And this the error on the local CouchDB when trying this through SSL:
<0.5735.8>, {error,{badinfo,{tcp,#Port<0.10031>. Futon outputs something like Replication failed:
The remote Couch does not have any error in the log.To me this seems to be an issue on the receiving side.
Both Couches are the same version and Platform (Ubuntu 10.04 64bit).