[ https://issues.apache.org/jira/browse/COUCHDB-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ramage closed COUCHDB-1471.
--------------------------------
Resolution: Not A Problem
Fix Version/s: 1.2
Jason Smith has shown the solution.
> Replication errors when posting doc as admin to _replicator db where doc contains a target
db which has a security doc with "members":{"names":[],"roles":["_admin"]}
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-1471
> URL: https://issues.apache.org/jira/browse/COUCHDB-1471
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 1.2
> Reporter: Ryan Ramage
> Priority: Minor
> Fix For: 1.2
>
>
> The following are the curl commands to reproduce this error:
> curl -X PUT http://admin:admin@localhost:5984/test-broken-replicator/
> curl -X PUT http://admin:admin@localhost:5984/test-broken-replicator/_security \
> -H "Content-Type: application/json" -d '{"admins":{"names":[],"roles":[]},"members":{"names":[],"roles":["_admin"]}}'
> curl -X PUT http://admin:admin@localhost:5984/test-broken-replicator-2/
> curl -X POST http://admin:admin@localhost:5984/_replicator \
> -H "Content-Type: application/json" -d '{ "source" : "test-broken-replicator-2", "target"
: "test-broken-replicator"}'
> here is the _replicator doc created, with the error state:
> {
> "_id": "d3d80187927957468e11f2e9cd000bc7",
> "_rev": "2-210555af6240c91fd5ed8f4c65009c7a",
> "source": "test-broken-replicator-2",
> "target": "test-broken-replicator",
> "owner": "admin",
> "_replication_state": "error",
> "_replication_state_time": "2012-04-25T20:52:16-06:00",
> "_replication_id": "e19511da196febe1da5f74495f132255"
> }
> Here is the snip from the debug log
> 2012-04-25 20:52:16.792 [info] <0.149.0>@couch_httpd:log_request:662 127.0.0.1
- - POST /_replicator 201
> 2012-04-25 20:52:16.795 [info] <0.206.0>@couch_replicator_manager:maybe_start_replication:374
Attempting to start replication `e19511da196febe1da5f74495f132255` (document `d3d80187927957468e11f2e9cd000bc7`).
> 2012-04-25 20:52:16.798 [error] <0.1996.0> CRASH REPORT Process <0.1996.0>
with 0 neighbours crashed with reason: {unauthorized,<<"unauthorized to access or create
database test-broken-replicator">>}
> 2012-04-25 20:52:16.810 [error] <0.206.0>@couch_replicator_manager:maybe_retry_replication:487
Error in replication `e19511da196febe1da5f74495f132255` (triggered by document `d3d80187927957468e11f2e9cd000bc7`):
{unauthorized,<<"unauthorized to access or create database test-broken-replicator">>}
> Restarting replication in 5 seconds.
> 2012-04-25 20:52:21.817 [error] <0.2005.0> CRASH REPORT Process <0.2005.0>
with 0 neighbours crashed with reason: {unauthorized,<<"unauthorized to access or create
database test-broken-replicator">>}
> 2012-04-25 20:52:21.819 [error] <0.206.0>@couch_replicator_manager:maybe_retry_replication:487
Error in replication `e19511da196febe1da5f74495f132255` (triggered by document `d3d80187927957468e11f2e9cd000bc7`):
{unauthorized,<<"unauthorized to access or create database test-broken-replicator">>}
> Restarting replication in 10 seconds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|