couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lucas Toulouse <lucas.toulo...@cozycloud.cc>
Subject Re: TimeOut before replication with https. How to Debug?
Date Tue, 11 Dec 2012 14:00:38 GMT
This is what the log say.
For me, it did'nt find the target. And I don't know why.

Thank's for your help

Moreover, I see my plaintext password in the error, the '******' in red
color, Any issue here?
Should i open an issue? where?


[Tue, 11 Dec 2012 13:42:07 GMT] [info] [<0.32.0>] Apache CouchDB has
started on http://0.0.0.0:5984/
[Tue, 11 Dec 2012 13:45:58 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
0.25 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:45:59 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
0.5 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:45:59 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
1.0 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:46:00 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
2.0 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:46:02 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
4.0 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:46:06 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
8.0 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:46:14 GMT] [info] [<0.379.0>] Retrying HEAD request to
https://lucas-toulouse-1:*****@backup-1.cozycloud.cc/lucas-toulouse-1/ in
16.0 seconds due to error {conn_failed,{error,eoptions}}
[Tue, 11 Dec 2012 13:46:28 GMT] [info] [<0.133.0>] 10.0.0.23 - - POST
/_replicate 500
[Tue, 11 Dec 2012 13:46:28 GMT] [error] [<0.389.0>] ** Generic server
<0.389.0> terminating
** Last message in was {'EXIT',<0.379.0>,killed}
** When Server state == {state,"https://lucas-toulouse-1:*****@
backup-1.cozycloud.cc/lucas-toulouse-1/",
                               20,[],[],
                               {[],[]}}
** Reason for termination ==
** killed

[Tue, 11 Dec 2012 13:46:28 GMT] [error] [<0.389.0>] {error_report,<0.31.0>,
                        {<0.389.0>,crash_report,
                         [[{initial_call,
                               {couch_httpc_pool,init,['Argument__1']}},
                           {pid,<0.389.0>},
                           {registered_name,[]},
                           {error_info,
                               {exit,killed,
                                   [{gen_server,terminate,6},
                                    {proc_lib,init_p_do_apply,3}]}},
                           {ancestors,
                               [<0.379.0>,couch_rep_sup,
                                couch_primary_services,couch_server_sup,
                                <0.32.0>]},
                           {messages,[]},
                           {links,[]},
                           {dictionary,[]},
                           {trap_exit,true},
                           {status,running},
                           {heap_size,377},
                           {stack_size,24},
                           {reductions,496}],
                          []]}}


2012/12/11 Andrey Kuprianov <andrey.kouprianov@gmail.com>

> What does couch log say?
>
>
> On Tue, Dec 11, 2012 at 6:06 PM, Lucas Toulouse
> <lucas.toulouse@cozycloud.cc
> > wrote:
>
> > Hello
> >
> > I test Couchdb for future production use.
> >
> > I want to use a instance of Couchdb as a backup on a server B. and I
> have a
> > another couchdb that run only on localhost on a server A.
> > I would use single replication (not continuous) to backup the couch A to
> > couch B.
> >
> > The couch B is online. Behind a reverse proxy who negociate SSL session
> and
> > transfer request in http to the Couch B.
> >
> > I launch locally on the server A a replication from source (local base on
> > A) and target couch B with credentials and remote DbName
> >
> > After few seconds, i receive this Json {"error":"timeout"}.
> >
> > When I try a curl from shell A I success to authentificate myself on the
> > Couch B. So this step seems Ok, and the server B answer my request.
> >
> > How I can debug from this message? A way to have more information?
> >
> > Have I a proxy config problem? Other things looks good on this proxy.
> >
> >
> > Best regards
> >
> > Lucas
> >
>

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