Re: Error trying replicator

[zecat]

If you are on Windows, the "EACCES" error  on test pass is "normal" as 
JIra bug said.   ( http://issues.apache.org/jira/browse/COUCHDB-326 ) 
...  so it should not be misinterpreted.

Sorry
Stéphane Mourey a écrit

No!
I got:

   1. *Exception raised:* {"error":"error","reason":"eacces"}

What does it mean?

2010/1/29 Paul Davis <paul.joseph.da...@gmail.com>

  
Does the replicator test in Futon pass for you?

2010/1/29 Stéphane Mourey <stephane.mou...@gmail.com>:
    
Yes, I've checked that before trying to replicate. I've read somewhere
      
that
    
you need this flag in your request if your db does not exist yet. If you
      
try
    
with Futon, you get this javascript alert:
Replication failed: {error,{db_not_found,<<"
http://91.121.54.128:5984/testsofi/";>>}}
which is different from the one I got previously and was :
"Replication failed: could not open http://myserver:5984/mydb/";.

2010/1/29 Paul Davis <paul.joseph.da...@gmail.com>

      
Oh, I should read tracebacks.

You either need to make sure that mydb2 exists before creation or pass
a flag in the replicator request. I'm not sure if Futon has a UI for
that yet though.

HTH,
Paul Davis

2010/1/29 Stéphane Mourey <stephane.mou...@gmail.com>:
        
Hi Paul,

The config of my local server in unchanged. I've bind the correct ip
          
in
    
the
        
config file of the distant db, and can access it from my local host
          
with
    
my
        
browser, but not with the replicator.
But you gave me an idear. I've just tried to replicate from one local
          
db
    
to
        
another local db, same server, but adressing the second as a distant
          
(i.e.
        
replicate from local mydb to distant http://127.0.0.1:5984/mydb2). It
          
failed
        
too!??!
Here is the log:
[Fri, 29 Jan 2010 13:23:47 GMT] [error] [<0.13432.0>]
{error_report,<0.24.0>,
   {<0.13432.0>,crash_report,
    [[{initial_call,{couch_rep,init,['Argument__1']}},
      {pid,<0.13432.0>},
      {registered_name,[]},
      {error_info,
          {exit,
              {db_not_found,<<"http://127.0.0.1:5984/mydb2/";>>},
              [{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
      {ancestors,

          
[couch_rep_sup,couch_primary_services,couch_server_sup,<0.1.0>]},
        
      {messages,[]},
      {links,[<0.43.0>]},
      {dictionary,[]},
      {trap_exit,true},
      {status,running},
      {heap_size,1597},
      {stack_size,24},
      {reductions,466}],
     []]}}

[Fri, 29 Jan 2010 13:23:47 GMT] [info] [<0.5467.0>] 127.0.0.1 - -
          
'POST'
    
/_replicate 404
I tried the same thing on the server (just using the bind adresse
          
instead
    
of
        
the 127.0.0.1), and it works.
So, it seems not to be a net issue, but a local one...

Thanks for your help and best regards,

Stephane

2010/1/29 Paul Davis <paul.joseph.da...@gmail.com>

          
Have you changed your CouchDB bind address? If its still set to
127.0.0.1 (which is the default) then you will only be able to access
it through 127.0.0.1 (or localhost if your hosts file is normalish).

If you want to use both 127.0.0.1 and $server_ip, then you should
update the configuration to 0.0.0.0

Or alternatively use local replication, or specify 127.0.0.1 instead
of $server_ip.

I only scanned quickly through the conversation so I may have missed
something.

Paul

2010/1/29 Stéphane Mourey <stephane.mou...@gmail.com>:
            
Thanks for your help.
I'll try monday, and let you know.

Best regards.

2010/1/29 zecat <couc...@lechat.org>

              
No definitively, I think you could give me your new googles... (-;
                
No
    
difference, right...

Yes you answered the question : if you can access from your
                
browser
    
to
        
server_ip, and your source db runs on the same as browser, yes
                
source
    
db
        
can
            
get server_ip.
Except if some antivirus or firewall or something else denies to
                
cmd
    
(or
        
service if running 0.11 - which version are you running 0.9 - 0.11
                
?
    
which
            
os ?) to go out to 5984 to remote, but accepts it when this is
                
initiated
        
by
            
the browser ?

At this point, you should try to sniff the communication to port
                
5984
    
between 127.0.0.1 and server_ip to check if they are speaking
                
together
        
or
            
not. Try wireshark for exemple. You should see that when using
                
hostname,
        
nothing is going out....


To illustrate my first thought :
I try two replication  : first with ip, second with hostname. As
                
you
    
could
            
read, when using hostname, the log, with error, is exactly the
                
same
    
you
        
get
            
.

First, replication is made with ip : -> success

[Fri, 29 Jan 2010 11:25:12 GMT] [info] [<0.11862.0>] starting
                
replication
            
"4925b1e30fdce425609eec7e8f3b2202" at <0.11915.0>
[Fri, 29 Jan 2010 11:25:12 GMT] [info] [<0.11915.0>] recording a
                
checkpoint
            
for db1 -> http://10.0.0.2:5984/mydb/ at source update_seq 5
[Fri, 29 Jan 2010 11:25:12 GMT] [info] [<0.11862.0>] 127.0.0.1 - -
                
'POST'
            
/_replicate 200


Second,  replication is made with hostname : -> fail

[Fri, 29 Jan 2010 11:24:10 GMT] [error] [<0.167.0>]
                
{error_report,<0.24.0>,
            
  {<0.167.0>,crash_report,

   [[{initial_call,{couch_rep,init,['Argument__1']}},
     {pid,<0.167.0>},

     {registered_name,[]},
     {error_info,
         {exit,
             {db_not_found,
                 <<"http://server1.mydom.com:5984/mydb/";>>},


                
 [{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
    
     {ancestors,

                
 [couch_rep_sup,couch_primary_services,couch_server_sup,<0.1.0>]},
            
     {messages,[]},
     {links,[<0.43.0>]},
     {dictionary,[]},
     {trap_exit,true},
     {status,running},
     {heap_size,987},
     {stack_size,24},
     {reductions,376}],
    []]}}
[Fri, 29 Jan 2010 11:24:10 GMT] [info] [<0.89.0>] 127.0.0.1 - -
                
'POST'
        
/_replicate 404

I have no more idea at this time. Sorry.

Please let me known if you find some solution.


Thierry

Stéphane Mourey a écrit :

                
Thierry,


Thanks again.
I cannot see any diffence between your two posts, I may need new
googles...
But I think I get the point. So:

My source db runs on the same host as my browser (i.e. on my
                  
desktop),
        
and
            
I
try to run the replication from Futon on this host (i.e.
http://127.0.0.1:5984/_utils/replicator.html). I suppose that if
                  
my
    
browser
can access to the remote db (http://server_ip:5984/mydb), my
                  
local
    
couchdb
server can also, am I right?
I suppose this answer your question.

Any idears?

Best regards,

Stephane

2010/1/29 zecat <couc...@lechat.org>



                  
Ouppss some mistakes in urls: Please use this answer...

Stéphane,

You open Futon from your browser by calling
                    
http://ip1:5984/_utils
    
Right ? (ie : http://10.0.0.1:5984/mydb  )
You have checked you can access the db using
http://server_ip:5984/mydbfrom your browser. (ie

http://10.0.0.2:5984/mydb )


Have you checked that server IP1 (ie: 10.0.0.1) is able to
                    
communicate
        
with
server_ip (ie 10.0.0.2) on port 5984  ?
As the replication script runs on IP1 (ie : 10.0.0.1) , it must
                    
have
        
this
            
access.

Thierry

zecat a écrit :



                    
Stéphane,

You open Futon from your browser by calling
                      
http://ip1:5984/_utils
        
Right ? (ie : http://10.0.0.1:5984/mydb  )
You have checked you can access the db using
http://server_ip:5984/mydbfrom your browser. (ie

http://10.0.0.2:5984/mydb )


Have you checked that server IP1 (ie: 10.0.0.1) is able to
                      
communicate
            
with server_ip (ie 10.0.0.2) on port 5984  ?
As the replication script runs on IP1 (ie : 10.0.0.1) , it must
                      
have
        
this
access.

Thierry

Stéphane Mourey a écrit :



                      
Hi Thierry,

Many thanks for your quick answer.
Butit it's still not working.
Same javascript alert.
The log said:
[Fri, 29 Jan 2010 10:36:15 GMT] [error] [<0.3117.0>]
{error_report,<0.24.0>,
  {<0.3117.0>,crash_report,
   [[{initial_call,{couch_rep,init,['Argument__1']}},
     {pid,<0.3117.0>},
     {registered_name,[]},
     {error_info,
         {exit,
             {db_not_found,<<"http://server_ip:5984/mydb/
                        
">>},
    
 [{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
            
     {ancestors,


                        
[couch_rep_sup,couch_primary_services,couch_server_sup,<0.1.0>]},
    
     {messages,[]},
     {links,[<0.43.0>]},
     {dictionary,[]},
     {trap_exit,true},
     {status,running},
     {heap_size,1597},
     {stack_size,24},
     {reductions,473}],
    []]}}

[Fri, 29 Jan 2010 10:36:15 GMT] [info] [<0.3064.0>] 127.0.0.1
                        
- -
    
'POST'
/_replicate 404

I've checked I can access the db using
                        
http://server_ip:5984/mydbfrom
        
my browser.

Any idears, guys?

Best regards,

Stephane


2010/1/29 zecat <couc...@lechat.org <mailto:
                        
couc...@lechat.org>>
    
  Hi,

  I have experimented this trouble during two days, until I
                        
found
    
  that replication (_replicate) is not able to work with
                        
hostname
    
in
        
  from or target field.

  Try only with IP address and you will see that replication
                        
is
    
  working very well as expected (-;


  Thierry

  Stéphane Mourey a écrit :

      Hi everybody,

      I've start to work with Couch just a month ago, and I'm
                        
very
        
      enthousiastic
      about it.
      I'm working on my desktop for development purposes. Now
                        
I'm
    
      trying to
      replicate my local db on our server.
      Both Couchdb server seems to work correctly. I can
                        
access
    
      http://127.0.0.1:5984/_utils/database.html?mydb,
      http://127.0.0.1:5984/mydb,
      http://myserver:5984/_utils/database.html?mydb,
      http://myserver:5984/mydbwith my browser, and can add
      documents from

      Futon. mydb is empty on the
      server, and I'm trying to replicate datas from the local
                        
db
    
to
        
      the server.
      For this, I use the Replicator function from Futon on my
      localhost. I did
      not try from the server, as incomming connections are
                        
not
    
      allowed on my lan.
      I got this JavaScript alertbox: "Replication failed:
                        
could
    
not
        
      open
      http://myserver:5984/mydb/";.
      In the log: I found:
      Fri, 29 Jan 2010 08:33:10 GMT] [error] [<0.1851.0>]
      {error_report,<0.24.0>,
         {<0.1851.0>,crash_report,
          [[{initial_call,{couch_rep,init,['Argument__1']}},
            {pid,<0.1851.0>},
            {registered_name,[]},
            {error_info,
                {exit,
                    {db_not_found,<<"
                        
http://myserver:5984/mydb/
    
">>},
            
[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
            {ancestors,


                        
[couch_rep_sup,couch_primary_services,couch_server_sup,<0.1.0>]},
    
            {messages,[]},
            {links,[<0.43.0>]},
            {dictionary,[]},
            {trap_exit,true},
            {status,running},
            {heap_size,1597},
            {stack_size,24},
            {reductions,460}],
           []]}}

      [Fri, 29 Jan 2010 08:33:10 GMT] [info] [<0.1282.0>]
                        
127.0.0.1
        
      - - 'POST'
      /_replicate 404
      I googled a while, but did not find anything helpfull
                        
for
    
the
        
      moment.
      Can anyone told what's wrong with this?

      Best regards,

      Stephane Mourey