incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Leddy <m...@loop.com.br>
Subject Re: Replication hangs w/redirected URL
Date Thu, 15 Jul 2010 17:49:15 GMT
I haven't seen the first one... but I can help you with the second:

1> [info] [<0.130.0>] 127.0.0.1 - - 'POST' /photos/_bulk_docs 415

The 415 response is v1.0.0 rejecting the bulk docs update because v0.11
doesn't include the required content type application/json. I ran into
this one when I upgraded one of my nodes to 1.0.0

My temporary solution was to patch v1.0.0 to not require the correct
content type until I have all my nodes running v1.0.0. ie. commenting
out line 272 in couch_httpd_db.erl:

    % couch_httpd:validate_ctype(Req, "application/json"),

Regards,

Mike


On Thu, 2010-07-15 at 09:05 -0700, Nathan Vander Wilt wrote:
> First of all, congrats to all on the 1.0 release!
> 
> I am having some trouble replicating a database from CouchDBX-0.11.0-R13B04-64bit-Snow-Leopard
to CouchDBX-1.0.0-7-Universal, however. On the new version, the replicate request gets stuck
in this loop:
> 
> 1> [error] [<0.163.0>] streaming att. ended but more data requested {1279,208676,683283}
> 1> [info] [<0.163.0>] request for "_design%2Fwebviewer/index.html" timed out,
retrying in 0.5 seconds
> 1> [error] [<0.163.0>] streaming att. ended but more data requested {1279,208677,197296}
> 1> [info] [<0.163.0>] request for "_design%2Fwebviewer/index.html" timed out,
retrying in 0.5 seconds
> 1> [error] [<0.163.0>] streaming att. ended but more data requested {1279,208677,709212}
> 1> [info] [<0.163.0>] request for "_design%2Fwebviewer/index.html" timed out,
retrying in 0.5 seconds
> 1> [error] [<0.163.0>] streaming att. ended but more data requested {1279,208678,225227}
> 1> [info] [<0.163.0>] request for "_design%2Fwebviewer/index.html" timed out,
retrying in 0.5 seconds
> ....
> 
> The old version (running on port 5983) is showing the following activity while this is
happening:
> 
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design%2Fwebviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
301
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design/webviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
200
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design%2Fwebviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
301
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design/webviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
200
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design%2Fwebviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
301
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /t1i_digipics/_design/webviewer/index.html?rev=1-6513a876c403710e07df0c8a7d5dfebe
200
> ....
> 
> I can pull up the document fine in Safari. Is the replication in 1.0 not handling the
redirect properly?
> 
> When I try to run in the opposite direction (starting fresh) by pushing from the old
database to the new I get an "Replication failed: undefined" alert in the /_config/ interface,
and the following logged by each instance:
> 
> Starting CouchDB...
> Eshell V5.7.5  (abort with ^G)
> 1> Apache CouchDB 0.11.0 (LogLevel=info) is starting.
> 1> Apache CouchDB has started. Time to relax.
> 1> [info] [<0.35.0>] Apache CouchDB has started on http://127.0.0.1:5983/
> 1> [info] [<0.111.0>] 127.0.0.1 - - 'GET' /_all_dbs 200
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' /_session 200
> 1> [info] [<0.98.0>] 127.0.0.1 - - 'GET' / 200
> 1> [info] [<0.116.0>] starting new replication "680eba2b70fe92691ae066e159fab5d7"
at <0.136.0>
> 1> [info] [<0.136.0>] replication terminating due to target_error: <<"bad_content_type">>
> 1> [info] [<0.116.0>] 127.0.0.1 - - 'POST' /_replicate 500
> 1> 
> 
> 
> Starting CouchDB...
> Eshell V5.7.5  (abort with ^G)
> 1> Apache CouchDB 1.0.0 (LogLevel=info) is starting.
> 1> Apache CouchDB has started. Time to relax.
> 1> [info] [<0.36.0>] Apache CouchDB has started on http://127.0.0.1:5984/
> 1> [info] [<0.106.0>] 127.0.0.1 - - 'HEAD' /photos/ 200
> 1> [info] [<0.130.0>] 127.0.0.1 - - 'GET' /photos/ 200
> 1> [info] [<0.138.0>] 127.0.0.1 - - 'GET' /photos/_local%2F680eba2b70fe92691ae066e159fab5d7
404
> 1> [info] [<0.139.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.140.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.141.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.142.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.144.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.145.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.146.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.106.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.106.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.106.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1> [info] [<0.130.0>] 127.0.0.1 - - 'POST' /photos/_bulk_docs 415
> 1> [info] [<0.106.0>] 127.0.0.1 - - 'POST' /photos/_missing_revs 200
> 1>  
> 
> Any tips or pointers to what's going wrong and how to correct would be appreciated. For
now, I've just deleted my photo couchapp's design document from the source repo and replication
seems to be progressing nicely.
> 
> thanks,
> -natevw



Mime
View raw message