Hi Alan, Thanks for reaching out.
It looks like CouchDB had failed to parse the replication document, and couldn't turn it into a proper replication job. The 'undef' error could suggest running on an unsupported version of Erlang. It's a generic "this function doesn't exist" error in Erlang. Are you running on at least Erlang 20? Does the target url have any unusual characters in it, or something that might cause parsing errors (say, ':' or '@' characters for example). Would it be possible to have an example script which fails. Ideally, a set of curl commands creating dbs, then the replication job using similar parameters you had? Cheers, -Nick On Sat, Feb 26, 2022 at 9:29 AM Alan Malta <[email protected]> wrote: > > Hi everyone, > > after a delay of many years to migrate to (almost) the latest CouchDB > version, I started working with CouchDB 3.1.2. > > My tests with replication to/from the same node/localhost have been > successful. But now that I am trying multiple push/pull replications with a > remote host, they get into a "failed" state. > > I just learned about the "_scheduler/jobs" API - and I am likely missing > some crucial knowledge here - and when I compare it against the documents > in the "_replicator" database, I see an inconsistent definition for either > the source or the target database. > For instance, the "_scheduler/jobs" gives me the following output for one > of the replications: > > {"database":"_replicator","doc_id":"87463eb82b3e1dcd7a3178276800026e","id":null,"source":"http://admin: > *****@localhost:5984/my_db_name/","target":null,"state":"failed","error_count":1,"info":{"error":"{error,undef}"},"start_time":"2022-02-26T13:43:42Z","last_updated":"2022-02-26T13:43:42Z"}, > while the "_replicator" db lists this document as: > > {"id":"87463eb82b3e1dcd7a3178276800026e","key":"87463eb82b3e1dcd7a3178276800026e","value":{"rev":"2-590d4eadf029c21303ce77116d2f3f92"},"doc":{"_id":"87463eb82b3e1dcd7a3178276800026e","_rev":"2-590d4eadf029c21303ce77116d2f3f92","source":"http://admin: > *****@localhost:5984/my_db_name","target":" > https://alanblah.blah.blah/couchdb/wmstats > ","continuous":true,"filter":"WMStatsAgent/repfilter","owner":"admin","_replication_state":"failed","_replication_state_time":"2022-02-26T13:43:42Z","_replication_state_reason":"{error,undef}"}}, > in short, the "target" parameter is defined as null in the "jobs" output. > Is it because the replication failed somehow? > > Just in case, this is the only error I see in the couch log regarding that > replication - on the node that triggered the replication: > > [error] 2022-02-26T13:43:42.016495Z [email protected] <0.534.0> -------- > Error processing replication doc `87463eb82b3e1dcd7a3178276800026e` from > `shards/00000000-7fffffff/_replicator.1645882154`: {error,undef} > > I also wonder if the replication protocol is compatible among different > releases of CouchDB? In my case, target is still on the super old version > 1.6.1 while source is on 3.1.2 > > Thank you very much for any help that you can provide. > Best, > Alan.
