You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Pieter van der Eems (JIRA)" <ji...@apache.org> on 2013/02/07 11:31:12 UTC

[jira] [Created] (COUCHDB-1671) Couchdb Statemachine crach when replicating between touchdb and couchdb

Pieter van der Eems created COUCHDB-1671:
--------------------------------------------

             Summary: Couchdb Statemachine crach when replicating between touchdb and couchdb
                 Key: COUCHDB-1671
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1671
             Project: CouchDB
          Issue Type: Bug
          Components: Replication
            Reporter: Pieter van der Eems


TouchDB on IOS started a replication (pull) from a couchdb (1.2.0) server.
The database in question contains about 8000 documents.
About half way during replication touchdb returns this error:
{panel:title=TouchDB error}
error (
    502,
    "502 Remote server error"
)
{panel}

In the couchdb log I see the following:
{code:title=Couchdb log}
[Thu, 07 Feb 2013 09:20:04 GMT] [info] [<0.5193.2174>] 87.195.224.218 - - GET /nl_jkroon_dirksland_de_nieuwe_gooye/ 200
[Thu, 07 Feb 2013 09:20:04 GMT] [error] [<0.23620.2208>] ** State machine <0.23620.2208> terminating 
** Last message in was {tcp,#Port<0.136125855>,
                            <<128,130,1,3,1,0,105,0,0,0,16,0,0,5,0,0,4,1,0,
                              128,0,0,2,0,0,8,0,0,20,0,0,3,2,0,128,0,0,1,0,0,
                              21,0,0,6,4,0,128,0,0,22,0,0,23,0,0,51,0,0,57,0,
                              0,25,0,0,58,0,0,26,0,0,24,0,0,53,0,0,9,0,0,10,0,
                              0,27,0,0,47,0,0,52,0,0,56,0,0,50,0,0,19,0,0,18,
                              0,0,17,7,0,192,6,0,64,3,0,128,0,0,255,145,18,95,
                              43,179,84,113,194,115,160,150,6,253,89,160,223>>}
** When State == hello
{code}

Complete couchdb log: [http://pastebin.com/rreiEd7f]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira