Re: Understanding replication documents

2022-03-16 Thread Nick Vatamaniuc
I am glad you found and solved the issue, Alan. Cheers, -Nick On Wed, Mar 16, 2022 at 11:41 AM Alan Malta wrote: > > Hi Nick, all, > > After further investigation, I actually found that the problem was on my > side. > I had to port a CouchDB patch from 1.6 to 3.1 and there was an oversight >

Re: Understanding replication documents

2022-03-16 Thread Alan Malta
Hi Nick, all, After further investigation, I actually found that the problem was on my side. I had to port a CouchDB patch from 1.6 to 3.1 and there was an oversight from my side on the method name used to read a configuration parameter (now called "config" instead of "couch_config"). That was

Re: Understanding replication documents

2022-02-28 Thread Alan Malta
Hi Nick, Thank you for the follow-up investigation and questions. I am in the process of rebuilding my software stack and will try to replicate data using the very same CouchDB 3.1.2 version + Erlang 22. > ... If you get a chance to find and run a remsh script check the output of : Regarding

Re: Understanding replication documents

2022-02-27 Thread Nick Vatamaniuc
Thanks for the script, Alan. I had tried to set up a basic replication between localhost endpoint on Erlang 22 with 3.2.1 release and that seems to work: https://gist.github.com/nickva/5a89198c62fdd3ec97693c87833d5738 Looking at the differences between our setups I noticed a few things: * I

Re: Understanding replication documents

2022-02-26 Thread Alan Malta
Hi Nick, Thank you for your prompt response. Yes, I confirm that CouchDB 3.1.2 is running with Erlang 22; and that user and password only have basic chars a-z. I wiped out all my setup, started from scratch and managed to reproduce this replication issue with the following set of commands:

Re: Understanding replication documents

2022-02-26 Thread Nick Vatamaniuc
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.