Hi @Herbert !
Hm, the rsync command looks okay → the “-a” parameter carries most of the weight for our case. Can you describe the rest of the on-prem setup server? How many resources does it have?
From your logs, CouchDB restarts a few times:
- [info] 2024-11-29T03:55:46.365164Z couchdb@127.0.0.1 <0.212.0> -------- Apache CouchDB 2.3.1 is starting.
- [info] 2024-11-29T04:01:15.491701Z couchdb@127.0.0.1 <0.212.0> -------- Apache CouchDB 2.3.1 is starting.
Is there any log entry between those timestamps that points to a crash dump? Are you running CouchDB or other processes at the destination server?
A few things we want to check
- Sometimes, this error comes as a result of insufficient resources
- Sometimes, we’ve seen this error as incorrect permissions on the destination server between the files that were transferred and the couchdb container
- Can we try isolating the rsync transfer? (i.e. shut down all other processes and traffic, send data over, and then turn on processes)
- Let’s also try copying one shard over at a time. Ensuring the
.shardfolder is copied before the shard directory.
Restarting the container worked previously, my suspicion is it worked in that scenario due to resource constraints
Other things we could try after the above steps are removing --ignore-existing from the rsync command. Here is our complete rsync command that works for the exact same scenarios we are trying to finish in this task:
sudo rsync -avhWt --no-compress --info=progress2 /folder/cht/couchdb-1/shards/eaaaaaa7-ffffffff/ /new-folder/cht/couchdb-1/shards/eaaaaaa7-ffffffff